Frequently asked questions
What is the best TTS for tourism?
MuseumEcho is a reliable text-to-speech API designed for startups building audioguides and accessible travel content. We handle voice generation so you can focus on user experience. Our service supports 23 languages and offers eight distinct voice presets suitable for various tour styles, ensuring consistent audio quality across your tourism application.
Which voice is best for museums?
Sage offers a calm, instructional tone ideal for museum exhibits, while Luna provides a soft, storytelling voice for historical narratives. Atlas delivers a neutral, news-style delivery for factual information, and Orion’s deep voice suits documentary-style tours. You can select the preset that best matches your specific content style.
Is TTS cheaper than human recording?
Our pricing is $10 per 1 million characters, or $0.01 per 1,000 characters. This model eliminates studio booking costs and allows instant updates to text without re-recording. Failed requests are free, and you only pay for actual usage, making it a cost-effective solution for dynamic or large-scale tour content.
How many languages do I need?
You do not need to buy separate licenses. Any of our eight voices can speak any of the 23 supported languages, including English, Spanish, French, German, Chinese, Japanese, and Arabic. You can generate multilingual content using the same voice model, simply specifying the desired language in your API request.
Can I use TTS for bus tours?
Yes, the API generates audio files via a simple POST request. You can pre-generate audio for long texts or generate on-demand. The service supports speeds from 0.25 to 4.0, allowing you to adjust playback speed to match the pace of a moving bus or train tour for optimal listener comprehension.
Is the audio copyright-free?
Voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain audiobooks. Generated files carry an inaudible watermark marking them as synthetic speech. Input text is not used for training, and generated audio is returned in the response without being stored, ensuring clear usage rights for your application.
How to handle multi-language tours?
Specify the ISO language code in your API request. If omitted, the system guesses the language, defaulting to English for Latin script. For non-English Latin text, explicitly set the language parameter. All eight voices support all 23 languages, allowing seamless switching between languages within a single tour application.
What is the best format?
You can choose from mp3, wav, opus, flac, or pcm formats. MP3 is recommended for general web and mobile applications due to its balance of quality and file size. WAV and FLAC offer lossless quality for high-fidelity playback, while PCM is suitable for raw audio processing in your backend systems.
Does TTS support accents?
The service supports 23 languages but does not offer specific accent customization beyond the voice presets. Each voice has a distinct character, such as Felix’s energetic promo style or Milo’s friendly conversational tone. You can adjust speed and select different voices to vary the delivery, but specific regional accents are not available.
Can I customize speed?
Yes, the API allows speed adjustment from 0.25 to 4.0. This lets you slow down complex historical explanations or speed up simple directional instructions. Adjusting speed helps optimize listener experience, especially for mobile users in noisy environments like bus tours or crowded museum halls, ensuring clear audio comprehension.
Is there a free tier?
New accounts signing in with Google receive a $0.50 trial credit, valid for 7 days, covering about 50,000 characters. Email/password accounts start without trial credit. There are no monthly plans or subscriptions. You can top up with USDT (TRC-20) starting at $5, with balance never expiring.
How to scale usage?
The API handles scaling by processing requests sequentially. For longer texts, split input into parts of up to 4,096 characters and join the resulting audio files. Rate limits are 60 requests per minute per key. Under load, requests may queue. You can issue a new API key to manage concurrent usage if needed.
What are the limits?
Each request supports up to 4,000 characters of input text. You are limited to 60 requests per minute per API key. Speed can range from 0.25 to 4.0. Failed requests do not incur charges. There is no minimum spend, and you can issue a new key at any time to reset limits.
Is it accessible?
Yes, the API supports 23 languages and allows speed adjustment from 0.25 to 4.0, aiding users with processing differences. Voices like Sage provide calm, instructional tones suitable for clear information delivery. The service is designed for startups building accessible travel content, ensuring audio can be easily integrated into screen-reader-friendly applications.
Criteria for Selection
Selecting a TTS API for museum audioguides requires balancing linguistic reach with natural delivery. You need voices that sound like professional narrators rather than robotic readers, ensuring visitors remain engaged with the content.
The integration process should be straightforward, allowing your team to focus on tour design rather than debugging audio pipelines. A reliable API minimizes technical debt from day one.
Language support
Museums often host international visitors, making multi-language support essential. Our API covers 23 languages, including English, Spanish, French, German, Chinese (Mandarin), and Japanese, ensuring clear communication across diverse crowds.
- Support for 23 major tourism languages
- Automatic language detection from script
- Consistent quality across all supported languages
Voice quality
Audio quality directly impacts visitor experience. We offer eight distinct voice presets, from warm narrators to energetic promo styles, allowing you to match the tone of your exhibits precisely.
- 8 distinct voice presets
- Licensed recordings from LibriVox
- Inaudible watermark for synthetic detection
Ease of integration
Our endpoint mirrors the OpenAI speech API, meaning you can use existing OpenAI SDKs by simply changing the base URL. This reduces development time and leverages familiar tools.
- OpenAI SDK compatible
- Standard JSON request format
- Simple POST endpoint
Voice Options for Tourism
Museum audioguides require distinct vocal personalities to match the content’s intent. We offer eight voice presets, each tailored for specific narrative or instructional roles, ensuring your tours sound professional and consistent.
Choose between warm narrators for historical stories or calm instructors for technical details. Each voice is grounded in licensed recordings, providing a reliable, human-like baseline without the variability of generic synthetic voices.
Narrative styles
Aria provides a warm, clear narration ideal for storytelling and historical accounts. Luna provides a soft, storytelling voice. Their natural cadence helps visitors connect with the content, making complex history feel personal and engaging.
Sage offers a calm, instructional tone perfect for guiding users through museum layouts or technical explanations. Her steady delivery ensures clarity without distraction, helping visitors absorb information without feeling rushed.
- Aria: Warm, clear narrator for historical stories
- Luna: Soft, storytelling voice for emotional exhibits
- Sage: Calm, instructional tone for guided tours
Informative tones
Felix brings energetic, promo-ready energy suitable for quick highlights or promotional snippets within a tour. His bright delivery captures attention during brief interludes or call-to-action segments.
Atlas delivers a neutral, news-style voice ideal for factual exhibits, dates, and historical data. His consistent tone ensures accuracy and clarity, reducing listener fatigue during dense informational segments.
- Atlas: Neutral, news-style for factual data
- Felix: Energetic, promo-style for highlights
- Milo: Friendly, conversational for interactive tours
Engaging delivery
Milo and Orion offer conversational and deep documentary tones that enhance visitor engagement. Milo’s friendly approach works well for interactive or family-friendly content, while Orion’s depth suits immersive historical documentaries.
Nova’s bright, upbeat voice adds energy to dynamic exhibits or youth-focused tours. Each voice is designed to maintain listener interest over extended periods, ensuring consistent engagement throughout the audioguide experience.
- Orion: Deep, documentary-style for immersive tours
- Nova: Bright, upbeat for dynamic exhibits
- Milo: Friendly, conversational for interactive content
Language Coverage
Museums and tourism startups operate in global markets, requiring clear audio for diverse visitor demographics. MuseumEcho supports 23 languages, ensuring your audioguide reaches international audiences without needing separate voice talent for each region.
23 languages supported
Our API handles Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, and Turkish. Any voice can speak any of these languages, allowing you to maintain consistent audio quality across all supported regions.
Major tourism languages
We prioritize the most common tourism languages, including English, Spanish, French, German, Japanese, and Mandarin Chinese. This coverage ensures that major tourist hubs have high-quality, natural-sounding narrations for their primary visitor bases.
Auto-detection
If you do not specify a language, the system guesses it from the script. Latin script text defaults to English. For non-English Latin-script text, explicitly set the language parameter to ensure accurate pronunciation and avoid misinterpretation.
Pricing Models
MuseumEcho uses a straightforward per-character billing model at $10 per million characters, meaning you pay only for what you generate. Spaces and punctuation count as characters, and failed requests are refunded in full, ensuring you never pay for errors.
Per-character billing
The cost is $0.01 per 1,000 characters. This transparent model allows startups to accurately forecast audioguide production costs without hidden surprises or complex tier structures.
- No minimum spend required
- Failed requests are free
- Balances do not expire
No monthly fees
We do not enforce monthly subscriptions, seat limits, or minimum usage requirements. You can pause usage during off-seasons and resume without administrative penalties or contractual commitments.
Free trial available
Signing in with Google provides $0.50 in trial credit, valid for 7 days. Accounts created with email and password start without trial credit. This allows you to test voice quality and integration workflows with approximately 50,000 characters before committing to top-ups via USDT (TRC-20).
Technical Requirements
MuseumEcho’s API mirrors the OpenAI speech endpoint structure, allowing you to send POST requests to https://api.siap234.cc/v1/audio/speech with standard JSON bodies. This design means you can integrate the service using familiar patterns without learning a new protocol.
You can use official OpenAI SDKs by simply updating the base_url to https://api.siap234.cc/v1 and providing your unique API key. This reduces development time, letting you focus on building the audioguide experience rather than managing custom HTTP clients.
Requests are processed sequentially. Long texts should be split into parts of up to 4,096 characters and the audio files joined. This ensures consistent delivery even for detailed museum descriptions.
API compatibility
The API follows a standard JSON request shape, accepting model, input, voice, and response_format fields. This compatibility allows you to swap in MuseumEcho with minimal code changes if you are already using OpenAI-compatible libraries.
You can test integration immediately using ready-made curl examples available on the /get-api-key/ dashboard, ensuring your setup works before deploying to production environments.
- POST endpoint at
/v1/audio/speech - Standard JSON body structure
- Compatible with OpenAI request formats
SDK support
While we do not provide a proprietary SDK, the interface is designed to work seamlessly with official OpenAI SDKs. You only need to change the base_url configuration to point to our API endpoint.
This approach leverages existing documentation and community resources, making it easier for startups to find solutions for common integration challenges without waiting for vendor-specific updates.
Rate limits
Each API key is limited to 60 requests per minute. New accounts start with a lower limit of 10 requests per minute until the first top-up is processed.
Under load, requests are queued and processed one after another. For most audioguide applications, this throughput is sufficient, as generation speed is roughly real-time (25 characters per second).
Audio Formats
Select from MP3, WAV, Opus, FLAC, or PCM formats. MP3 is recommended for general use due to its small file size and wide device compatibility.
Higher quality formats like FLAC are available if you need uncompressed audio for archival purposes, though they consume more storage and bandwidth.
Scalability
The API handles up to 60 requests per minute per key, which is suitable for most startup-scale audioguide deployments. For larger volumes, you can issue additional keys.
Text is automatically split into 4,096-character segments and joined, ensuring that long tour scripts do not exceed input limits or cause errors.
Accessibility
Speed control allows users to adjust playback from 0.25x to 4.0x, catering to diverse hearing needs. Clear, neutral voices like Atlas or Sage provide high readability for historical content.
Multiple audio formats ensure compatibility with assistive technologies and screen readers that may process audio files directly.
Data Privacy
Input text is used solely for synthesis and is not used for training models. Generated audio is returned in the response and not stored on our servers.
Request metadata, including time and character count, is retained only for billing purposes, ensuring minimal data retention.
Customer Support
Support is available via email only. We do not offer live chat or phone support.
Comprehensive documentation is available at /docs/, providing clear examples and troubleshooting steps for common integration issues.
Integration Ease
The endpoint accepts standard parameters, making it easy to integrate with existing web or mobile applications. Errors return clear HTTP status codes and messages.
The /get-api-key/ page provides a ready-to-use curl example, allowing you to verify your API key and balance before writing custom code.
Final Recommendation
MuseumEcho is ideal for startups building audioguides, offering reliable performance and cost-effective billing. The lack of monthly fees and simple pricing model makes it easy to predict expenses.
With support for 23 languages and straightforward integration, it provides a solid foundation for accessible, engaging tourism content.
image:
Audio Formats
Selecting the right audio format ensures your museum audioguide files load quickly on mobile devices while maintaining clarity. MuseumEcho supports MP3, WAV, Opus, FLAC, and PCM, letting you balance quality against bandwidth constraints for tourist networks.
MP3 compatibility
MP3 is the default choice for broad compatibility across all web players and mobile apps. It offers excellent compression for speech, making it ideal for on-demand audioguide streams.
High quality options
For archival tours or high-fidelity experiences, WAV and FLAC provide lossless audio. These formats preserve every nuance of the voice, such as Aria’s warm narration, ensuring pristine sound quality for premium exhibits.
File size considerations
Larger files like WAV require more storage and bandwidth. Choose Opus for efficient bandwidth usage, or MP3 for a balanced approach. Always test file sizes against your target tourist device capabilities.
Scalability
MuseumEcho handles high-volume audioguide requests by processing synthesis sequentially rather than in parallel. This ensures stable resource usage, though requests may queue under heavy load. The system processes one request at a time, meaning longer texts or concurrent users experience a linear wait time proportional to the number of pending items.
Handle peak traffic
During peak tourist seasons, your API key allows 60 requests per minute. This limit is sufficient for most startup-scale audioguide deployments. If traffic exceeds this, requests wait in a queue rather than failing immediately.
Queue management
Requests are processed one after another. Short phrases take a few seconds, while longer texts take time proportional to their length. Under load, you may notice delays as earlier requests complete.
Consistent performance
Performance remains predictable: roughly real-time generation (25 characters per second). The queue ensures fair ordering without dropping requests. Failed requests do not consume credits, maintaining accurate billing even during busy periods.

