Frequently asked questions
What is a text reader?
LingoVoice is a cloud TTS API that converts text into audio files. Send a POST request to https://api.play2jj.com/v1/audio/speech with your input. It supports the tts-1 and tts-1-hd models, which share the same engine and pricing. Each request accepts up to 4096 characters of text.
How does a text reader help language learning?
It provides consistent, high-quality audio for language education tools. Users can hear accurate pronunciation across 23 languages, including English, Spanish, and Japanese. The API ensures uniform voice quality, helping learners associate text with correct speech patterns without relying on variable human recordings.
Which voices are best for learners?
All eight voices support any of the 23 available languages. Sage is explicitly designed for instructional content, offering a calm, instructional tone. Aria provides a warm, clear narrator style, while Luna offers a soft, storytelling tone. You may select any voice to match your curriculum’s requirements without relying on subjective rankings.
Can I use a text reader for multiple languages?
Yes, any voice can speak any of the 23 supported languages. If the language parameter is omitted, the system guesses from the script, defaulting to English for Latin text. For non-English Latin scripts, explicitly set the language parameter to ensure accurate pronunciation.
How do I integrate a text reader API?
Send a POST request to https://api.play2jj.com/v1/audio/speech with a JSON body containing your text, voice, and model. Use your Bearer token for authentication. The official OpenAI SDKs work by setting the base_url to https://api.play2jj.com/v1. This allows easy integration into existing applications.
What is the character limit?
Each API request accepts up to 4096 characters of input text. Spaces and punctuation count toward this limit. If your content exceeds this length, you must split the text into smaller parts, generate audio for each, and join the resulting files.
How do I handle long texts?
Split your text into chunks of up to 4096 characters. Send each chunk as a separate POST request to the speech endpoint. Once you receive all audio files, join them sequentially. This ensures consistent generation quality and avoids exceeding the per-request character limit.
Is a text reader expensive?
Pricing is $10 per 1 million characters, or $0.01 per 1,000 characters. Failed requests are free. There are no monthly plans or minimum spends. You pay only for what you use, with a transparent billing model based on character count rather than duration.
Do I need a developer for a text reader?
A basic understanding of HTTP requests is sufficient. You can use standard tools like curl or the OpenAI SDK. The API uses standard JSON bodies and Bearer token authentication. Developers can integrate it quickly, but non-developers can also test endpoints via the dashboard.
Can I adjust the speed?
Yes, you can set the speed parameter between 0.25 and 4.0. This allows you to slow down speech for beginners or speed it up for advanced learners. Adjusting speed helps tailor the audio to different proficiency levels. The API accepts this value to control generation rate, ensuring consistent playback for your language education tools.
What audio formats are supported?
The API supports mp3, wav, opus, flac, and pcm formats. Select the response_format field in your request body based on your application needs. MP3 is efficient for web delivery, while WAV and FLAC offer higher quality for educational materials.
Is the text reader real-time?
No, the API does not support real-time streaming or WebSocket connections. Requests are processed sequentially, with a typical generation speed of approximately 25 characters of text per second of audio. Short phrases may take a few seconds to complete. Under high load, requests may experience queueing delays before synthesis begins.
Do I need to store audio files?
Generated audio is returned in the response and not stored by the API. You must handle storage if you need to retain the files. Input text is used only for synthesis and not for training. Request metadata is kept for billing purposes.
How do I pay for a text reader?
Top up your balance using USDT (TRC-20) on the TRON network. The minimum deposit is $5, with credits added automatically within minutes. We do not accept credit cards, PayPal, subscriptions, or VAT invoices. Google sign-up accounts receive a $0.50 trial valid for 7 days. Email sign-ups start without trial credit. Balances do not expire.
Why Use a Text Reader for Language Learning
Text-to-speech integration allows language education platforms to generate consistent audio from any source text. This approach ensures that learners receive uniform pronunciation models across diverse topics without requiring extensive recording budgets for every lesson.
Improves listening comprehension
Learners can access audio content that matches their curriculum precisely. By converting reading materials into speech, educators provide consistent auditory input that reinforces vocabulary retention and reading fluency.
Supports pronunciation study
Students can compare their own speech against generated audio files. The API supports 23 languages, allowing learners to practice specific phonetic structures in their target language with clear, preset voice models.
Enables interactive lessons
Applications can dynamically generate audio prompts for quizzes or exercises. This capability enables real-time feedback loops where students hear questions or instructions in their target language immediately upon request.
Choosing the Right Voice
The API provides eight distinct voice presets, each designed for specific pedagogical contexts. Female options include Aria, a warm and clear narrator, Luna, a soft storyteller, Nova, a bright upbeat speaker, and Sage, a calm instructional voice. Male options include Felix, an energetic promo voice, Milo, a friendly conversational speaker, Atlas, a neutral news anchor, and Orion, a deep documentary narrator.
Clear narration for beginners
For introductory material, Aria and Luna offer clear or soft tones suitable for structured reading. Nova provides a bright, upbeat pace for engaging content, while Sage delivers a calm, instructional style ideal for step-by-step guidance. These voices ensure consistent audio quality for foundational listening exercises.
- Aria: warm, clear narrator
Neutral tones for advanced learners
Atlas and Orion provide neutral or deep tones for complex vocabulary and news-style content. Atlas offers a neutral news delivery, while Orion provides a deep, documentary-style narration. These presets minimize expressive variation, allowing students to focus on linguistic structures without auditory distraction.
- Atlas: neutral, news
Distinct voices for dialogue
Use Felix and Milo for dynamic conversations. Felix brings energetic, promo-style delivery, while Milo offers a friendly, conversational tone. Assigning different voices to characters helps learners distinguish speakers in multi-dialogue exercises, enhancing comprehension through auditory cues.
- Felix: energetic, promo

