Frequently asked questions
Is this the best text to audio app for large-scale NGO projects?
We do not claim to be the best. EchoServe provides an independent, fact-based review of cloud TTS providers. Our API offers consistent pricing at $0.01 per 1,000 characters and supports 23 languages. We focus on real-world usability, licensing clarity, and cost-efficiency for public service teams evaluating TTS solutions.
Which voices are best for public service announcements?
For public service announcements, atlas (neutral, news) and sage (calm, instructional) are suitable for clear information delivery. Felix (energetic, promo) works for urgent alerts. All eight voices support all 23 languages, allowing you to select the tone that best fits your specific communication context and audience needs.
Does the API support all 23 languages equally?
The API supports 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. If the language is not set, it is guessed from the script.
How do I handle texts longer than 4096 characters?
Split your text into parts of up to 4096 characters. Send each part as a separate request. Then, join the resulting audio files. This ensures compliance with the character limit per request while allowing you to generate audio for longer documents or extensive public service announcements.
What happens if a synthesis request fails?
If synthesis fails, the charge is returned in full. Failed requests are free. You are only charged for successful audio generation. This ensures that network issues or processing errors do not result in unnecessary costs for your account balance, maintaining predictable budgeting for your API usage.
Is the audio output royalty-free for public use?
Voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain audiobook readings. The generated audio carries an inaudible watermark marking it as synthetic speech. While the source is public domain, the specific synthetic output should be reviewed for your compliance requirements regarding public distribution.
Can I use the API for emergency broadcast systems?
The API is not guaranteed for emergency broadcast systems. There is no SLA or uptime guarantee. Requests are processed sequentially, so under load, a request may wait in a queue. For critical real-time needs, consider the potential latency and lack of dedicated infrastructure guarantees.
Do I need to pay VAT on the API usage?
No. We do not provide invoices with VAT. Payments are made via USDT on the TRON network. There are no monthly plans, seats, or minimum spends. The pricing is straightforward at $10 per 1 million characters, with no additional tax fees added to your usage costs.
How fast is the audio generation for long documents?
Generation is roughly real time, about 25 characters of text per second of generation. Short phrases take a few seconds. Requests are processed one after another, so under load, a request may wait in a queue. This speed is consistent across all supported voices and languages.
Is there a free trial available for testing?
Yes, a free trial of $0.50 credit (about 50,000 characters) is valid for 7 days. This is given when you sign in with Google. Accounts created with email and password start without trial credit. This allows product teams to evaluate the API before committing to top-ups.
What is the minimum top-up amount via USDT?
The minimum top-up amount is $5. Payments are accepted via USDT on the TRON network (TRC-20) only. Credits are added automatically within minutes after the transfer. There are no subscriptions or invoices, and your balance does not expire, allowing flexible funding for your API usage.
Does the API handle non-Latin scripts automatically?
If the language is not set, it is guessed from the script. Latin text defaults to English. For non-English Latin-script text, you must set the language parameter. This ensures accurate pronunciation for the 23 supported languages, including Arabic, Chinese, Hebrew, Hindi, Japanese, Korean, and Russian.
Are there any hidden fees for high-volume usage?
No. The price is $0.01 per 1,000 characters. There are no monthly plans, seats, or minimum spends. Failed requests are free. Spaces and punctuation count as characters. The rate remains constant regardless of volume, providing predictable cost-efficiency for large-scale NGO projects and public service deployments.
How do I reset my API key if it is compromised?
A new key can be issued any time from your account dashboard. When a new key is issued, the old one stops at once. This ensures immediate security if a key is compromised. You can manage your active key directly through the /get-api-key/ page on our site.
First request
curl
curl https://api.playtk77.com/v1/audio/speech \
-H "Authorization: Bearer $TTS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"tts-1","voice":"aria","input":"Hello from the API.","response_format":"mp3"}' \
--output hello.mp3API Overview
EchoServe provides a cloud-based text-to-speech API designed for public services and NGOs needing reliable audio generation without infrastructure overhead. The service accepts text input and returns synthesized audio files via a simple HTTP request, integrating seamlessly into existing web or mobile applications used for accessibility and public information dissemination.
The endpoint is fully compatible with the OpenAI speech API specification, allowing teams to leverage familiar SDKs and development patterns. This compatibility reduces integration friction, enabling product teams to switch providers or test alternatives without rewriting core audio generation logic.
Cloud-based speech synthesis ['The API handles all processing in the cloud, eliminating the need for local hardware or specialized voice engines. Requests are processed one after another, so under load a request may wait in a queue.', 'Typical speed is roughly real time on long texts (about 25 characters of text per second of generation); short phrases take a few seconds. Failed requests incur no charge, ensuring cost efficiency for high-volume public service announcements.'] ['No local server maintenance required', 'Automatic handling of request queuing']
OpenAI-compatible endpoint ['The API mirrors the OpenAI speech endpoint structure, allowing developers to update the base_url to https://api.playtk77.com/v1 and use the official OpenAI SDKs directly. This ensures that existing codebases can adopt the service with minimal code changes.', 'Authentication uses a standard Bearer token, maintaining security standards familiar to most engineering teams. The single active key per account simplifies credential management for small NGO teams.'] ['Uses OpenAI SDK compatibility', 'Standard Bearer token auth']
Standard JSON body format ['Requests use a standard JSON body containing model, input, voice, and optional parameters like speed and language. This structure is predictable and easy to debug, supporting rapid prototyping for accessibility overlays.', 'The endpoint returns the audio file directly in the response, allowing immediate playback or storage. Supported formats include MP3, WAV, Opus, FLAC, and PCM, covering most public service distribution needs.'] ['JSON request body', 'Direct audio file response']
Accessibility & Languages
EchoServe supports 23 languages, including 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, ensuring broad coverage for diverse public service audiences.
If language is not set, it is guessed from the script (Latin text defaults to English). For non-English Latin-script text, set the language parameter explicitly to ensure accurate synthesis.
23 supported languages
The platform supports 23 languages, including 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, ensuring broad coverage for diverse public service audiences.
Latin script default handling
The API guesses the language from the script, defaulting to English for Latin text. For non-English Latin-script text, set the language parameter explicitly to ensure accurate synthesis.
Manual language override
You can override the detected language by providing an ISO code in the request. This is essential for texts that might otherwise be misidentified by the default heuristic.
Not supported: Vietnamese, Indonesian, Thai, Ukrainian, Romanian, Czech, Bengali and all others not in the list.
- Set
languageparameter explicitly for non-English Latin text. - ISO code required for precise language targeting.