Accessibility
Accessibility is a core requirement for museum audioguides, ensuring your content reaches visitors with varying needs. Our API generates clear, natural-sounding speech that avoids the robotic tone of older systems, making historical narratives and exhibit descriptions easier to comprehend for all users.
Clear speech
The eight voice presets are designed for clarity and natural rhythm, reducing listener fatigue during long tours. Whether using a warm narrator voice or a calm instructional tone, the audio remains distinct and easy to follow.
Speed control
Visitors can adjust playback speed to match their comprehension level. The API supports a speed range from 0.25x to 4.0x, allowing you to generate audio optimized for quick scanning or detailed listening sessions.
Format variety
Support for multiple formats like MP3, WAV, and FLAC ensures compatibility with various assistive technologies and legacy museum hardware. This flexibility allows you to deliver high-quality audio without worrying about device-specific constraints.
Data Privacy
MuseumEcho treats your input data with strict operational boundaries. The text you submit is used exclusively for the immediate generation of the audio file. We do not use your museum tour scripts, guide narratives, or tourist feedback to train or improve our voice models. Your content remains yours.
No data training
Unlike many consumer-grade AI services, we do not ingest your input text into our training datasets. This ensures that proprietary tour guides or unique historical narratives you provide remain distinct from our general model data. Your intellectual property stays isolated from our training pipeline.
Minimal storage
We retain minimal metadata strictly for billing and usage tracking. The generated audio files are returned in the response stream and are not permanently stored on our servers after delivery. Only the time, character count, and status of the request are kept to verify your account balance.
- Input text is discarded after synthesis
- Audio files are not archived
- Metadata kept only for billing verification
Secure transmission
All API requests and audio responses are transmitted over secure HTTPS connections. This ensures that your tour data and generated audio streams are protected from interception during transit between your application and our API endpoint.
Customer Support
Support for MuseumEcho is handled exclusively via email. There is no phone number or live chat available, so all inquiries are managed through written correspondence. This approach keeps overhead low, which helps maintain our competitive per-character pricing for startups building audioguides.
We provide comprehensive documentation to help you integrate the API quickly. The docs include ready-to-use curl examples, clear endpoint definitions, and error code explanations. This ensures you can resolve technical issues independently without waiting for a conversation.
Email support
All support requests are sent via email. We do not offer phone support or live chat, ensuring that every query is documented and traceable. This method allows our team to provide detailed, written answers that you can reference later during development.
- No phone number available
- No live chat widget
- Written record of all interactions
Documentation quality
Our documentation covers all API endpoints, including voice lists, models, and speech generation. It includes practical examples for common tourism use cases, such as multi-language museum tours. You can test the API directly using the provided curl commands.
- Complete endpoint reference
- Curl examples included
- Error code explanations
Response time
While we do not guarantee a specific response window, our team aims to reply to emails within 24 hours during business days. For urgent issues, clearly state the problem in your email to help us prioritize your request effectively.
You can also troubleshoot many issues by reviewing our detailed error messages and the OpenAI-compatible SDK behavior, which reduces the need for direct support contact.
- Typical response within 24 hours
- Business days only
- Self-service docs available
Integration Ease
MuseumEcho is designed to integrate seamlessly with your existing workflow. By mimicking the OpenAI speech endpoint structure, you can connect using the official OpenAI SDKs simply by changing the base URL to https://api.siap234.cc/v1. This means you likely already have the code ready to go, reducing development time for your audioguide backend.
The API uses straightforward HTTP requests, making it easy to implement in any language or framework. You send a POST request with your text and voice parameters, and receive an audio file. The system handles the complexity of synthesis, letting you focus on curating the tour experience for your visitors.
OpenAI SDK ready
Use the standard OpenAI Python or Node.js libraries. Just update the base URL to https://api.siap234.cc/v1 and use your MuseumEcho API key. This compatibility ensures you can leverage familiar authentication methods and request structures without learning a new library.
- Compatible with official OpenAI SDKs
- Change base_url to https://api.siap234.cc/v1
- Use your site-specific API key
Simple endpoints
The primary endpoint is POST https://api.siap234.cc/v1/audio/speech. Send a JSON body with model, input, voice, and optional parameters like speed or language. The API returns the audio file directly in the response, simplifying your code logic.
- Single endpoint for audio generation
- JSON request body
- Direct audio file response
Clear errors
The API returns standard HTTP status codes to indicate success or failure. If a request fails, you are not charged, and the error message helps you quickly identify issues like invalid parameters or rate limits, ensuring smooth debugging during integration.
- Standard HTTP status codes
- No charge on failure
- Helpful error messages
Final Recommendation
MuseumEcho is purpose-built for startups developing audioguides and accessible travel content. By handling voice generation, the API lets teams focus on user experience rather than infrastructure. The straightforward integration with existing OpenAI SDKs and simple endpoints reduces development time, allowing rapid prototyping and deployment of tourism applications without complex setup.
Best for startups
MuseumEcho is purpose-built for startups developing audioguides and accessible travel content. By handling voice generation, the API lets teams focus on user experience rather than infrastructure. The straightforward integration with existing OpenAI SDKs and simple endpoints reduces development time, allowing rapid prototyping and deployment of tourism applications without complex setup.
- Simple JSON API compatible with OpenAI SDKs
Cost-effective
Usage-based billing at $0.01 per 1,000 characters eliminates monthly overhead. There are no minimum spend requirements, subscriptions, or seats to manage. A $0.50 free trial provides 50,000 characters, enabling immediate testing. Top-ups via USTRC-20 are processed automatically, ensuring continuous service without administrative delays.
Reliable performance
The service maintains consistent quality with 60 requests per minute and automatic queue management. Texts are split into 4,000-character chunks to ensure stable generation. Audio files are delivered directly in the response, supporting formats like MP3 and WAV for broad compatibility in tourism apps and audioguide platforms.
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. For archival tours or high-fidelity experiences, WAV and FLAC provide lossless audio.
23 languages
Any voice speaks any of these languages.
