Frequently asked questions
What is read aloud?
Read aloud converts your text content into natural-sounding audio files using our TTS API. You send a POST request with your text, and receive an audio file back. This allows users to listen to your courses instead of reading, improving accessibility and engagement for on-the-go learners.
Why use TTS for courses?
TTS lets you produce narrated courses at scale without hiring human voice actors. With 8 distinct voices and 23 languages, you can create consistent, accessible content quickly. It is ideal for product teams wanting to turn existing text into audio formats for their LMS or apps.
Which voice is best?
Q: Which voice should I choose? A: Select a voice that matches your content’s tone. Use Aria for warm narration, Nova for upbeat content, Sage for calm instruction, or Orion for deep documentaries. All eight voices support all 23 languages, so choose the style that best fits your course’s mood rather than a specific language requirement.
How to handle long texts?
Split your text into parts of up to 4096 characters. Send each part as a separate request to the API. Then, join the resulting audio files. This ensures reliable synthesis, as each request stays within the character limit and allows for better error handling during generation.
What languages are supported?
We support 23 languages including English, Spanish, German, French, Japanese, and Hindi. Any voice can speak any of these languages. If you do not set the language parameter, the system guesses it, but for non-English Latin text, you should explicitly set the language code for accuracy.
How to integrate with LMS?
Use our standard REST API endpoint. Send a POST request with your text and voice selection. The API returns an audio file you can embed in your LMS. Since the request shape matches OpenAI’s speech endpoint, you can often use existing integrations by simply updating the base URL.
What is the cost?
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 free trial credit. Top-ups via USDT on TRON are credited automatically. There are no monthly plans or minimum spends, so you only pay for what you use.
Is it real-time?
It is not real-time streaming. Synthesis takes time, roughly real-time speed for long texts, but short phrases may take a few seconds. Requests are processed sequentially, so under load, your request may wait in a queue. You receive the complete audio file after processing finishes.
How to ensure quality?
Quality is consistent across all 8 voices, which are based on licensed recordings. Each file includes an inaudible watermark marking it as synthetic. To ensure clarity, keep your input text under 4096 characters per request. Use appropriate voices for your content type, such as Sage for instructional material.
Can I change speed?
Yes, you can adjust the speed between 0.25 and 4.0. This allows you to make narration faster for quick reviews or slower for complex explanations. Simply include the speed parameter in your API request body. The default speed is usually sufficient, but customization helps tailor the listening experience.
What formats are best?
You can choose from mp3, wav, opus, flac, or pcm. MP3 is suitable for web players due to small file size. WAV offers high quality for local storage. Opus is efficient for streaming-like playback. Choose based on your LMS capabilities and bandwidth constraints.
How to handle errors?
If synthesis fails, the charge is returned in full. Check your request parameters, such as voice name or text length. If you encounter issues, contact support by email. Since requests are processed sequentially, high load might cause delays, but failed attempts do not incur costs or reduce your balance.
Is it accessible?
Yes, TTS significantly improves accessibility by providing audio alternatives to text. Our API supports multiple languages and adjustable speeds, helping diverse learners. The generated audio files are standard formats playable by most assistive technologies. This makes your courses usable for visually impaired users or those preferring auditory learning.
How to test performance?
Start with the free trial credit of $0.50. Send short test requests to measure latency and audio quality. Monitor your usage dashboard for character counts and request status. Since requests are queued under load, test during peak hours to understand potential delays. Use the curl examples in the docs for quick setup.
Understanding Read Aloud
Read aloud transforms static text into an immersive listening experience, allowing users to absorb content while multitasking. For online courses, this shifts the medium from visual reading to auditory learning, making materials accessible during commutes or breaks.
User Experience
Users consume longer texts more comfortably when audio reduces eye strain. The API delivers natural-sounding narration that maintains clarity, enabling seamless integration into LMS platforms without requiring human voice actors for every chapter.
- Reduces cognitive load for long-form content
- Enables multitasking consumption of course materials
Accessibility
Audio support ensures content reaches users with visual impairments or dyslexia. By providing a text-to-speech option, product teams remove barriers to entry, ensuring that educational materials are inclusive and compliant with modern accessibility standards.
- Supports visual impairments and dyslexia
- Inclusive design for diverse learning styles
Engagement
Listening often increases completion rates for lengthy courses. The consistent, professional narration keeps listeners engaged without the fatigue of continuous reading, encouraging users to finish modules and return for future lessons.
- Higher completion rates for long modules
- Reduces reading fatigue during study sessions
Voice Selection
Choosing the right voice is critical for maintaining listener engagement during long-form content like audiobooks and courses. The right voice should feel like a trusted mentor, guiding users through material without becoming distracting.
Clear Narration
Prioritize voices that offer crisp articulation and steady pacing. Aria provides a warm, clear narrator style ideal for complex explanations, while Luna’s soft tone suits storytelling segments. Clear diction ensures users can follow dense educational material without strain.
- Aria for warm, clear narration
- Luna for soft storytelling
- Sage for calm, instructional content
Neutral Tone
A neutral tone prevents the voice from imposing unwanted emotion on neutral facts. Atlas delivers a balanced, news-style delivery perfect for factual updates. Milo offers a friendly, conversational style that feels natural for conversational courses.
- Atlas for neutral, news-style delivery
- Milo for friendly, conversational tone
Professional Voices
For premium content, select voices with distinct professional characteristics. Orion’s deep, documentary style adds authority to serious topics. Felix brings energetic clarity suitable for promotional or high-level overviews. All voices support 23 languages, ensuring consistent quality across global audiences.
- Orion for deep, documentary authority
- Felix for energetic, promotional clarity
Language Support
Lectia supports 23 languages, covering major global markets. Any voice can speak any of these languages, allowing flexible narration choices regardless of the source text. Supported languages include Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, and Turkish.
23 Languages
Our API covers the most widely spoken languages for online courses. This ensures your narrated content reaches a broad audience without needing separate voice talent for each region.
Auto Detection
If you do not set the language field, the system guesses the language from the script. Latin script text defaults to English. For non-English Latin-script text, you must explicitly set the language parameter to ensure accurate pronunciation.
Multi-Language
Since any voice can speak any supported language, you can maintain consistent narrator identity across different language versions of your course. This simplifies brand management for your product team.
- Not supported: Vietnamese, Indonesian, Thai, Ukrainian, Romanian, Czech, Bengali, and others.
Technical Setup
Integrate our TTS API by sending a POST request to https://api.f9999.info/v1/audio/speech. The endpoint accepts JSON bodies with model, input, voice, and response_format fields, mirroring the standard OpenAI speech structure. This compatibility allows you to use existing OpenAI SDKs by simply updating the base_url to https://api.f9999.info/v1 and supplying your unique API key.
Authentication requires the Authorization: Bearer header with your key. You can manage keys via the /get-api-key/ dashboard. Each request returns a complete audio file, ensuring reliable playback for long-form content like audiobooks or course modules without complex streaming logic.
API Integration
Connect your application by pointing your HTTP client to the API base URL. Pass your text in the input field, select a voice from the 8 available presets, and specify the desired output format. The system processes requests sequentially, so under heavy load, queuing may occur.
- Use POST https://api.f9999.info/v1/audio/speech
- Include
Authorization: Bearer tts-...header - Supports standard OpenAI SDKs with base_url override
Streaming vs File
Unlike real-time streaming services, our API returns complete audio files. This approach simplifies playback in LMS players and ensures the entire segment is available for caching or offline access. Each request generates a finite file, which avoids the complexity of WebSocket management.
Caching
Since audio files are returned directly, you can store them in your CDN or local storage. This reduces repeated API calls for identical text segments, lowering costs and improving load times for users revisiting the same lesson or book chapter.
Content Preparation
Preparing your content for synthesis ensures the API generates accurate, high-quality audio without errors. Properly formatting your text and understanding character constraints prevents unexpected truncation or pricing surprises during the conversion process.
By cleaning your source material and adhering to strict length limits, you guarantee that every sentence is rendered clearly. This preparation step is crucial for maintaining consistent narration quality across long-form audiobooks and educational courses.
Text Formatting
Remove complex HTML tags and ensure clean, plain-text input. The API processes standard characters, spaces, and punctuation as part of the character count, so extra formatting can inflate costs without adding value.
Ensure consistent spacing and remove special symbols that might confuse the speech engine. Clean text leads to more natural pacing and reduces the likelihood of mispronunciations during synthesis.
- Use plain text without HTML wrappers
- Remove non-standard symbols and extra whitespace
- Ensure consistent punctuation for better phrasing
Character Limits
Each API request supports a maximum of 4,096 characters. This limit includes spaces and punctuation, so plan your text segments accordingly to avoid truncation.
Exceeding this limit in a single request will result in an error. Break longer passages into smaller chunks before sending them to the endpoint to ensure reliable processing.
Keep an eye on your total character usage, as billing is based on the total characters processed across all requests. Efficient segmentation helps manage your monthly budget effectively.
- Maximum 4,096 characters per request
- Spaces and punctuation count toward the limit
- Exceeding the limit causes a request error
Splitting Logic
- Split at logical sentence or paragraph boundaries
- Process segments sequentially for narrative flow
- Retry failed segments to ensure completeness
Audio Processing
After the API generates the audio, you receive a binary file in your chosen format (mp3, wav, opus, flac, or pcm). These files are self-contained and ready for immediate playback in your LMS player without further transcoding.
Format Conversion
The API returns the audio directly in the format you specified in the response_format field. This eliminates the need for server-side conversion pipelines, allowing you to store the original file as-is or convert it later for specific player compatibility.
Speed Adjustment
You can control the playback speed between 0.25 and 4.0 using the speed parameter during generation. This is critical for educational content, allowing students to slow down dense technical explanations or speed up review sessions without re-generating the audio file.
Quality Check
Each generated file includes an inaudible watermark identifying it as synthetic speech. Verify the audio integrity by checking the file size against the character count; typical generation speed is roughly real-time, so a 10-minute audio file should take approximately 10 minutes to generate.
User Interface
To deliver a seamless read-aloud experience, your interface must prioritize clarity and simplicity. The player should blend unobtrusively into your course layout, ensuring the focus remains on the educational content. Use neutral, professional voices like Atlas or Sage to maintain a consistent, distraction-free narrative tone suitable for long-form audiobooks.
Player Design
Design a minimal player that supports the available formats (mp3, wav, opus, flac, pcm). Ensure it is lightweight and does not hinder page performance, allowing users to consume audio without heavy DOM overhead.
- Minimalist design focusing on content
Controls
Provide essential playback controls: play, pause, and stop. Allow users to adjust the speed between 0.25x and 4.0x to accommodate different learning paces. Avoid complex features like SSML or emotion tags unless explicitly handled by your backend.
- Play, pause, stop
Progress Tracking
Implement clear progress indicators so users know how much content remains. Since requests are processed sequentially, ensure the UI reflects the current state accurately without showing partial audio streams. Sync the player state with the API response to prevent desynchronization during long texts.
- Clear progress indicators