Managing Multiple Languages
We support 23 languages, enabling startups to build comprehensive language learning tools. Any voice can speak any of these languages, providing flexibility for diverse curriculum needs. This allows developers to create immersive listening exercises without managing separate voice models for each language.
Support for 23 languages
Our 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. This broad coverage allows you to create lessons for a wide range of learners.
- Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, Turkish.
Language detection accuracy
If the language field is omitted, the system guesses based on the script. Latin script text defaults to English. This simplifies integration but may require manual adjustment for mixed-language content or non-English Latin scripts to ensure accurate synthesis.
Explicit language codes
For non-English Latin-script text, set the language parameter explicitly. This ensures the correct pronunciation and intonation. Supported ISO codes allow precise control over the output, preventing misinterpretation of characters from languages like Greek or Cyrillic.
Technical Integration Steps
Integration begins by registering via the /get-api-key/ page using Google or email credentials. The dashboard provides your active API key, current balance, and a ready cURL example. Note that accounts are per site, and each key supports a 60 requests per minute rate limit.
API key acquisition
Sign up on the site's /get-api-key/ page. The dashboard displays your active key, balance, and a ready cURL example.
- Google or email + password sign-up
- One active key per account
- 60 requests per minute limit
Endpoint configuration
Send POST requests to https://api.play2jj.com/v1/audio/speech. The API follows the OpenAI request shape, allowing use of official OpenAI SDKs by adjusting the base_url. Include the model, input text, voice, and optional language parameters in the JSON body.
- Base URL: https://api.play2jj.com/v1
- Auth: Authorization: Bearer tts-...
- Standard JSON body structure
Audio file handling
The API returns the audio file directly in the response. Choose formats like mp3, wav, opus, flac, or pcm based on your app's needs. Files are not stored server-side after generation.
- Formats: mp3, wav, opus, flac, pcm
- Direct response delivery
- No server-side storage
Handling Long Texts
Handling long texts requires splitting input into segments of up to 4096 characters, as each API request is limited to this length. You must join the resulting audio files sequentially to reconstruct the complete lesson. This workflow ensures consistent quality across entire course materials without exceeding payload constraints.
4096 character limit
Each request accepts a maximum of 4096 characters, including spaces and punctuation. If your text exceeds this limit, you must divide it manually or via your backend logic before sending requests to the endpoint.
Splitting and joining audio
Split your source text into chunks not exceeding 4096 characters. Send each chunk as a separate POST request to receive individual audio files. Your application should then concatenate these files in order to produce the final audio asset for the learner.
Queue management
Requests are processed sequentially, meaning under load, a request may wait in a queue. Typical generation speed is roughly real-time (25 characters per second). For long texts, factor in this queue time when designing your user interface to prevent timeouts or poor user experience.
Cost Management Strategies
Precise character counting ensures accurate billing, as every space and punctuation mark is included in the 0.01 per 1,000 characters rate. Failed requests incur no charge, protecting your budget during development.
Managing your balance requires understanding the top-up mechanics. Credits do not expire, allowing you to accumulate funds over time without urgency, provided you maintain sufficient balance for production traffic.
Character counting
Calculate costs by counting all characters, including spaces and punctuation. The API charges $0.01 per 1,000 characters. For a 4,000-character lesson, expect a $0.04 cost if successful.
- Include spaces and punctuation in counts
- Failed requests are free
- Rate is $0.01 per 1,000 characters
Free trial usage
Google sign-ins receive $0.50 credit (approx. 50,000 characters) valid for seven days. Use this for initial integration testing. Email-based accounts start with zero balance.
- $0.50 credit for Google sign-ins
- Valid for 7 days
- Email accounts start with zero balance
USDT top-up timing
Top up via USDT (TRC-20) on the TRON network. Minimum $5. Credits are credited automatically within minutes. No monthly plans or invoices.
- USDT (TRC-20) only
- Minimum $5 top-up
- Credited within minutes
Audio Format Selection
Selecting the correct audio format balances playback compatibility with storage efficiency. Our API supports MP3, WAV, OPUS, FLAC, and PCM, allowing you to optimize based on your application’s specific needs. The choice directly impacts bandwidth usage and device compatibility without altering the underlying synthesis quality.
MP3 for mobile apps
MP3 is the standard choice for mobile applications due to its universal support across iOS and Android devices. It offers a reliable balance between file size and audio quality, ensuring smooth playback without requiring additional codec installations on the client side.
- Universal device compatibility
- Optimal file size for mobile data
WAV for quality
WAV provides uncompressed audio, preserving the full fidelity of the generated speech. This format is ideal for educational tools where audio clarity is paramount, such as pronunciation drills, ensuring that every phoneme is rendered exactly as synthesized without compression artifacts.
OPUS for efficiency
OPUS delivers excellent audio quality at significantly lower bitrates compared to MP3. This makes it ideal for reducing bandwidth costs in high-volume language learning platforms, allowing you to serve more lessons within the same network constraints while maintaining clear speech.

