Frequently asked questions
What is a text-to-speech API?
A text-to-speech API converts written text into audio files via a simple HTTP request. You send text and receive an audio file, making it easy to integrate reading capabilities into websites or apps without complex infrastructure.
How does TTS help dyslexia?
TTS supports readers by converting text to speech, reducing visual stress and improving comprehension. Our voices offer clear, distinct tones, and you can adjust speed to match individual processing needs, aiding focus and reducing reading fatigue.
Is an API better than a mobile app?
An API offers greater flexibility for no-code creators to embed audio directly into web content. Unlike apps, it works across devices and platforms without requiring separate downloads, ensuring consistent access to reading support wherever your content lives.
What are the technical requirements?
You need an API key and basic HTTP knowledge. Send a POST request with your text and voice selection. The official OpenAI SDKs work by changing the base URL, requiring no custom software or complex integrations.
How do I choose the right voice?
You can adjust speed between 0.25 and 4.0. This allows users with dyslexia to slow down audio for better comprehension or speed it up for efficiency, ensuring the audio matches their personal reading pace and comfort level.
Can I control the speaking speed?
We support 23 languages including English, Spanish, French, German, Arabic, Chinese, Japanese, and Hindi. Any voice can speak any supported language, allowing you to serve diverse readers without needing multiple voice models or separate language packs.
What languages are supported?
Input text is used only to produce audio and is not used for training. Generated audio is returned in the response and not stored. Only request metadata like time and characters is kept for billing purposes.
Is my data private?
Pricing is $10 per 1 million characters, or $0.01 per 1,000 characters. Failed requests are free. You can start with a $0.50 trial credit when signing in with Google, with no monthly plans or minimum spend required.
How much does it cost?
The API processes requests sequentially, which may cause slight delays under load. Typical speed is roughly real-time for long texts. Requests are processed one after another, so high traffic may result in a brief queue before generation.
Is the service reliable?
We do not guarantee future updates or new features. The current model set includes tts-1 and tts-1-hd. There is no SLA or commitment to specific roadmap changes.
Will the API evolve over time?
Support is available via email only. There is no live chat or phone number. For technical issues or billing questions, contact us through the email address provided on the contact page for assistance with your integration.
How do I get support?
Yes, the API is ideal for educational materials. You can generate audio for textbooks, articles, or exercises. The clear voices and adjustable speed help students with dyslexia engage with content independently, supporting inclusive learning environments effectively.
Can I use it for educational content?
Each request supports up to 4,096 characters. For longer texts, split them into parts and join the resulting audio files. This allows you to handle books or long articles by breaking them into manageable segments for synthesis.
Understanding TTS API Basics
Text-to-speech technology converts written content into audio files via a cloud service. Instead of reading static text, users hear synthesized speech, which can significantly reduce visual stress for dyslexic readers by allowing them to listen while following along or closing their eyes to focus on comprehension.
Cloud-based audio generation
Our API processes text on remote servers, eliminating the need for local installation. You send text via HTTP, and the system returns an audio file. This infrastructure ensures consistent quality without requiring specialized hardware on the user's device.
- No local software installation required
- Consistent audio quality across devices
Programmatic access via HTTP
Integration is straightforward using standard HTTP requests. By sending a POST request to the speech endpoint with JSON data, you receive an audio file directly. This method allows no-code creators to easily embed audio into accessible reading experiences.
- Standard HTTP POST requests
- JSON data format for simplicity
Approximate real-time text to audio conversion
The system generates audio at roughly real-time speed, processing approximately 25 characters per second. While short phrases may take a few seconds, longer texts are processed sequentially. Under heavy load, requests may queue, but the output remains immediate relative to the audio duration.
Benefits for Dyslexic Readers
Converting text to audio removes the strain of decoding dense paragraphs, allowing dyslexic readers to focus on meaning rather than visual processing. By listening to clear, synthetic speech, users can maintain engagement with complex material without the fatigue associated with traditional reading.
Reduces visual stress from text
Visual crowding and letter reversal can make standard text exhausting. TTS bypasses these barriers by delivering audio directly, reducing the cognitive load required to track lines and distinguish characters.
Improves comprehension through listening
Listening allows users to process information at their own pace. With adjustable speeds from 0.25x to 4.0x, readers can slow down for difficult concepts or speed through familiar content, ensuring better retention and understanding.
Allows multi-sensory learning
Combining visual text with auditory input reinforces learning pathways. This dual-input approach helps solidify vocabulary and grammar rules, making it easier to recall information later without relying solely on visual memory.
Comparison: App vs API
For dyslexic readers, consistency is key. While desktop apps offer convenience, they often lock users into a single device or operating system. An API-based solution decouples the audio generation from the interface, allowing you to integrate high-quality speech into any no-code platform you choose.
API offers greater flexibility
An API allows you to embed audio directly into your custom reading tools, websites, or educational apps. Unlike standalone apps, you control the user experience entirely, ensuring the voice and speed settings match the specific needs of each reader.
- Integrate with any no-code platform
- Customize user interface and controls
- Update voices without app updates
App is limited to single device
Traditional apps usually require installation on a specific device. If a student switches from a tablet to a laptop, they must reinstall the software and reconfigure settings. This fragmentation can disrupt the learning flow and increase cognitive load for users with dyslexia.
API scales better for many users
Whether you support five readers or five thousand, the API handles the load. You pay only for the characters consumed, avoiding expensive per-seat licenses. This makes it ideal for schools and libraries looking to provide accessible reading experiences to large groups without infrastructure limits.
Technical Requirements for Integration
Integrating our TTS API requires minimal technical overhead, making it ideal for no-code creators. You only need basic HTTP knowledge to send requests and receive audio files. There is no need to install specialized software or manage complex local servers, as the processing happens entirely in the cloud.
The system uses standard JSON data formats for all requests, ensuring compatibility with most modern tools and platforms. This simplicity allows you to focus on content rather than debugging intricate connection protocols.
Basic HTTP knowledge needed
You do not need a dedicated development team to start. Sending a POST request to the API endpoint is sufficient to trigger audio generation. Most no-code platforms support simple HTTP requests, allowing you to embed audio generation directly into your workflows without writing custom code.
For more control, you can use the OpenAI SDKs by adjusting the base URL to our endpoint. This allows you to leverage existing libraries for authentication and error handling, reducing the learning curve for technical integrations.
JSON data format usage
All requests are sent as JSON bodies, including fields like model, input, voice, and speed. This standardized structure ensures consistent behavior across different programming languages and tools.
You can easily construct these JSON objects using no-code automation tools like Make or Zapier. The predictable format allows for reliable data mapping, ensuring your text inputs are correctly processed and converted into audio files every time.
No specialized hardware required
Since all processing occurs on our cloud servers, your device does not need high-end specifications. Any computer or tablet with a web browser and internet connection can generate audio.
This cloud-based approach also means you never need to manage local storage for large audio files or handle software updates. Your infrastructure remains lightweight, and you can scale usage as your audience grows without upgrading your hardware.
Voice Selection for Clarity
Choosing the right voice is critical for readers with dyslexia, as distinct acoustic features can significantly reduce cognitive load. Our API provides eight presets. For instance, Aria offers a warm, clear narrator style, while Luna provides a soft, storytelling tone that can ease the stress of dense text. Selecting a voice that matches the reader’s preference ensures a smoother, less fatiguing listening experience.
Consistency in voice aids recognition, allowing users to build a mental map of the audio stream. By sticking to one voice for a project, readers can focus on content rather than adapting to new timbres. However, variety is also valuable for engagement. You can switch between voices, such as using Milo for conversational content or Felix for energetic promos, to maintain interest during longer reading sessions.
Clear enunciation reduces confusion
Clarity in speech prevents misinterpretation of similar-sounding words, which is common for dyslexic readers. Our voices are based on licensed recordings. For example, Sage provides a calm, instructional tone ideal for educational materials, ensuring that every syllable is distinct. This reduces the effort required to decode audio, allowing the reader to focus on comprehension rather than phonetic parsing.
- Aria: Warm, clear narrator for general reading
- Sage: Calm, instructional tone for educational content
- Luna: Soft, storytelling style for narrative texts
- Atlas: Neutral, news-style for factual content
Consistent voice aids recognition
Using a single voice for a specific book or course helps listeners build familiarity. When the auditory pattern remains constant, the brain can predict pacing and intonation, reducing cognitive strain. This consistency is especially helpful for long-form content, where switching voices might disrupt the flow of understanding and require re-adjustment to new vocal characteristics.
Multiple voices for variety
Variety can prevent auditory fatigue during extended listening sessions. Our eight presets allow you to diversify content without changing the underlying technology. Use Felix for energetic, promo-style content or Orion for deep, documentary-style narratives. This flexibility keeps the listening experience engaging, particularly for users who might lose focus with repetitive audio patterns.
Note that all voices support all 23 languages, allowing you to maintain a consistent auditory identity even when switching between English, Spanish, or Japanese content. This ensures that the 'voice' remains a familiar anchor, regardless of the language being spoken.
- Felix: Energetic, promo style
- Orion: Deep, documentary style
- Nova: Bright, upbeat tone
- Milo: Friendly, conversational style
Speed Control for Comprehension
Speed control allows dyslexic readers to adjust audio playback to match their cognitive processing pace. By modifying the speed parameter between 0.25x and 4.0x, users can reduce visual strain and improve comprehension without waiting for standard playback speeds.
This flexibility supports multi-sensory learning by letting readers listen at a pace that feels natural, reducing the cognitive load associated with decoding text.
Slower speeds help with complex vocabulary, while faster speeds maintain engagement with familiar content, ensuring the audio remains an effective reading aid rather than a tedious chore.
Adjustable speed from 0.25x to 4.0x
The API allows precise control over playback speed using the speed field. Users can set values between 0.25 and 4.0, enabling customization for individual reading preferences.
This range accommodates both detailed analysis and rapid skimming, ensuring the audio matches the user's comfort zone.
- Set speed via simple JSON parameter
- Range supports 0.25x to 4.0x
- Adjustable per request for flexibility
Slower speed for complex texts
For dense or unfamiliar material, reducing the speed to 0.5x or lower allows readers to process each word clearly. This reduces confusion and aids in understanding complex sentence structures.
Slower playback helps maintain focus, making it easier to follow intricate narratives or technical content.
- Ideal for new or difficult material
- Reduces cognitive overload
- Enhances word recognition
Faster speed for familiar content
When reading known material, increasing the speed to 2.0x or higher can maintain engagement and prevent boredom. Faster playback mimics natural conversation, keeping the listener engaged.
This is particularly useful for reviewing previously read text or listening to stories with established characters.
- Maintains engagement with known text
- Mimics natural conversation pace
- Prevents listener fatigue
Language Support for Multilingual Users
Our API supports 23 languages, including English, Spanish, German, French, Japanese, and Arabic. This broad coverage ensures that multilingual learners and diverse classrooms can access consistent, high-quality audio without needing multiple specialized services. Whether a student is reading in their first or second language, the synthesis engine delivers clear, natural speech.
23 languages supported
We support 23 languages, covering major global tongues and regional variants. The list includes Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, and Turkish. Every voice can speak any of these languages, ensuring consistent audio quality regardless of the source text's origin.
- Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, Turkish
Automatic language detection
If you do not specify a language, the system guesses it from the text script. Latin script text defaults to English, which works well for many users. However, for non-English Latin-script text, relying on auto-detection may lead to incorrect accents or pacing.
Manual language override available
For precise control, you can set the language parameter using an ISO code. This is essential when mixing languages or using Latin script for non-English languages like Dutch or German. It ensures the voice pronounces words correctly, reducing cognitive load for dyslexic readers who rely on accurate phonetic output.