Performance
Latency varies by text length. Short phrases take a few seconds, while long texts generate at roughly real-time speed (25 characters per second). Requests are processed sequentially, so under load, a request may wait in a queue.
Latency
Expect a few seconds for short inputs. Longer texts generate at approximately real-time speed. Be aware that requests are processed one after another, meaning delays can occur during peak usage.
Load Handling
The API processes requests sequentially. During high demand, your requests may enter a queue. This ensures fair processing but may increase wait times for concurrent users.
- Sequential processing ensures fairness.
- Queue delays possible under load.
- No guaranteed instant response.
Optimization
Pre-generate audio files for static course content to avoid runtime latency. Split texts into parts under 4,096 characters to ensure smooth synthesis. Monitor your 60 requests-per-minute limit to prevent throttling.
- Pre-generate for static content.
- Split text under 4,096 chars.
- Respect 60 req/min limit.
Cost Management
Managing costs for long-form audio requires understanding the per-character pricing model. At $0.01 per 1,000 characters, costs scale directly with content volume. Failed requests are free, so you only pay for successful synthesis. A $0.50 free trial provides about 50,000 characters for testing, but standard accounts start with zero balance.
Payment is handled via USDT on the TRON network (TRC-20) with a $5 minimum top-up. Credits are automatic and never expire. There are no monthly subscriptions, seats, or hidden fees, making budgeting predictable for product teams scaling their audiobook libraries.
Budgeting
Calculate your monthly audio budget by estimating total character counts across all course modules. Since spaces and punctuation count, include all formatting characters in your estimates. Top-ups are instant, allowing you to fund only what you need without committing to a recurring plan.
Use the free trial to validate your cost assumptions before committing funds. Each account starts with $0.50 credit if signed in with Google, giving you a small buffer to test voice selection and format choices without immediate payment.
- $0.01 per 1,000 characters (including spaces)
- $5 minimum top-up via USDT (TRC-20)
- No monthly plans or seats
- Balance never expires
Usage Monitoring
Your dashboard displays real-time balance, characters remaining, and usage history. Track which voices or formats consume the most budget relative to user engagement. Since requests are processed sequentially, high concurrency may increase latency but does not change the per-character rate.
Failed requests are fully refunded, so you can monitor error rates to avoid paying for wasted characters. Use the /v1/voices endpoint to check pricing for different formats and voices before generating large batches.
- Real-time balance and character count
- Automatic refund for failed requests
- Sequential processing queue info
Optimization
Split texts into 4,096-character chunks to ensure consistent processing and easier error handling. Use mp3 format for general playback to save storage and bandwidth, reserving wav or flac for high-quality downloads. Adjust speed between 0.25 and 4.0 to reduce generation time for short phrases.
Pre-generate audio for static content like course introductions to avoid runtime latency. For dynamic content, cache generated audio files since input text is not stored long-term. This reduces repeated API calls for the same text segments.
Avoid sending large blocks of text with complex punctuation, as they count toward the character limit. Clean your text input to remove unnecessary whitespace before sending it to the API.
- Split text into 4,096-character parts
- Use MP3 for general playback
- Cache generated audio for static content
- Adjust speed to reduce generation time
Best Practices
Maintaining a consistent voice across your entire course or audiobook library builds trust and reduces cognitive load for learners. Since your API supports eight distinct presets, assign a single voice to each module or chapter and stick with it. This consistency helps users recognize the narrator’s style, making long-form content feel like a unified production rather than a collection of disjointed audio files.
High-quality input text directly impacts the final audio. Ensure your source material is clean, with proper punctuation and no stray formatting characters that might confuse the synthesizer. For best results, keep individual requests under 4096 characters to ensure consistent latency and quality, splitting longer texts logically before sending them to the API.
Voice Consistency
Assign one voice per course to maintain a uniform tone. Use 'sage' for instructional modules and 'aria' for narrative sections. Avoid switching voices mid-sentence, as this breaks immersion. Document your voice choices in your product spec so your development team applies them consistently across all endpoints.
- Use 'sage' for instructional content
- Use 'aria' for narrative sections
- Document choices in product spec
Text Quality
Pre-process text to remove markdown artifacts and ensure proper punctuation. The API guesses language from script, so explicitly set the language field for non-English Latin text to avoid misinterpretation. Clean text reduces errors and ensures accurate pronunciation across all 23 supported languages.
- Remove markdown artifacts
- Set explicit
languagefield - Ensure proper punctuation
Testing
Test edge cases like long sentences, numbers, and special characters. Verify that speed adjustments between 0.25 and 4.0 do not distort clarity. Use the free trial credit to validate your integration before scaling to full production volumes, ensuring your splitting logic handles the 4096-character limit correctly.
- Test numbers and special characters
- Verify speed adjustments
- Validate splitting logic
Common Issues
Even with careful implementation, technical hiccups can interrupt the listener's flow. Understanding these common pitfalls helps you maintain a smooth, professional experience for your users without unexpected interruptions.
Audio Glitches
Synthesized audio may contain minor artifacts if the source text contains unusual punctuation or mixed scripts. These are rare but can occur if the input exceeds 4096 characters without proper splitting. Ensure your splitting logic handles boundary conditions cleanly to avoid abrupt cuts between segments.
- Use consistent formatting to reduce synthesis artifacts.
- Verify character count limits before splitting.
Language Errors
Voice selection does not strictly enforce language; a voice might mispronounce text if the language parameter is omitted for non-English Latin script. Always explicitly set the language code to ensure accurate pronunciation. Unsupported languages like Vietnamese or Thai will not be synthesized correctly.
- Always set the
languageparameter explicitly. - Check supported languages list before deployment.
Rate Limits
Accounts are limited to 60 requests per minute. If your application sends too many requests simultaneously, additional requests may queue or fail. Monitor your usage dashboard to stay within limits, especially when generating long audiobooks or bulk content.
- Limit requests to 60 per minute.
- Monitor usage via the dashboard.
Future Updates
The core API remains stable, focusing on reliable character processing rather than speculative features. We avoid adding custom voice cloning or SSML support, ensuring the tool stays simple for product teams building long-form content.
New Voices
The eight current presets (Aria, Nova, Luna, Sage, Felix, Milo, Atlas, Orion) are the complete set. We are not introducing new voice models or emotion tags, keeping the library predictable for consistent audiobook narration.
- No new voices planned
- Existing voices support all 23 languages
Language Expansion
The current list of 23 supported languages is the complete list. We are not adding Vietnamese, Indonesian, Thai, Ukrainian, Romanian, Czech, or Bengali. The system continues to guess language from script, defaulting to English for Latin text.
Feature Roadmap
We will not add streaming, WebSocket, or SSML. The endpoint structure remains fixed. Updates focus on infrastructure reliability and billing transparency, not new interface features. No custom pronunciation lexicons or voice design tools will be added.
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Her pacing works well for quick tips, feature introductions, or engaging marketing-style course segments where energy is key.
23 languages
Any voice speaks any of these languages.