Voice Presets
EchoServe provides eight distinct voice presets based on licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain audiobook readings. These voices support all 23 listed languages, allowing NGOs to localize content without additional training data.
Female voices: Aria, Nova
Aria offers a warm, clear narrator style ideal for detailed public announcements or educational content. Nova provides a bright, upbeat tone suitable for engaging community updates or dynamic service notifications.
Male voices: Felix, Milo
Felix delivers an energetic, promo-style voice effective for time-sensitive alerts or campaign highlights. Milo uses a friendly, conversational tone that enhances accessibility for routine information dissemination.
Neutral and deep options
Atlas provides a neutral, news-style delivery for standard informational broadcasts. Orion offers a deep, documentary tone well-suited for longer audiobooks or historical content generated by NGOs.
Licensing & Data
EchoServe’s speech synthesis engine is built on licensed recordings from LibriTTS-R, sourced directly from LibriVox public-domain audiobook readings. This foundation ensures that the underlying voice models are derived from legally cleared material, providing a clear audit trail for compliance teams in public services and NGOs who need to verify the origin of synthetic media assets.
The source material is released under the Creative Commons Attribution 4.0 International license. This standardized open license allows for broad commercial and non-commercial use, provided attribution is maintained. For NGOs and public sector projects, this reduces the complexity of rights management compared to proprietary voice datasets that may carry restrictive usage clauses or require per-seat licensing fees.
LibriTTS-R source material
The engine uses recordings from LibriTTS-R, a structured dataset designed for high-quality speech synthesis, from LibriVox public-domain audiobook readings. This specific dataset provides the acoustic foundation for all eight voice presets, ensuring consistent audio quality across different languages and use cases without requiring additional data licensing agreements.
- Source: LibriVox public-domain audiobook readings
- Dataset: Structured LibriTTS-R format
- Origin: Dedicated speech synthesis training data
CC BY 4.0 recordings
Source material originates from LibriVox public-domain audiobook readings, released under the Creative Commons Attribution 4.0 International license. This means the underlying voice recordings are free from complex royalty structures, allowing your organization to generate audio content without worrying about ongoing licensing fees or restrictive derivative work clauses common in enterprise TTS solutions.
- License: CC BY 4.0 International
- Origin: LibriVox public-domain readings
- Usage: Broad commercial and non-commercial rights
No training on input text
Input text is used only to produce the audio and is not used for training. This distinction is critical for NGOs handling sensitive community data or public sector documents with privacy constraints. Unlike some competitors who may use customer data to improve their base models, EchoServe treats each request as a discrete transaction, ensuring your content remains proprietary.
Pricing Model
EchoServe charges $0.01 per 1,000 characters, making costs predictable for budget-conscious NGOs. This per-character model ensures you only pay for actual usage, with failed requests refunded in full.
Per character billing
Each character, including spaces and punctuation, counts toward your total. For example, 1 million characters cost $10, allowing precise cost forecasting for large-scale accessibility projects or audiobook generation.
No monthly subscriptions
There are no recurring fees, seats, or minimum spend requirements. You maintain a balance that does not expire, paying only when you generate audio. This flexibility suits NGOs with variable traffic patterns.
USDT TRC-20 payments
Top-ups are processed via USDT on the TRON network (TRC-20) with a $5 minimum. Funds are credited automatically within minutes, avoiding traditional banking delays or credit card processing fees.
- Minimum top-up: $5
- Network: TRON (TRC-20)
- Crediting time: ~minutes

