Frequently asked questions
Which TTS API is best for LMS?
Q: Which TTS API is suitable for LMS? A: LMS Voice Core is built for L&D teams managing large-scale online course production. It provides a reliable, character-based TTS API that integrates directly into your existing LMS workflows without complex infrastructure overhead. It supports 23 languages and 8 distinct voice presets suitable for educational narration.
How does the pricing compare to other TTS providers?
Pricing is $10 per 1 million characters, or $0.01 per 1,000 characters. Spaces and punctuation count as characters. Failed requests are free, with the charge returned in full. There are no monthly plans, seats, or minimum spend requirements, only a pay-as-you-use model.
Do the voices sound natural for educational content?
Voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain audiobook readings. Each generated file carries an inaudible watermark marking it as synthetic speech. Options include calm, instructional tones like Sage or neutral news styles like Atlas, suitable for clear educational delivery.
Can I use the API for bulk course generation?
Yes, texts are split into parts of up to 4096 characters and joined into audio files. Typical speed is roughly real time, generating about 25 characters of text per second. Requests are processed sequentially, so under load, a request may wait in a queue before synthesis begins.
Is the API compatible with OpenAI SDK?
Yes, the endpoint shape matches the OpenAI speech endpoint. You can use official OpenAI SDKs by changing the base_url to https://api.playa1one.com/v1 and using your site-specific key. This allows direct integration into existing codebases without requiring a proprietary SDK or custom client library.
How many languages are supported?
The API supports 23 languages, including English, Spanish, German, French, Japanese, Chinese, and Arabic. Any voice can speak any of these languages. If the language parameter is not set, the system guesses from the script, defaulting to English for Latin-script text.
Do I need to pay for a monthly subscription?
No, there are no monthly plans, subscriptions, or seats. You pay only for characters used. Top-ups are made via USDT on the TRON network (TRC-20) with a minimum of $5. Balance does not expire, and there are no invoices with VAT.
Can I clone my own voice with this API?
No, custom voice cloning is not offered. You cannot upload your own voice or design a new one. The API uses eight fixed presets based on licensed recordings. Voices are static and cannot be customized or cloned for specific individuals or brands.
Is there a free trial available?
Yes, signing in with Google provides $0.50 of credit, valid for 7 days, allowing about 50,000 characters. Accounts created with email and password start without trial credit. Failed requests are free, so you can test the API without incurring charges for errors.
How long does it take to integrate the API?
Integration is straightforward using standard HTTP requests or the OpenAI SDK. You send a POST request to the speech endpoint with your API key. Typical speed is roughly real time, with short phrases taking a few seconds to generate, allowing for quick testing and deployment.
Do I get an SLA for uptime?
No, there is no SLA, uptime guarantee, or enterprise contract. The service is provided on a best-effort basis. Requests are processed sequentially, so under load, a request may wait in a queue, potentially affecting generation latency during high traffic.
Can I use the API for accessible content?
Yes, the API generates audio files in formats like mp3, wav, opus, flac, and pcm, suitable for accessibility standards. Voices include clear narrator and instructional tones. Input text is used only to produce audio and is not used for training, ensuring privacy for your course content.
What happens if the API goes down?
There is no SLA or uptime guarantee to compensate for downtime. If synthesis fails, the charge is returned in full. Input text is not stored, and generated audio is returned in the response, so you do not lose data during service interruptions.
Do I need technical skills to use the API?
Yes, you need to send JSON POST requests with specific fields like model, input, voice, and speed. You must manage your API key and handle character splitting for texts over 4096 characters. While SDKs simplify this, basic programming knowledge is required for integration.
Evaluation Criteria
For L&D teams, selecting a TTS API requires balancing cost predictability with output fidelity. The primary evaluation criteria focus on how pricing scales with volume, the naturalness of the generated voices, and the breadth of language support required for global course libraries.
Pricing Model
Cost efficiency is driven by a per-character rate of $0.01 per 1,000 characters, regardless of voice or format. Failed requests incur no charge, ensuring budget accuracy for high-volume quiz generation.
- Transparent character-based billing
- No minimum spend or monthly fees
- Failed requests are free
Voice Quality
Voices are derived from licensed LibriTTS-R and public-domain LibriVox recordings, providing consistent, professional narration suitable for educational content. Each file includes an inaudible synthetic watermark for content verification.
- Licensed source recordings
- Consistent narration tone
- Inaudible watermarking
Language Support
The API supports 23 languages, allowing any voice to speak any supported language. Automatic detection works for Latin script, but manual language codes are required for non-English Latin text to ensure accuracy.
- 23 supported languages
- Automatic script detection
- Manual language override
Our API: Technical Overview
The API endpoint follows the standard OpenAI speech structure, accepting POST requests to /v1/audio/speech. The JSON body requires a model selection of "tts-1" or "tts-1-hd", along with the input text, voice preset, and desired audio format. This design allows LMS teams to leverage existing integrations without custom middleware development.
Endpoint Structure
Requests are processed sequentially, returning the audio file directly in the response. The input text is limited to 4096 characters per request, requiring text splitting for longer lecture transcripts. Supported output formats include mp3, wav, opus, flac, and pcm, ensuring compatibility with various LMS media players.
- Endpoint: POST /v1/audio/speech
- Max input: 4096 characters
- Formats: mp3, wav, opus, flac, pcm
SDK Compatibility
The API mimics the official OpenAI speech endpoint shape, allowing the use of standard OpenAI SDKs by simply changing the base URL to https://api.playa1one.com/v1. Authentication is handled via a Bearer token in the Authorization header, ensuring secure integration with your existing infrastructure.
- Base URL: https://api.playa1one.com/v1
- Auth: Bearer token
- Compatible with OpenAI SDKs
Rate Limits
Each API key is limited to 60 requests per minute, with a lower limit of 10 requests per minute before the first top-up. Requests are processed sequentially, meaning high-volume generation may experience queueing during peak usage periods. This limit applies per key, allowing teams to scale by issuing additional keys.
- Limit: 60 requests/minute per key
- Pre-top-up: 10 requests/minute
- Sequential processing
Voice Selection Analysis
Voice selection directly impacts learner engagement in online course modules. LMS teams can choose from eight distinct presets tailored to specific instructional contexts, ensuring audio aligns with content tone.
Available Presets
The API provides eight voice presets, categorized by gender and intended use. Female voices include Aria (warm narrator), Nova (bright), Luna (soft storytelling), and Sage (calm instruction). Male options are Felix (energetic), Milo (conversational), Atlas (neutral news), and Orion (deep documentary).
- Aria: Warm, clear narrator
- Nova: Bright, upbeat
- Luna: Soft, storytelling
- Sage: Calm, instructional
- Felix: Energetic, promo
- Milo: Friendly, conversational
Tone Variations
Each voice offers a consistent tonal profile suitable for repetitive course content. For instance, Sage provides a neutral, instructional tone ideal for procedural training, while Orion’s deep register suits documentary-style lectures. These presets are based on licensed recordings, ensuring professional consistency across large-scale productions.
Linguistic Suitability
All eight voices support 23 languages, including English, Spanish, German, Japanese, and Arabic. A single voice can deliver any supported language, allowing teams to maintain consistent narrator identity across multilingual courses. For non-English Latin script text, explicitly setting the language code prevents detection errors.
Pricing Comparison
Pricing for LMS content generation is calculated strictly on character count, including spaces and punctuation. The standard rate is $10 per 1 million characters, equating to $0.01 per 1,000 characters. Failed requests incur no charge, ensuring you pay only for successful audio synthesis.
This model eliminates monthly subscription fees and minimum spend requirements, allowing L&D teams to scale costs directly with course volume. Unlike complex tiered plans, our structure provides predictable unit economics for large-scale online course production without hidden infrastructure overhead.
Per Character Rates
The cost is $0.01 per 1,000 characters. This includes all spaces and punctuation marks within your input text. You are charged only when synthesis completes successfully; failed requests are free.
Trial Offerings
New accounts created via Google sign-in receive a $0.50 trial credit, valid for 7 days and sufficient for approximately 50,000 characters. Email-password accounts start with zero balance. This allows technical verification before committing to larger volumes.
Payment Methods
We accept USDT on the TRON network (TRC-20) for top-ups. The minimum deposit is $5, with automatic crediting within minutes of transfer. There are no credit cards, PayPal options, or VAT invoices, simplifying procurement for global L&D teams.
Integration Complexity
Integrating LMS Voice Core into your course production workflow requires minimal infrastructure overhead. The API endpoint structure mirrors the OpenAI speech endpoint, allowing you to use existing HTTP clients or the official OpenAI SDKs by simply adjusting the base_url to https://api.playa1one.com/v1. This compatibility ensures that your development team can leverage familiar tools without learning a proprietary protocol.
The primary requirement is implementing the Authorization: Bearer tts-... header using your unique API key. You send a JSON body containing the model, input text, and voice preset to receive the audio file. This straightforward request shape minimizes parsing errors and simplifies debugging during the initial integration phase with your LMS content management system.
API Documentation
The /v1/audio/speech endpoint accepts standard JSON inputs, including model (tts-1 or tts-1-hd), input (up to 4096 characters), voice, and response_format. You can also specify speed between 0.25 and 4.0. The /v1/voices endpoint provides a complete list of available presets and supported formats, ensuring you can programmatically select the appropriate voice for each course module.
- Standard JSON request body
- Consistent endpoint structure
- Clear parameter definitions
SDK Support
We do not provide a proprietary mobile or WordPress SDK, nor our own official SDK. Instead, we rely on the official OpenAI SDKs, which are widely available in Python, Node.js, and other common languages. By setting the base_url to https://api.playa1one.com/v1, you can use the same code structure as OpenAI, reducing the learning curve for your engineering team and ensuring consistent behavior across different platforms.
Implementation Time
For teams familiar with HTTP requests, integration typically takes a few hours to a single day. The primary task is handling the 60 requests per minute rate limit per key. For large-scale course generation, you may need to implement a queue system to split long texts into 4096-character chunks and manage the sequential processing of audio files without exceeding the limit.
Language Coverage
Selecting the right voice for your LMS content requires precise language support. Our API provides 23 specific languages, covering major markets for global e-learning. This scope ensures your courses reach the intended audience without requiring external localization services for basic narration needs.
The system handles language detection automatically based on script, but manual control is available for Latin-script text that might otherwise default to English. This flexibility prevents mispronunciation in multilingual course modules.
Supported Languages
We support 23 languages, including English, Spanish, French, German, Japanese, and Chinese. Any voice can speak any of these languages, allowing consistent branding across diverse course modules. Languages not supported include Vietnamese, Indonesian, Thai, and Ukrainian.
- Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, Turkish
Automatic Detection
If the language field is omitted, the system guesses the language from the script. Latin script text defaults to English unless specified otherwise.
Manual Overrides
For non-English Latin-script text, you must set the language parameter to ensure correct pronunciation. This is critical for mixed-language content or specific regional dialects in your LMS curriculum.
Data Privacy Features
Our API processes input text solely to generate the requested audio file, ensuring that your course content remains private. Generated audio is returned directly in the response and is not stored on our servers after delivery. This ensures that your instructional material is not retained for any secondary purpose.
Request metadata, including timestamp, character count, and status, is kept exclusively for accurate billing and usage tracking. This minimal data retention supports transparent accounting without compromising the confidentiality of your course scripts or learner data.
Training Data Usage
Input text is used only to produce the audio and is not used for training our models. Your specific course scripts and educational content remain distinct from our training dataset, ensuring that your intellectual property is not absorbed into future model iterations.
This separation guarantees that the voice engine’s general capabilities do not become dependent on your proprietary content, maintaining a clear boundary between your data and our infrastructure.
- Input text is not used for training.
Audio Storage Policy
Generated audio files are returned in the API response and are not stored on our servers. Once the audio is delivered to your LMS or application, we hold no copy of the final audio product.
This policy reduces storage costs for your team and ensures that sensitive course audio is controlled entirely by your infrastructure.
Key Management
Each account maintains one active API key. If you need to rotate credentials, issuing a new key immediately invalidates the old one, ensuring secure access control.
Request metadata is retained solely for billing accuracy, providing a clear audit trail of character usage without storing the actual content of your courses.
- One active key per account.
- New keys immediately invalidate old ones.