Data Privacy Considerations
Our API prioritizes your data privacy by ensuring that input text is used strictly for audio synthesis. Once the audio is generated and returned, the original text is not stored in long-term memory, ensuring your reading material remains private and secure.
Input text not stored permanently
When you send text to our API, it is processed in real-time to generate the audio file. We do not retain your input text for training or other purposes, meaning your educational content remains yours.
Audio generated on demand
Audio files are created dynamically when requested and returned directly in the response. We do not store the generated audio files permanently on our servers, reducing the risk of data exposure and ensuring immediate delivery.
Metadata kept for billing only
We retain minimal metadata, including the time of request, character count, and status, solely for accurate billing and service monitoring. This data is not used for profiling or third-party sharing, keeping your usage transparent and private.
Cost Efficiency for Schools
Text-to-speech technology transforms static reading into auditory learning, reducing visual stress for dyslexic students. By converting text to audio, it supports multi-sensory education and improves comprehension without requiring expensive hardware or specialized software installations.
Schools benefit from predictable costs and easy integration. The API’s straightforward pricing model ensures that educational budgets remain stable, allowing institutions to focus on content rather than infrastructure maintenance.
Pay per character used
The API charges $10 per 1 million characters, or $0.01 per 1,000 characters. This usage-based model means schools only pay for what they actually consume, avoiding waste on unused licenses.
Failed requests are free, ensuring that billing accurately reflects successful audio generations. This fairness protects school budgets from unexpected charges during high-usage periods.
- $0.01 per 1,000 characters
- Spaces and punctuation count as characters
- Failed requests incur no charge
No monthly subscription fees
Unlike traditional software licenses, there are no recurring monthly costs or minimum spend requirements. Schools can scale usage up or down based on academic needs without financial penalties.
The absence of per-seat limits allows unlimited students to access the same API key, making it ideal for classroom-wide deployments.
Free trial for testing
New accounts receive $0.50 of trial credit, equivalent to 50,000 characters, valid for 7 days. This allows educators to test voice clarity and integration without immediate financial commitment.
The trial is available when signing in with Google, making it easy to evaluate the service before committing to a top-up via USDT.
Reliability and Uptime
Our cloud API delivers audio files directly via HTTP without requiring local server maintenance. Because the service runs remotely, you avoid the overhead of managing on-premise infrastructure or coordinating software patches across multiple devices.
Cloud infrastructure ensures access
Requests are processed through a centralized cloud environment, ensuring consistent availability for your users. While requests are handled sequentially and may queue under high load, the system remains accessible for generating audio on demand.
No local software updates needed
Since the synthesis engine resides on our servers, your readers always access the latest voice models without needing to update applications on their individual devices. This reduces technical friction for non-technical users.
Consistent performance across devices
The API returns standard audio formats (mp3, wav, opus) compatible with any modern browser or device. Users experience uniform audio quality regardless of whether they are on a desktop, tablet, or mobile phone.
Future-Proofing Your Solution
A text-to-speech API future-proofs your accessibility solution by decoupling the audio engine from your interface. As the underlying model improves, your users automatically benefit from better voice quality without requiring code changes or app updates. This ensures your reading experience remains clear and engaging over time.
The API approach allows you to easily swap or add new capabilities. Since you interact via standard HTTP requests, integrating new tools or platforms becomes straightforward as your needs evolve, keeping your solution relevant without major redevelopment.
API updates improve voices
The engine supports two distinct models, tts-1 and tts-1-hd, allowing you to balance cost and quality. Updates to these engines enhance clarity and naturalness, directly benefiting dyslexic readers who rely on clear enunciation to reduce cognitive load.
You can switch between models programmatically. This flexibility ensures that if a new voice preset becomes available, you can offer it to users immediately via the existing API structure.
- Access to tts-1 and tts-1-hd engines
- Automatic quality improvements via API updates
- No client-side code changes required
New languages added over time
With support for 23 languages, the API accommodates diverse learner needs. The API supports 23 languages.
The system also guesses language from script, simplifying the experience for users who mix languages. Manual overrides ensure precision when needed, keeping the interface intuitive.
- Support for 23 languages
- Automatic language detection
- Easy expansion of linguistic coverage
Integration with new tools is easy
Using standard HTTP endpoints, you can connect the TTS service to various no-code platforms, learning management systems, or custom web apps. The JSON-based request format ensures compatibility with modern development tools.
This reduces technical debt. You do not need to rebuild the audio generation logic when new platforms emerge; you simply point your new tool to the same API endpoint.
The consistent request shape allows for rapid prototyping. No-code users can integrate audio features quickly, ensuring your solution scales with new educational tools.
- Standard HTTP/JSON integration
- Compatible with no-code platforms
- Easy to connect to new tools
Support and Documentation
Dyslexia TTS Review offers straightforward assistance for integration challenges. Support is available via email only. This direct channel is ideal for developers who need specific answers about API behavior or billing questions.
We provide detailed documentation that explains endpoints, parameters, and error codes. The docs are structured to help no-code creators understand how to connect their tools without needing deep programming expertise. You can quickly find the information needed to start generating audio.
Email support for technical issues
Our email support team is available to resolve integration questions and billing inquiries. We focus on providing clear, actionable answers to help you maintain your reading experience without interruption.
Unlike phone support, email allows you to include logs or error messages, making it easier for us to diagnose issues with your specific setup or account configuration.
- Direct email contact for technical queries
- No phone queues or hold times
- Responses focused on your specific integration context
Clear API documentation
The documentation covers all endpoints, including voice selection and speed controls. It explains the JSON structure required for requests, making it easy to understand how to send text and receive audio files.
You can reference the docs to verify rate limits, character counts, and supported formats like MP3 or WAV, ensuring your integration meets your accessibility standards.
- Endpoint reference for /v1/audio/speech
- Voice and language parameter details
- Rate limit and pricing explanations
Example code provided
We provide ready-to-use code snippets, including a curl example, to help you test the API immediately. This allows you to verify connectivity and audio quality before full integration.
The examples demonstrate how to set the authorization header, select a voice like Aria or Felix, and handle the response, reducing the learning curve for no-code users.
- Ready-to-use curl example
- JSON body structure guide
- Authorization header setup
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.