Technical Limits
Understanding the technical boundaries of the EchoServe TTS API is essential for planning reliable audio generation workflows in public service applications. The system operates with specific constraints on input length, request frequency, and processing latency that directly impact user experience and integration design.
4096 character max input
For each individual API call, the maximum input text length is capped at 4,096 characters. This limit applies to the input field in the JSON body, meaning longer documents or transcripts must be programmatically split into manageable segments before synthesis.
60 requests per minute
The API enforces a rate limit of 60 requests per minute per active API key. For new accounts before the first top-up, this limit is stricter at 10 requests per minute. Exceeding these thresholds will result in temporary rejection of subsequent requests until the window resets.
Real-time processing speed
Typical speed is roughly real time on long texts (about 25 characters of text per second of generation); short phrases take a few seconds. However, requests are processed sequentially, so under high load, a request may wait in a queue before synthesis begins. Short phrases may take a few seconds to generate.
Supported Formats
The API returns audio in MP3, WAV, Opus, FLAC, or PCM formats. MP3 and WAV are standard for most web players and CMS platforms. Opus and FLAC provide efficient compression for storage.
MP3 and WAV output
MP3 offers universal compatibility with low file sizes. WAV provides lossless quality. Both formats are suitable for public service announcements and web overlays.
- MP3: Ideal for web playback and mobile apps.
- WAV: Best for high-fidelity archiving or editing.
Opus and FLAC options
Opus delivers high-quality audio at low bitrates, reducing bandwidth costs for NGOs. FLAC provides lossless compression.
- Opus: Best for low-bandwidth environments.
- FLAC: Best for archival quality.
PCM raw audio
PCM returns raw uncompressed audio data. This format is useful for low-level audio processing or custom playback engines. It skips container overhead for direct signal handling.
- PCM: Raw, uncompressed audio data.
- Use case: Custom audio pipelines.
Integration
EchoServe’s API mirrors the standard OpenAI speech endpoint, allowing teams to reuse existing client libraries with minimal code changes. This compatibility reduces integration friction for product teams already familiar with the OpenAI ecosystem.
Authentication relies on a simple Bearer token. You provide your unique API key in the Authorization header, ensuring secure access to the speech synthesis endpoint for your public service or NGO applications.
OpenAI SDK compatibility
The API accepts the same JSON body structure as the OpenAI speech endpoint. This means you can use official OpenAI SDKs by simply pointing them to our base URL, avoiding the need for custom HTTP clients.
- Reuses existing OpenAI client libraries
- Standard JSON request body
- Minimal code adjustments required
Base URL configuration
Configure your SDK’s base URL to https://api.playtk77.com/v1. This single change directs all requests to our processing infrastructure while maintaining the standard endpoint path /v1/audio/speech.
Bearer token authentication
Include your API key in the Authorization: Bearer tts-... header. Each account holds one active key, which can be rotated instantly if compromised, ensuring secure access for your integration.

Use Cases
EchoServe enables public services to convert static text into clear audio quickly. This supports compliance with accessibility standards without requiring complex infrastructure. The API handles large volumes efficiently, ensuring reliable delivery for civic communications.
For NGOs, generating audiobooks from published texts becomes cost-effective. With no monthly subscriptions, teams can scale audio production based on actual usage. This model suits organizations with variable content needs and limited budgets.
Public announcement systems
Use the API to convert emergency alerts or daily briefings into audio files. The system processes requests sequentially, ensuring consistent output for public displays.
The 60 requests per minute limit allows for batch processing of multiple announcements. Audio files are ready for immediate playback on digital signage or web players.
- Convert text to MP3 or WAV for web integration
- Batch process announcements within rate limits
- No server maintenance required for audio generation
Audiobook generation for NGOs
Leverage the 4096 character limit per request to segment longer texts. Combine generated audio files to create complete chapters or full books.
The per-character pricing ensures you only pay for what you use. This is ideal for organizations with sporadic publishing schedules.
- Segment text under 4096 characters
- Combine audio files for full books
- Pay only for generated content
Accessibility web overlays
Integrate the TTS endpoint into websites to provide audio versions of articles. This supports users with visual impairments or reading difficulties.
The API’s compatibility with standard SDKs simplifies integration into existing web frameworks. Users can toggle audio playback directly on the page.
- Integrate TTS into existing web platforms
- Support multiple languages for diverse audiences
- Ensure compliance with accessibility guidelines
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Our platform empowers public service teams to deliver seamless, inclusive digital experiences for every citizen, everywhere.
23 languages
Any voice speaks any of these languages.
Sources and further reading
- Wikipedia
- Node.js documentation
- LibriTTS-R corpus (OpenSLR 141)
- TRON developer hub: TRC-20
- curl documentation
- W3C WAI: making audio and video accessible
- Python documentation
- LibriTTS-R paper (arXiv 2305.18802)
- OpenAI API reference: create speech
- MDN: Web Speech API
- FFmpeg documentation
- Creative Commons Attribution 4.0
