Frequently asked questions
Is Google text to speech app better than a cloud API?
The cloud API offers 23 languages and 8 distinct voice presets, whereas standard apps often limit language choices. Our API supports formats like MP3, WAV, and FLAC, providing greater flexibility for web integration. You can control speed precisely between 0.25 and 4.0. Unlike app-based solutions, this API allows programmatic access via simple HTTP requests, making it suitable for scalable, multi-language accessibility tools.
How does cloud TTS help dyslexic readers?
Cloud TTS converts text into clear audio, reducing visual strain and supporting auditory learning. Our voices, like Aria and Luna, provide warm, clear narration that aids comprehension. The API handles up to 4096 characters per request, allowing you to break long texts into manageable segments. This flexibility helps users process information at their own pace without visual fatigue.
Can I use this API for educational apps?
Yes, the API is ideal for educational apps. It supports 23 languages, including English, Spanish, and French, catering to diverse student needs. You can integrate it via standard HTTP requests or the OpenAI SDK. The pricing model charges only for characters used, making it cost-effective for schools. Input text is not used for training, ensuring student privacy.
What languages are supported for dyslexia tools?
We support 23 languages: 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 specified, it guesses from the script, defaulting to English for Latin text.
Is the API expensive for small projects?
The API costs $10 per 1 million characters, or $0.01 per 1,000 characters. Failed requests are free, so you only pay for successful generations. You start with a $0.50 free trial (50,000 characters). There are no monthly plans or minimum spends, making it affordable for small projects. You can top up with USDT on the TRON network.
Do I need coding skills to use the API?
Basic coding skills help, but no advanced expertise is required. You can use the OpenAI SDK by changing the base URL, or send simple HTTP POST requests. The endpoint accepts JSON bodies with text, voice, and format parameters. Many no-code platforms can integrate via HTTP connectors. We provide ready curl examples to help you get started quickly.
How fast is the audio generation?
Audio generation is roughly real-time for long texts, processing about 25 characters per second. Short phrases may take a few seconds. Requests are processed sequentially, so under heavy load, you might experience slight queueing delays. Despite this, the speed is sufficient for most educational and accessibility applications where immediate playback is not critical.
Can I adjust the speaking speed?
Yes, you can adjust the speaking speed between 0.25 and 4.0. This allows dyslexic readers to control the pace of audio playback. Faster speeds help users who process information quickly, while slower speeds aid those who need more time to absorb spoken words. This flexibility enhances the listening experience and reduces cognitive load during reading.
Is my input text stored after generation?
No, your input text is used only to produce the audio and is not stored for training purposes. The generated audio is returned in the response and not stored on our servers. We keep request metadata, such as time, character count, and status, strictly for billing purposes. This ensures your content remains private and secure.
What happens if the API request fails?
If synthesis fails, the charge is returned in full. You are not billed for unsuccessful requests. This ensures you only pay for usable audio files. You can retry the request with adjusted parameters if needed. The system provides clear status codes to help you debug issues, ensuring a reliable experience for your accessibility applications.
Are there hidden fees in the pricing?
There are no hidden fees. The price is $10 per 1 million characters, with spaces and punctuation counting as characters. Failed requests are free. There are no monthly plans, seats, or minimum spends. You can top up with USDT on the TRON network. Balance does not expire, and you pay only for what you use.
Can I use the voices commercially?
The voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain audiobooks. You can use the generated audio commercially. Each file carries an inaudible watermark marking it as synthetic speech. This makes the API suitable for educational, commercial, and accessibility projects.
How do I start with a free trial?
Sign up on our /get-api-key/ page using your Google account. You receive $0.50 of credit, valid for 7 days, which covers about 50,000 characters. Accounts created with email and password start without trial credit. You can then top up with USDT on the TRON network to continue using the API for your projects.
What is the character limit per request?
Each request can handle up to 4096 characters of text. For longer texts, you should split them into parts of this size and join the resulting audio files. This limit ensures efficient processing and maintains audio quality. You can adjust the speed and voice for each segment to create a cohesive listening experience for your users.
First request
curl
curl https://api.playtbjee.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.mp3Why Choose a Cloud API Over a Mobile App
Mobile apps require individual downloads and updates on every device, creating friction for dyslexic readers who need immediate access. A cloud API delivers audio directly to your web interface, eliminating installation steps and ensuring the latest voice models are always available without user intervention.
This approach removes device-specific constraints, allowing a single integration to serve users on desktops, tablets, and smartphones seamlessly. The API handles the heavy lifting of audio synthesis, providing a consistent listening experience regardless of the hardware being used.
No installation required for web-based tools
Users access content instantly through their browser. There is no need to navigate app stores, manage permissions, or wait for background updates. This immediacy is crucial for educational tools where reading practice should begin the moment the page loads.
For no-code creators, this means embedding TTS directly into existing websites or learning platforms. Readers encounter text and audio simultaneously, reducing the cognitive load of switching between separate applications.
- Instant access via standard web browsers
- No app store dependencies or update cycles
- Embed directly into existing learning management systems
Consistent audio quality across devices
The API uses a single engine for all requests, ensuring that the voice characteristics remain identical whether accessed from an iPhone, an Android tablet, or a Windows PC. This consistency helps build auditory familiarity, which is vital for dyslexic readers who rely on predictable speech patterns.
Unlike local app versions that may vary by operating system or version, the cloud endpoint returns standardized audio files. This uniformity supports better comprehension and reduces the distraction of unexpected changes in voice tone or speed between devices.
- Single engine ensures uniform voice output
- Identical audio experience on iOS, Android, and desktop
- Reduces cognitive load through predictable speech patterns
Scalable for growing user bases
As your user base grows, you do not need to distribute new app builds or manage device-specific compatibility issues. Requests are processed one after another, with a rate limit of 60 requests per minute.
This scalability allows you to add features or change voice presets globally without requiring user action. Whether you have ten readers or ten thousand, the integration architecture remains the same, simplifying long-term maintenance for no-code developers.
- Handles concurrent requests via queue system
- Global updates without user intervention
- Simplifies maintenance as user base expands
Voice Clarity for Dyslexic Users
Clear audio output without background noise helps readers focus on text structure. Our API delivers clean WAV or MP3 files, ensuring that phonetic nuances remain distinct. This clarity reduces the cognitive load required to decode written language, making long-form reading less exhausting for users with dyslexia.
Natural pacing reduces cognitive load
Adjustable speed (0.25x–4.0x) lets users control the rhythm of speech. This flexibility allows readers to match audio to their personal processing speed, preventing information overload. Consistent pacing ensures that sentence boundaries remain clear, aiding comprehension without sudden shifts in tone or volume.
- Adjustable speed from 0.25x to 4.0x
- Consistent tone across long texts
Clear enunciation aids phonemic awareness
Voices like Aria and Luna provide warm, clear narration. Each voice is based on licensed recordings, ensuring natural but precise articulation. This clarity helps users distinguish between similar sounds, supporting phonemic awareness without the artifacts common in lower-quality TTS engines.
- 8 preset voices with distinct styles
- Licensed recording base for natural sound
Consistent voice identity builds familiarity
Using the same voice across different reading sessions builds familiarity. Users can choose from eight presets, such as the calm Sage or friendly Milo, to create a consistent listening experience. This consistency reduces the mental effort of adapting to new voices, allowing deeper focus on content.
- 8 distinct voice presets
- Same voice across all sessions
Language Support for Diverse Readers
The API supports 23 languages, including English, Spanish, French, German, and Arabic. This allows no-code creators to build reading experiences for diverse student groups without managing separate voice models. Each voice can speak any of the supported languages, ensuring consistent audio quality regardless of the reader’s native tongue.
Support for 23 major languages
We cover major global languages like Chinese, Japanese, Hindi, and Swahili. If a language is not in the list—such as Vietnamese, Thai, or Ukrainian—it is not supported. This clarity helps you avoid unexpected failures when serving non-standard dialects or regional variants outside the supported set.
- Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, Turkish
Accents are not guaranteed
Voices are based on licensed recordings from LibriVox, providing clear, standard enunciation. However, specific accent variations are not guaranteed. The system prioritizes clarity and consistent pacing, which reduces cognitive load for dyslexic readers, rather than offering nuanced regional dialects.
Automatic language detection for mixed content
If you do not set the language field, the API guesses the language from the text script. Latin script defaults to English. For non-English Latin text, you should explicitly set the language code to ensure accurate pronunciation. This prevents misreading mixed-content inputs.
Accessibility Features in TTS
TTS APIs offer adjustable playback speeds ranging from 0.25x to 4.0x, allowing dyslexic readers to customize audio pacing for better comprehension. This control helps reduce cognitive load by letting users slow down complex texts or speed through familiar content, ensuring a personalized reading experience that adapts to individual processing needs.
Adjustable speed from 0.25x to 4.0x
Users can fine-tune audio speed to match their reading comfort level. This flexibility supports diverse learning styles, enabling slower playback for difficult passages or faster speeds for review, without sacrificing clarity or introducing unnatural distortions common in lower-quality engines.
- Speed range: 0.25x to 4.0x
- Instant adjustment during playback
Clean audio output without background noise
Generated audio files are clean and free from background noise, ensuring clear enunciation that aids phonemic awareness. The consistent voice identity builds familiarity for regular users, while the absence of distracting artifacts helps maintain focus on the text content during long reading sessions.
Simple integration into existing reading apps
The API uses standard JSON requests compatible with the OpenAI SDK, making it easy for no-code users to embed audio into existing web applications. This simplicity allows creators to add accessible TTS features without building complex infrastructure from scratch, supporting rapid deployment of reading tools.
- Standard JSON request format
- OpenAI SDK compatible
- No official SDK required
Pricing Transparency for Non-Profits
Pricing is straightforward: $10 per million characters, or $0.01 per 1,000 characters. Spaces and punctuation count toward this total, ensuring predictable costs for budgeting. Failed requests incur no charge, protecting your funds during testing or API hiccups.
Pay only for characters used
You pay strictly for what you consume. With a free trial of $0.50 (approx. 50,000 characters) valid for 7 days via Google sign-in, you can test clarity without commitment. Email-based accounts start without trial credit.
- $0.01 per 1,000 characters
- Failed requests are free
- Balance does not expire
No monthly subscription fees
There are no seats, minimum spends, or recurring billing cycles. You can top up via USDT (TRC-20) on the TRON network, with a $5 minimum. Credits are automatic and available within minutes, avoiding invoice delays or VAT complexities.
Free trial available for testing
New Google-sign-in accounts receive $0.50 in credit, allowing immediate evaluation of voice quality and integration speed. This allows non-profits to verify audio clarity for dyslexic readers before committing to larger top-ups.

