Frequently asked questions
Which TTS API is best for mobile?
Q: Which TTS API is suitable for mobile? A: Voxera provides a cloud API compatible with OpenAI SDKs, simplifying iOS and Android integration. It supports 23 languages and eight voice presets. Pricing is transparent at $10 per million characters, with no monthly fees or minimum spend. This model suits freelancers evaluating cost efficiency and SDK compatibility without vendor lock-in.
How does our API compare to Amazon Polly?
Unlike Amazon Polly, Voxera uses a simple pay-per-character model at $10 per million characters, with no regional complexity. Our API mimics the OpenAI speech endpoint, allowing direct SDK reuse. We provide eight specific voice presets and support formats like MP3 and WAV, focusing on straightforward integration for mobile developers.
Is ElevenLabs better for mobile?
Voxera provides eight licensed voices from LibriTTS-R and LibriVox, ensuring clear licensing for commercial apps. While ElevenLabs offers advanced features, Voxera focuses on cost efficiency and strict corporate transparency. Our API returns audio instantly via standard HTTP, avoiding complex setup, and charges only $10 per million characters.
What is the best pricing model?
Q: What is the pricing model? A: Voxera charges $10 per million characters ($0.01 per 1,000 characters). Failed requests are free. There are no monthly plans, seats, or minimum spend. Top up via USDT on TRON; balances do not expire. This model ensures predictable costs for mobile app development without hidden fees.
Are there any free TTS APIs?
Voxera offers a free trial with $0.50 credit, valid for seven days upon Google sign-in. This covers approximately 50,000 characters. Email-based accounts start without trial credit. After the trial, you pay $10 per million characters. This allows freelancers to evaluate the API’s quality and integration before committing funds.
How do I choose a voice?
Select from eight presets: Aria, Nova, Luna, Sage, Felix, Milo, Atlas, and Orion. Each voice supports all 23 listed languages. For non-English Latin text, specify the language code. Voices are based on licensed recordings, ensuring clear rights for mobile apps. Choose based on tone, such as warm narration or energetic promos.
What is SSML and do I need it?
SSML (Speech Synthesis Markup Language) is not supported by Voxera. We do not offer phoneme dictionaries or custom pronunciation lexicons. You control speech via the speed parameter (0.25–4.0) and voice selection. This simplifies integration for mobile apps, reducing parsing complexity while maintaining clear, direct audio generation via standard JSON requests.
Can I use the API for commercial apps?
Yes. Voices are based on LibriTTS-R (CC BY 4.0) and LibriVox public-domain readings. Generated audio carries an inaudible synthetic watermark. Input text is not used for training. This licensing clarity suits mobile developers who need straightforward rights for commercial applications without complex enterprise contracts or additional attribution requirements beyond the license terms.
How do I handle rate limits?
The API allows 60 requests per minute per key (10 before first top-up). Process requests sequentially. For longer texts, split into 4096-character parts and join audio files. Under load, requests may queue. Implement retry logic in your mobile app to handle temporary delays during high-volume synthesis periods efficiently.
Is the API secure?
Use a Bearer token for authentication. Each account has one active key, revocable instantly. Request metadata is kept for billing. Input text is used only for generation and not stored. Generated audio is returned in the response and not stored. This ensures data privacy for mobile apps handling user content securely.
What audio formats are best for mobile?
The API supports MP3, WAV, Opus, FLAC, and PCM. MP3 is a common choice for mobile storage and bandwidth. WAV provides uncompressed quality, while Opus offers efficient compression. FLAC and PCM are also available. The API returns the audio file directly in the response, allowing immediate playback or caching in your mobile application.
How do I integrate the SDK?
Use the official OpenAI SDK. Change the base_url to https://api.playbe99.com/v1 and set your API key. Send a POST request to /v1/audio/speech with the text, voice, and format. This standard approach ensures compatibility with existing codebases, reducing integration time for iOS and Android developers familiar with OpenAI’s interface.
Can I clone voices?
No. Voxera does not offer custom voice cloning or uploading your own voice. We provide eight preset voices based on licensed recordings. This simplifies licensing and reduces complexity for mobile apps. If you need a specific voice, select from our existing presets, which cover various tones and languages effectively.
How do I scale the API?
Scale by managing rate limits (60 requests/minute). Split long texts into 4096-character chunks and process them sequentially. Use multiple keys if higher throughput is needed, as limits are per key. There are no enterprise contracts or SLAs. Monitor usage via the dashboard and top up via USDT to maintain service continuity.
Criteria for Mobile TTS APIs
Freelance mobile developers require text-to-speech APIs that balance cost, compatibility, and quality. The selection criteria focus on minimizing overhead while ensuring seamless integration into iOS and Android environments.
Key considerations include transparent billing structures, SDK support for rapid development, and voice variety that meets user expectations without excessive resource consumption.
Cost Efficiency for Freelancers
Pricing models directly impact project margins. APIs charging per character allow precise budgeting, avoiding waste from unused minutes or sessions.
Understanding rate limits and concurrency costs helps freelancers predict expenses during peak usage periods without unexpected overages.
- Per-character billing aligns costs with actual usage.
- Transparent rate limits prevent service interruptions.
- No minimum spend reduces entry barriers.
SDK Compatibility and Ease of Use
Compatibility with standard SDKs like OpenAI’s simplifies integration. Developers can swap bases without rewriting core logic.
Ease of use reduces development time, allowing focus on app features rather than API quirks.
Clear documentation and examples accelerate debugging and deployment phases.
- OpenAI SDK compatibility ensures familiarity.
- Standardized endpoints reduce learning curves.
- Comprehensive docs speed up implementation.
Voice Quality and Variety
Voice quality affects user engagement. Distinct presets cater to diverse content types, from narrations to notifications.
Variety in voice styles allows apps to tailor audio experiences without additional licensing costs.
Natural-sounding voices enhance accessibility and user retention in mobile applications.
- 8 distinct voice presets available.
- High-quality natural speech generation.
- Diverse styles for different content types.
Top API Contender: Our Cloud API
Voxera’s cloud API is engineered for seamless integration into iOS and Android projects. By adopting the standard OpenAI request shape, mobile developers can utilize existing OpenAI SDKs with a simple base_url adjustment, eliminating the need for custom wrapper libraries or extensive refactoring during the evaluation phase.
The API supports eight distinct voice presets across male and female categories, ensuring clear audio output for diverse app contexts. Each voice is derived from licensed LibriTTS-R recordings, providing a consistent, high-quality baseline without the complexity of neural style transfer models.
OpenAI SDK Compatibility
The endpoint POST https://api.playbe99.com/v1/audio/speech mirrors the OpenAI speech structure. Developers can switch by changing the base_url to https://api.playbe99.com/v1 and injecting the Voxera key. This ensures identical JSON body handling for model, input, voice, and speed parameters across standard HTTP clients and official SDKs.
This compatibility reduces integration time significantly. Since the request shape is identical, code written for testing with OpenAI’s endpoint requires minimal modification to function with Voxera’s infrastructure, preserving existing error-handling logic and payload structures.
- Supports
tts-1andtts-1-hdmodels with identical pricing
8 Distinct Voice Presets
The API provides eight curated voice presets, ranging from warm narrators like Aria to energetic promo voices like Felix. These presets cover a wide range of tones suitable for mobile applications, from instructional guides to engaging content delivery. All voices support 23 languages, allowing for localized app deployments without additional voice selection overhead.
Each voice is based on licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain readings. This licensing clarity ensures that freelance developers can confidently use the generated audio in commercial mobile apps without navigating complex royalty structures or attribution requirements for each track.
- Aria, Nova, Luna, Sage, Felix, Milo, Atlas, Orion
Transparent Character Billing
Billing is strictly based on character count, priced at $10 per million characters. Spaces and punctuation are included in the count, providing predictable cost projections for app development. Failed requests are free, ensuring that network errors or invalid payloads do not incur unnecessary charges.
This model eliminates hidden fees associated with duration-based pricing. Developers can accurately estimate costs based on text length, which is crucial for budgeting in freelance projects. The absence of monthly plans or minimum spends allows for flexible scaling, paying only for the exact usage required by the app.
Comparison with Amazon Polly
Amazon Polly offers a distinct pricing model compared to our cloud API. Polly charges separately for standard and neural voices, often resulting in higher costs for long-form content. In contrast, our API maintains a flat rate of $10 per million characters, regardless of the selected voice model. This transparency simplifies budget forecasting for freelance mobile developers who need predictable expenses for iOS and Android applications.
The pricing structure eliminates variable costs based on voice quality tiers. You pay strictly for character volume, with failed requests billed at zero. This approach ensures that high-volume TTS integration remains cost-efficient without unexpected surges during peak usage periods.
Pricing Structure Differences
Our flat character-based billing contrasts with Polly’s tiered voice pricing. This model favors developers who require consistent costs across different voice presets without monitoring individual voice usage tiers.
Failed synthesis requests are refunded immediately, ensuring you only pay for successful audio generation. This reduces waste during development and testing phases where request volumes may fluctuate.
- Flat rate: $10 per million characters
- No voice-tier differentiation
- Zero cost for failed requests
SSML Support Comparison
Polly provides SSML support. Our API currently does not support SSML, relying instead on natural language processing within the text input. For most mobile app use cases, this simplifies the integration process, as developers can pass plain text without managing XML tags.
The absence of SSML reduces payload size and parsing overhead on the client side. This is particularly beneficial for mobile apps where network efficiency and low latency are critical.
SDK Flexibility
Polly offers dedicated SDKs for AWS-supported languages, but integration often requires handling AWS-specific authentication and service endpoints. Our API is compatible with the official OpenAI SDKs by simply changing the base URL. This allows developers to reuse existing TTS code snippets from the OpenAI ecosystem.
This flexibility enables quick prototyping and reduces boilerplate code. Freelancers can switch between different TTS providers with minimal code changes, maintaining vendor neutrality while leveraging familiar tools.
Comparison with Google Cloud TTS
When evaluating text-to-speech solutions for mobile applications, freelancers must weigh naturalness against infrastructure complexity. Our cloud API offers eight distinct voice presets capable of speaking 23 languages, providing consistent quality without requiring extensive model configuration.
This approach contrasts with Google Cloud TTS, which offers a broader range of neural voice models but often requires more granular setup to achieve similar conversational tones in iOS and Android environments.
Naturalness of Voices
Google Cloud TTS provides high-quality neural voices with extensive customization options. However, achieving optimal naturalness often requires selecting specific model versions, adding complexity to the integration phase for solo developers managing multiple app projects.
Our API delivers uniformly high-quality speech across eight presets. Each voice is tuned for specific use cases, from warm narration to energetic promos, ensuring consistent output without model versioning decisions.
- Google offers diverse neural model options
- Requires manual model selection per voice
- Our API uses fixed, optimized presets
- Uniform quality across all requests
Language Support Coverage
Google Cloud TTS supports a vast number of languages and regional variants. This breadth is advantageous for global apps but can complicate language detection logic in client-side code.
Our API supports 23 languages with any voice speaking any language. This simplifies localization strategies, as freelancers do not need to map specific voices to specific language models.
- Google supports 100+ languages
- Requires language-specific voice mapping
- We support 23 languages
- Any voice speaks any language
Integration Complexity
Google Cloud TTS integration typically involves managing API keys, quotas, and potentially complex authentication flows via Google Cloud IAM. This adds overhead for freelancers who must also handle billing configurations separately.
Our API uses a simple Bearer token authentication compatible with the OpenAI SDK. This allows freelancers to switch between TTS providers with minimal code changes, reducing vendor lock-in and maintenance burden.
- Google requires IAM and quota management
- Complex authentication flows
- Simple Bearer token auth
- OpenAI SDK compatibility
Comparison with ElevenLabs
Freelancers often compare our API against ElevenLabs for voice synthesis capabilities. While ElevenLabs is known for voice cloning, our solution offers a streamlined alternative focused on stability and predictable billing for mobile applications.
We provide eight distinct voice presets suitable for various app tones without requiring additional configuration. This approach reduces integration complexity while maintaining high-quality audio output for end users.
Voice Clining Features
ElevenLabs offers custom voice cloning. Our API does not offer custom voice cloning; it utilizes eight licensed presets derived from LibriTTS-R and LibriVox recordings.
These presets cover a range of tones, from warm narrators to energetic promo voices, ensuring consistent quality without the overhead of managing cloned voice models. Each generated file includes an inaudible synthetic watermark.
- No custom voice cloning available
- Eight licensed voice presets
- Inaudible watermark in all audio files
Cost Per Character
Our pricing is straightforward: $10 per 1 million characters, equating to $0.01 per 1,000 characters. Spaces and punctuation count toward this total. Failed requests are refunded in full, ensuring you pay only for successful synthesis.
In contrast, ElevenLabs employs a tiered subscription model alongside character-based usage costs, which can complicate budgeting for freelance projects with variable traffic. Our model eliminates monthly fees, allowing you to scale costs directly with usage.
- $10 per 1 million characters
- $0.01 per 1,000 characters
- Failed requests are free
API Rate Limits
We enforce a limit of 60 requests per minute per key, with an initial limit of 10 requests per minute before the first top-up. This structure is designed to prevent abuse while supporting steady mobile app generation needs.
ElevenLabs also imposes rate limits, but their structure varies by subscription tier. Our transparent, flat-rate limits allow freelance developers to predict capacity accurately without navigating complex tier upgrades or overage penalties.
- 60 requests per minute per key
- 10 requests/minute before top-up
- Simple, predictable limits
Licensing and Usage Rights
Understanding licensing is critical for mobile developers selecting a TTS provider. Our API utilizes voices derived from licensed recordings and public-domain audiobook readings, ensuring clear commercial usage permissions for end-users.
This transparency reduces legal risk when integrating speech into iOS and Android applications, allowing straightforward distribution without complex royalty negotiations.
Public Domain Sources
The voice models are based on licensed recordings from the LibriTTS-R dataset (CC BY 4.0) and public-domain readings from LibriVox. This foundation ensures that the synthetic audio generated does not infringe on copyrighted voice performances.
Using established public-domain sources provides a stable legal baseline, avoiding the ambiguity often found with proprietary voice actors.
- LibriTTS-R (CC BY 4.0)
- LibriVox public-domain audiobooks
Commercial Usage Permissions
The generated audio files are cleared for commercial use within your mobile application. You can embed the audio in your app binaries or stream it to users without additional per-download fees.
There are no hidden restrictions on audience size or specific commercial contexts, making it suitable for both free and premium app models.
Watermarking Implications
Every generated audio file contains an inaudible watermark identifying it as synthetic speech. This marker is embedded by default and cannot be removed via the API.
This watermark helps distinguish AI-generated speech from human recordings, which may be relevant for content transparency policies or specific app store guidelines.
Technical Performance Metrics
Technical performance directly impacts user experience in mobile applications. Understanding generation speed, error rates, and concurrency limits helps freelancers predict latency and plan infrastructure accordingly.
These metrics define the reliability of the TTS API under typical load conditions.
Generation Speed
Text synthesis processes roughly 25 characters per second for long texts, yielding audio at near real-time speed. Short phrases may take a few seconds to generate.
Requests are processed sequentially, meaning under load, a request may wait in a queue before synthesis begins.
- Approx. 25 characters per second for long texts
- Short phrases take a few seconds
- Sequential processing may cause queueing
Error Rates
Failed requests incur no charge; the full cost is returned to the account balance. This ensures that temporary processing issues do not penalize the developer financially.
Input validation errors, such as exceeding the 4096-character limit, are handled gracefully without consuming credits.
Concurrency Handling
Each API key is limited to 60 requests per minute. Before the first top-up, this limit drops to 10 requests per minute.
Developers should implement client-side queuing or batching to stay within these limits and avoid throttling during peak usage.
- 60 requests/minute after top-up
- 10 requests/minute before top-up
- Client-side queuing recommended