Performance Metrics
Performance metrics directly impact your course production timeline. Understanding generation speed and queue behavior helps L&D teams schedule audio synthesis during off-peak hours to ensure consistent delivery for large-scale video projects.
Rate limits and error handling determine how smoothly your automated workflows operate. Knowing these constraints prevents bottlenecks when processing thousands of lesson segments simultaneously.
Generation Speed
Long texts generate at roughly real-time speed, averaging 25 characters per second. Short phrases typically require a few seconds to process. Requests are processed sequentially, so heavy load may introduce queue delays.
- ~25 characters per second for long texts
- Few seconds for short phrases
- Sequential processing may cause queue delays under load
Request Limits
Each API key allows 60 requests per minute. New accounts start with a limit of 10 requests per minute until the first top-up is completed. This structure supports steady batch processing for course libraries.
- 60 requests per minute per key
- 10 requests per minute for new accounts
- Limit increases after first top-up
Error Rates
Failed synthesis requests incur no charge. If audio generation fails, the full amount is returned to your balance immediately. This ensures accurate billing regardless of transient processing issues.
- No charge for failed requests
- Full credit returned on error
- Transparent billing for all attempts
Use Case Suitability
The API supports distinct use cases across course production. Short quiz items process instantly, while long transcripts require chunking. Multilingual courses leverage 23 languages with automatic detection or manual overrides.
Short Quiz Content
Quiz questions under 4096 characters generate quickly. The 60 requests per minute limit handles typical quiz volumes without delay.
- Ideal for multiple-choice audio prompts
- Instant generation for short phrases
Long Lecture Transcripts
Transcripts exceeding 4096 characters must be split into segments. Each segment generates as a separate audio file, which are then joined. Processing occurs sequentially, so high volumes may queue.
- Requires client-side segmentation
- Audio files joined post-generation
Multilingual Courses
Supports 23 languages including Arabic, Chinese, and Spanish. The language field allows explicit specification, preventing incorrect detection for Latin-script texts. All voices support all listed languages.
- 23 supported languages
- Explicit language code override
Support and Maintenance
LMS teams managing large-scale course production require predictable support channels without the overhead of enterprise contracts. Our support structure is designed to be lightweight, ensuring that technical questions regarding API integration or billing discrepancies are addressed efficiently without unnecessary intermediaries.
Maintenance is handled directly by the engineering team, ensuring that updates to the TTS engine or API endpoints are communicated clearly. There are no complex tiered support levels; all users receive the same direct access to assistance via email.
Email Support Only
We do not offer phone support or live chat. All inquiries, including technical issues and billing questions, are handled via email. This approach ensures that every ticket is documented and traceable, which is critical for L&D teams auditing their vendor communications.
Response times are based on queue volume and are not guaranteed. For urgent integration blockers, detailed descriptions with request IDs help us resolve issues faster than verbal back-and-forth would allow.
- No phone number available
- No live chat widget
- All support via email
Documentation Quality
Our documentation provides clear, copy-pasteable examples for cURL, Python, and Node.js, aligning with the OpenAI SDK compatibility. It details every endpoint, parameter, and error code, reducing the time your developers spend guessing how to implement the API.
The docs include specific examples for splitting long texts into 4096-character chunks and handling rate limits, which are common challenges in LMS integrations.
- cURL, Python, and Node.js examples
- Rate limit handling details
- Error code reference
Update Frequency
Updates to the API are pushed regularly but without guaranteed schedules. When new voices or formats are added, the documentation is updated simultaneously. There is no SLA guaranteeing specific maintenance windows or uptime during these updates.
Users are not required to manually update SDKs, but it is recommended to check the /v1/models endpoint periodically to ensure compatibility with the latest engine versions.
Final Recommendations
For teams prioritizing predictable expenditure, our API is suitable for cost efficiency. At $0.01 per 1,000 characters, expenses scale linearly with course volume, avoiding fixed monthly overhead. Failed requests incur no charge, protecting your budget during integration testing or high-traffic periods. The USDT top-up model ensures immediate balance availability without subscription locks.
The API is suitable for ease of integration, requiring only a standard POST request to the speech endpoint. Existing OpenAI SDKs work by adjusting the base URL, allowing L&D engineers to swap the provider with minimal code changes. Documentation and ready-to-use curl examples reduce implementation time, while the uniform request shape simplifies automation across your LMS.
Suitable for Cost Efficiency
Pricing is strictly per character at $0.01 per 1,000 characters. There are no monthly plans, seats, or minimum spends. This structure allows large course libraries to scale costs directly with usage. Failed synthesis requests are free, ensuring you only pay for successful audio generation.
- No monthly fees or subscription locks
- Pay only for successful generations
- Immediate USDT top-ups for balance
Suitable for Ease of Integration
The endpoint mirrors the OpenAI speech API shape, allowing teams to use existing OpenAI SDKs by simply changing the base URL. This reduces development overhead for LMS integrations. Documentation includes ready-to-use curl examples, accelerating initial setup for engineering teams managing large-scale audio pipelines.
- Compatible with OpenAI SDKs
- Standard POST endpoint structure
- Ready curl examples provided
Suitable for Language Diversity
Support for 23 languages allows multinational course production without seeking additional vendors. Any voice can speak any supported language, providing consistent audio quality across diverse content. Automatic language detection works for standard scripts, with manual overrides available for mixed-language or ambiguous inputs.
- Supports 23 languages
- Any voice speaks any language
- Automatic detection with manual override
Limitations to Consider
While LMS Voice Core delivers reliable synthetic speech, teams must account for specific technical constraints. The absence of custom voice cloning means you cannot replicate your own brand ambassadors or instructors. Audio is generated in full chunks rather than streamed, requiring complete synthesis before playback begins. Additionally, there is no formal Service Level Agreement guaranteeing specific uptime percentages, so critical live broadcasts should buffer accordingly.
These limitations do not affect the core text-to-speech functionality but influence architectural decisions for real-time or highly branded course modules. Understanding these boundaries helps L&D teams select appropriate use cases, such as pre-recorded lectures versus interactive, real-time dialogue systems.
No Custom Voice Cloning
The API offers eight fixed presets derived from licensed LibriTTS-R recordings. You cannot upload a reference voice to create a custom clone of your instructors or brand characters. Each generated file uses one of the eight available voices (e.g., Aria, Felix, Sage), ensuring consistency but limiting unique brand voice replication.
No Streaming Support
Audio is returned as a complete file (mp3, wav, opus, flac, or pcm) after synthesis finishes. There is no WebSocket or streaming endpoint to receive partial audio chunks in real time. This requires waiting for the full request duration, which is roughly real-time for long texts but may introduce latency for immediate playback needs.
No SLA Guarantee
We do not provide a formal Service Level Agreement with uptime guarantees or financial credits for downtime. Requests are processed sequentially, so high-volume periods may result in queueing delays. While we strive for reliability, there is no contractual commitment to specific availability percentages or response time bounds.
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Failed requests incur no charge, ensuring you pay only for successful audio synthesis.
23 languages
Any voice speaks any of these languages.
Sources and further reading
- Wikipedia
- openai-python on GitHub
- IETF RFC 7845: Ogg Opus
- LibriVox public-domain audiobooks
- curl documentation
- FFmpeg documentation
- OpenAI API reference: create speech
- LibriTTS-R corpus (OpenSLR 141)
- ISO 639 language codes
- W3C WAI: making audio and video accessible
- MDN: Web Speech API
- TRON developer hub: TRC-20