Technical Requirements for No-Code Users
You do not need to write complex code to integrate our API. The service uses standard HTTP requests that connect directly to your existing web forms or no-code platforms. This simplicity allows you to add high-quality audio reading capabilities to your projects without hiring a dedicated engineering team.
The interface is designed for clarity, ensuring that even users with minimal technical experience can generate speech files reliably. By relying on straightforward web protocols, we remove the friction often associated with API adoption, letting you focus on content rather than configuration.
Simple REST API integration
Our endpoint accepts standard POST requests, making it compatible with most no-code automation tools like Zapier or Make. You simply send text and receive an audio file in return, requiring no middleware or custom server infrastructure.
The process is linear: input text, specify your preferred voice and format, and receive the audio. This direct approach minimizes points of failure and keeps your reading experience consistent across different devices.
- No server setup required
- Compatible with no-code platforms via HTTP
- Straightforward request-response workflow
Supports standard JSON requests
We use a JSON body structure that is easy to construct visually in most no-code builders. You only need to provide the text, voice selection, and output format, keeping the data payload small and manageable.
This standardized format ensures that your integration remains stable even as you scale. There is no need to parse complex XML or handle binary streams manually, reducing the chance of errors during audio generation.
Works with OpenAI SDK for easy setup
If you prefer a library-based approach, our API follows the same request shape as the OpenAI speech endpoint. You can use the official OpenAI SDK by simply changing the base URL to our API address.
This compatibility allows you to leverage existing code snippets and documentation you may already have. It provides a familiar development experience while accessing our specific voice library and pricing model.
Data Privacy for Student Data
For educational platforms, knowing how student data is handled is critical. Our API treats input text as a transient resource, ensuring that the content read aloud by dyslexic students is not ingested into training datasets. This preserves the integrity of private reading materials and reduces compliance concerns for schools managing sensitive student information.
Input text not used for training
The text you send to generate speech is used solely for the immediate synthesis of the audio file. We do not repurpose your input data to improve our voice models or for other commercial purposes. This ensures that your students' reading materials remain private and distinct from our general training corpus.
Audio generated on demand and not stored
Once the audio file is returned in the API response, it is not stored on our servers. The generated file exists in your application’s memory or storage, giving you full control over retention periods. This on-demand generation minimizes the risk of lingering audio files containing student voices or content on our infrastructure.
Metadata kept only for billing purposes
We retain minimal metadata, including the timestamp, character count, and request status, strictly for accurate billing and usage tracking. This data does not include the actual content of the text or the resulting audio. It is kept only as long as necessary to verify charges and resolve any account discrepancies.
Performance and Reliability
For short phrases, synthesis typically completes in a few seconds, while longer texts process at roughly real-time speed (approximately 25 characters per second). Requests are processed sequentially, meaning under heavy load, a request may wait in a queue before generation begins.
We do not offer a formal Service Level Agreement (SLA) or uptime guarantee. The system remains operational without strict commercial promises, providing consistent performance for no-code creators who prioritize predictable character-based pricing over guaranteed 99.9% availability metrics.
Real-time generation for short texts
Short phrases typically finish in a few seconds. Longer texts generate at approximately real-time speed, processing about 25 characters of text per second of audio output. This ensures that reading flows naturally without significant delays for standard content lengths.
Queue handling during high load
Requests are processed one after another. If many users generate audio simultaneously, your request may wait in a queue. This sequential processing ensures stable audio quality even when the API receives more traffic than the standard 60 requests per minute limit.
Consistent uptime without SLA guarantees
We do not provide a formal SLA or uptime guarantee. The service remains consistently available for no-code users who value transparent pricing and straightforward integration over commercial reliability contracts. You can rely on the API for daily educational content generation without enterprise overhead.
Customer Support for Developers
Support is provided exclusively via email, ensuring that technical queries are handled with care and without the pressure of live chat windows. This approach allows our team to provide detailed, written responses that developers can reference later during integration or debugging phases.
Email-only support for technical issues
We do not offer phone lines or real-time chat, keeping support focused on substantive technical help. You can reach us for API questions, voice selection advice, or integration troubleshooting. Our email support team reviews each ticket thoroughly to ensure accurate, context-aware answers.
- No waiting on hold
- Written record of solutions
- Focused technical assistance
Clear documentation for integration
Our documentation at /docs/ explains the REST API structure, request parameters, and response formats clearly. It includes examples for standard JSON requests and shows how to use the OpenAI SDK with our base URL. This reduces the learning curve for no-code users and developers alike.
Direct contact for billing inquiries
For questions about your USDT top-ups, character counts, or trial credit, you can contact us directly via email. We handle billing transparently, so you can resolve any account issues quickly without navigating complex support queues.
Listen to the 8 voices
Each sample below was generated by this API from the same sentence.
23 languages
Any voice speaks any of these languages.