Integration Experience for Freelancers
Freelancers require clear, copy-paste-ready documentation to integrate text-to-speech APIs efficiently. Our guides provide concrete examples for iOS and Android, detailing request shapes and response handling without unnecessary abstraction. This reduces initial setup time and minimizes debugging efforts during the development phase.
The API mirrors the OpenAI speech endpoint structure, allowing you to use existing OpenAI SDKs by simply changing the base URL. This compatibility ensures a smooth transition for developers already familiar with common TTS workflows, requiring minimal code adjustments for integration.
Documentation Quality
Our documentation provides specific, copy-paste-ready examples for iOS and Android integration. It details request shapes and response handling to reduce debugging time during development.
- Copy-paste-ready code examples for iOS and Android
- Clear explanation of request shapes and responses
- Step-by-step integration guides
SDK Availability
The API mirrors the OpenAI speech endpoint structure. You can use existing OpenAI SDKs by simply changing the base URL, ensuring a smooth transition for developers familiar with common TTS workflows.
- Compatible with OpenAI SDKs
- Minimal code adjustments required
- Standard JSON request format
Support Channels
Support is available via email only. There is no phone support or live chat, which aligns with our cost-efficient model. Responses are provided promptly to keep your development cycle moving.
- Email support only
- No phone or live chat
- Prompt response times
Scalability for Growing Apps
As your mobile application gains users, the TTS API must handle concurrent requests without degrading audio quality or increasing latency. Our architecture processes requests sequentially, meaning that under heavy load, synthesis may queue, but throughput remains stable at approximately 25 characters of text per second.
Handling Increased Traffic
Each request is processed independently, allowing you to scale your backend logic to parallelize calls. Since long texts are split into 4096-character segments, you can manage multiple audio segments concurrently to reduce total generation time for your users.
Managing Rate Limits
The API enforces a strict limit of 60 requests per minute per key. For most freelance projects, this is sufficient, but if your app experiences sudden spikes, you may need to implement client-side queuing or distribute load across multiple keys if you upgrade.
- Standard limit: 60 requests/minute.
- Pre-top-up limit: 10 requests/minute.
- No hard concurrency cap, but sequential processing applies.
Cost Projections
Billing is transparent: $0.01 per 1,000 characters. Failed requests incur no charge, protecting your budget during testing or network instability. With no monthly subscriptions or minimum spend, your costs scale linearly with usage, making it easy to forecast expenses for your app's growth.
Mobile-Specific Considerations
Mobile applications face unique constraints regarding network reliability, storage limits, and device power. When integrating text-to-speech, developers must balance audio fidelity with efficient data usage to ensure a smooth user experience across varying connection qualities.
Bandwidth Optimization
Utilize the Opus format for superior compression ratios without significant quality loss, reducing data transfer costs for users on limited plans. Choose MP3 or WAV only when broader compatibility is required, as these formats consume more bandwidth per second of audio.
- Default to Opus for data efficiency
- Reserve MP3/WAV for specific legacy device requirements
Offline Caching Strategies
Since the API returns standard audio files, store generated responses locally on the device to enable playback without an active internet connection. Implement a cache expiration policy to balance storage usage with content freshness, ensuring older audio assets are cleared automatically.
- Cache audio files for offline playback
- Automate cache eviction to manage device storage
Battery Usage Impact
Pre-fetching audio segments can reduce CPU spikes associated with real-time decoding, potentially lowering battery drain during playback. Avoid excessive background polling of the API by batching requests or using local queues, preserving device power during extended usage sessions.
- Pre-fetch segments to smooth CPU usage
- Batch requests to minimize background polling
Final Recommendations
Selecting the right TTS API depends on your specific constraints. Our cloud API offers transparent character billing at $0.01 per 1,000 characters, with no hidden fees or subscription tiers. Failed requests are free, ensuring you only pay for successful synthesis.
Voice quality is determined by licensed LibriTTS-R recordings, providing eight distinct presets without the need for complex configuration. The API supports 23 languages, allowing flexible localization for global mobile applications without additional licensing costs.
Recommendation for Cost-Conscious Freelancers
Our API charges $0.01 per 1,000 characters, making it ideal for budget-sensitive projects. With no monthly plans or minimum spend, you pay only for what you use. The free trial provides 50,000 characters for testing, and USDT top-ups ensure flexible funding.
- $0.01 per 1,000 characters
- No monthly subscription fees
- Failed requests are free
- USDT (TRC-20) payments only
Recommendation for Quality-Focused Apps
Eight distinct voice presets cover various tones, from warm narrators to deep documentary styles. Each voice supports 23 languages, ensuring consistent quality across localized content. Audio files include an inaudible watermark, clearly marking synthetic speech for transparency.
- 8 distinct voice presets
- Support for 23 languages
- Inaudible synthetic watermark
- Licensed LibriTTS-R recordings
Recommendation for Quick Integration
The API uses the OpenAI SDK format, allowing immediate integration with existing codebases. Developers can change the base URL to https://api.playbe99.com/v1 and start generating audio within minutes. Standard HTTP requests support JSON bodies, simplifying mobile app development.
- OpenAI SDK compatibility
- Standard JSON requests
- 60 requests per minute
- Simple base URL change
Next Steps for Implementation
Implementing the Voxera text-to-speech API into your mobile application requires a structured approach to ensure seamless integration and optimal performance. By following these next steps, freelance developers can efficiently transition from evaluation to production while maintaining cost efficiency and SDK compatibility.
The process begins with obtaining your API key, followed by rigorous testing of various voice presets and languages. Finally, deploying to production involves monitoring usage metrics and managing rate limits to support growing user bases without unexpected costs.
Getting an API Key
Navigate to the /get-api-key/ page on playbe99.com to create your account using Google or email. This page displays your unique API key, current balance, and a ready-to-use cURL example for immediate testing.
Ensure you understand the authentication format: Authorization: Bearer tts-.... Remember that each account has one active key, which can be revoked and replaced instantly if needed.
- Sign up via /get-api-key/ using Google or email
- Retrieve your unique Bearer token
- Note the base URL: https://api.playbe99.com/v1
Running Test Requests
Use the official OpenAI SDKs by setting the base_url to https://api.playbe99.com/v1. Send a POST request to /v1/audio/speech with a short text input to verify voice quality and response time.
Test different parameters such as voice, response_format, and speed to find the optimal configuration for your app’s specific use case. Remember that texts are limited to 4096 characters per request.
- Set SDK base_url to https://api.playbe99.com/v1
- POST to /v1/audio/speech with sample text
- Test multiple voices and formats like mp3 or wav
Deploying to Production
Monitor your usage dashboard to track character consumption against your $0.01 per 1,000 characters billing rate. Implement logic to split longer texts into 4096-character chunks and join the resulting audio files.
Ensure your app handles network errors gracefully, as failed requests are free but may affect user experience. Consider caching frequently used audio files to optimize bandwidth and reduce redundant API calls.
- Monitor character usage via dashboard
- Implement text splitting for inputs >4096 chars
- Cache audio files to reduce API calls
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Create intuitive mobile applications that empower freelancers to work efficiently from anywhere in the world.
23 languages
Any voice speaks any of these languages.