Speed Adjustment Benefits
The speed parameter allows you to control the playback rate of generated audio, ranging from 0.25 to 4.0 times the default pace. This feature is essential for adapting audio content to different learning stages and user preferences.
Slower speed for learners
Setting the speed below 1.0 (e.g., 0.75) helps beginners parse unfamiliar phonemes and sentence structures. Slower audio provides more time for cognitive processing, improving listening comprehension and pronunciation study accuracy.
Faster speed for review
Increasing the speed (e.g., 1.5x or 2.0) is ideal for advanced learners reviewing known material. Faster playback reduces lesson duration, allowing users to cover more vocabulary or text in less time.
0.25 to 4.0 range
The API accepts any float value between 0.25 and 4.0, inclusive. This wide range ensures fine-grained control over audio tempo, enabling precise customization for specific language exercises or accessibility needs without requiring post-processing.
Data Privacy Considerations
Our architecture ensures that input text is used exclusively to generate the requested audio file and is not utilized for model training or improving the underlying voice engine. This guarantees that your educational content remains distinct from the data used to refine the synthesis algorithms.
No data training
The input text you send to the API is processed solely for the immediate purpose of synthesis. It is not retained in a pool to train or enhance the voice models, ensuring that your curriculum text does not influence future voice generation behaviors.
Input text retention
Generated audio is returned in the response and not stored on our servers. The input text is used only to produce the audio and is not used for training. Your proprietary lesson content remains under your control.
Metadata usage
Request metadata, including timestamp, character count, and status, is kept for billing purposes. This data supports accurate invoicing and usage tracking without retaining the actual educational content itself.
Scalability for Startups
Our character-based billing model ensures that costs scale directly with usage, eliminating the risk of unexpected fees during traffic spikes. Startups can process high volumes of text without managing complex infrastructure or negotiating minimum spend tiers, paying only for the characters actually synthesized.
The API architecture removes infrastructure overhead, allowing teams to focus on product development rather than server maintenance. While the rate limit is 60 requests per minute per key, the predictable pricing structure supports consistent growth without requiring immediate capital expenditure for dedicated hardware or load balancers.
Pay-per-use model
You are charged $0.01 per 1,000 characters, with failed requests refunded in full. This ensures that wasted compute power does not inflate your operational costs, providing transparent billing aligned with actual consumption.
No monthly plans or seats mean you retain full control over your burn rate. Balance does not expire, allowing you to accumulate credit during quieter periods for peak usage times.
- Charge only for successful synthesis
- No minimum spend requirements
- Transparent per-character billing
No infrastructure overhead
The cloud-based API handles all synthesis processing, so you do not need to provision servers or manage TTS engines. Your application simply sends JSON payloads and receives audio files.
You avoid the complexity of scaling storage or compute resources as your user base grows. The service handles the heavy lifting, ensuring consistent performance regardless of your internal architecture.
- Cloud-native processing
- No server management required
- Simplified technical stack
Rapid scaling
Startups can integrate the API quickly using standard HTTP requests or the OpenAI SDK, enabling fast deployment of language learning features. The straightforward authentication with a single active key per account simplifies initial setup.
While each account is limited to 60 requests per minute, the predictable nature of the service allows for easy vertical scaling by upgrading your plan or managing multiple accounts if necessary. This ensures your application can handle increased demand without significant architectural changes.
Note: Issuing a new key replaces the existing one, maintaining the 60 req/min limit per account rather than increasing throughput for a single account.
- Easy integration via HTTP
- Standard SDK compatibility
- Predictable performance limits
Error Handling in Production
In production environments, network interruptions or temporary API unavailability can cause request failures. Implementing robust retry logic with exponential backoff ensures that transient errors do not result in lost audio files or inconsistent user experiences.
Since failed requests are free, verifying refund status provides financial clarity during debugging. Monitoring request metadata helps identify patterns in failures, allowing teams to adjust their integration strategy before significant volume impacts billing.
Retry logic
Configure automatic retries for HTTP 500 or 503 errors. Use exponential backoff to avoid overwhelming the queue during high-load periods, ensuring steady processing of up to 60 requests per minute.
- Implement exponential backoff for transient errors
- Handle 500/503 status codes automatically
- Respect rate limits during retry cycles
Refund verification
Failed synthesis requests incur no charge. Verify that credits are restored immediately after a confirmed failure to maintain accurate balance tracking without manual intervention.
Use this feature to validate integration stability. If refunds do not appear, check the request ID against billing logs to ensure the failure was correctly registered.
- Automatic credit restoration on failure
- No charge for failed synthesis
- Verify refund status in billing logs
Status monitoring
Track request metadata including time, characters, and status codes. This data supports debugging and helps predict queue delays under load.
Monitor usage trends to anticipate scaling needs. Since requests are processed sequentially, high volume may cause queuing delays, which can be mitigated by monitoring real-time status updates.
- Log request metadata for debugging
- Track character count and status codes
- Monitor queue wait times under load

Future-Proofing Your App
Your application benefits from a standardized API structure that mirrors established industry patterns. This design minimizes integration complexity and ensures that your speech synthesis module remains compatible with existing infrastructure as your language learning platform expands.
By leveraging the standard JSON request format, you reduce the risk of breaking changes during updates. This stability allows your development team to focus on content delivery rather than managing proprietary protocol shifts.
Standard API design
The API follows a predictable endpoint structure for speech synthesis and voice listing. This consistency simplifies testing and deployment pipelines for startups building multilingual educational tools.
SDK compatibility
The service accepts requests via the official OpenAI SDKs by simply adjusting the base URL to https://api.play2jj.com/v1. This allows you to use familiar client libraries without rewriting your HTTP logic.
Voice updates
The eight preset voices (aria, nova, luna, sage, felix, milo, atlas, orion) provide a stable set of options for dialogue and narration. While the engine remains consistent, you can always check the /v1/voices endpoint for current availability.
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Mastering new languages empowers your startup to expand globally and connect with diverse talent pools effortlessly.
23 languages
Any voice speaks any of these languages.
