Frequently asked questions
Which cloud TTS API is best for SaaS?
Q: Which cloud TTS API is suitable for SaaS? A: Our API is designed for SaaS teams moving beyond the browser’s Web Speech API. It offers reliable, scalable synthesis via a standard REST endpoint. With 60 requests per minute and support for 23 languages, it handles high-volume notification workflows efficiently without the latency of client-side generation.
How does pricing compare across providers?
We charge $10 per 1 million characters, or $0.01 per 1,000 characters. Failed requests are free. Unlike many competitors, we use USDT (TRC-20) for top-ups with no monthly plans or subscriptions. This flat rate simplifies cost forecasting for large-scale SaaS deployments.
Which API has the best voice quality?
We provide eight distinct presets based on licensed recordings from LibriTTS-R and LibriVox. Voices include aria, nova, luna, and sage for female tones, and felix, milo, atlas, and orion for male tones. Each generated file includes an inaudible watermark to identify synthetic speech.
Does this API support SSML?
No, this API does not support SSML. It accepts plain text input up to 4096 characters per request. You can adjust speed between 0.25 and 4.0, but there are no phoneme dictionaries or custom pronunciation lexicons available for fine-grained control over speech synthesis.
Can I clone voices with this API?
No, custom voice cloning is not offered. You cannot upload your own voice or design new voices. The API uses eight fixed presets derived from licensed recordings. If you need specific voice characteristics, you must select from the available male and female options.
Is there a free tier?
Yes, signing in with Google provides $0.50 of credit, valid for 7 days. Email-based accounts start without trial credit. There are no monthly plans or minimum spends. You can top up with USDT on the TRON network, with a minimum deposit of $5.
How many languages are supported?
We support 23 languages, including English, Spanish, French, German, Japanese, and Hindi. Any voice can speak any of these languages. If the language field is omitted, the system guesses from the script, defaulting to English for Latin text. Vietnamese and Thai are not supported.
What formats are available?
You can request audio in mp3, wav, opus, flac, or pcm formats. These are returned directly in the API response. The generated audio is not stored on our servers; it is delivered to your client for immediate use in your SaaS notification pipeline.
Is there a rate limit?
Yes, the limit is 60 requests per minute per key. Before your first top-up, this limit is 10 requests per minute. Longer texts should be split into 4096-character chunks and joined. Requests are processed sequentially, so high load may introduce queuing delays.
Do I need an enterprise contract?
No, there are no enterprise contracts, seats, or minimum spends. Accounts are created per site with Google or email. You can issue a new API key at any time, which immediately invalidates the old one. This model suits teams of any size without complex negotiations.
Is there an SLA?
No, we do not offer an SLA or uptime guarantee. There is no on-premise install option or data-center choice. We do not provide certifications like SOC 2 or HIPAA. Our service is designed for teams that prioritize cost and flexibility over guaranteed uptime metrics.
How is support handled?
Support is handled by email only. There is no phone number or live chat available. We do not provide dedicated account managers or priority support queues. All inquiries are managed through our standard email channel, ensuring direct communication without third-party intermediaries.
Can I use this for notifications?
Yes, this API is ideal for SaaS notifications and interfaces. It replaces the browser’s Web Speech API with a reliable cloud solution. With speeds roughly matching real-time generation, it efficiently handles bulk audio creation for user alerts, updates, and interface feedback mechanisms.
Is the API easy to integrate?
Yes, it uses the same request shape as the OpenAI speech endpoint. You can use official OpenAI SDKs by changing the base URL to https://api.playtop99.com/v1. Authentication uses a Bearer token, making it straightforward to integrate into existing Python, JavaScript, or Go applications.
Selection Criteria
Choosing a cloud TTS API for SaaS notifications requires balancing audio clarity with predictable costs. Our service delivers consistent voice quality across eight distinct presets, ensuring your interface sounds professional without the variability of browser-based solutions.
Language support spans 23 languages, covering major global markets. Our model handles diverse scripts with auto-detection, reducing configuration overhead for international applications.
Pricing is straightforward: $0.01 per 1,000 characters. This per-character model eliminates surprise bills for high-volume notification systems, making budget forecasting simple and accurate.
Voice Quality
Our eight voice presets range from warm narrators to energetic promos, all derived from licensed recordings. Each output includes an inaudible synthetic watermark, ensuring clear identification of generated audio without compromising listener experience.
The engine handles standard text well, though complex scripts may require character splitting for optimal results. Audio generation typically matches real-time speed on long texts, with short phrases taking a few seconds to process.
- Eight distinct voice presets
- Licensed source recordings
- Inaudible synthetic watermark
Language Coverage
Support covers 23 languages, including English, Spanish, German, Japanese, and Hindi. Any voice can speak any supported language, providing flexibility in voice selection regardless of target market.
Auto-detection works for Latin scripts, defaulting to English. For non-English Latin text, explicitly setting the language code ensures accurate pronunciation and tone.
- 23 supported languages
- Any voice for any language
- Auto-detection with fallback
Pricing Model
Cost is $10 per million characters, or $0.01 per 1,000 characters. Spaces and punctuation count toward the total, ensuring precise billing. Failed requests incur no charge.
Trial credits of $0.50 are available for Google sign-ups, valid for seven days. Top-ups via USDT (TRC-20) are processed automatically within minutes, with no monthly plans or subscriptions.
- $0.01 per 1,000 characters
- No charge for failures
- USDT top-up only
API Comparison
Cloud TTS differs from major platforms by eliminating monthly subscriptions and complex enterprise contracts. It offers a straightforward per-character model at $10 per million characters, with failed requests refunded immediately. This structure suits SaaS teams needing predictable costs.
The API mirrors the OpenAI speech endpoint shape, allowing teams to swap base URLs without code changes. This compatibility reduces integration friction for existing workflows, ensuring that standard HTTP clients and OpenAI SDKs function seamlessly with minimal configuration adjustments.
Cloud TTS vs Competitors
Unlike many competitors, we do not offer voice cloning or SSML support, focusing instead on reliable, scalable synthesis. The pricing is strictly usage-based, avoiding the overhead of tiered plans. This approach keeps overhead low for high-volume notification systems.
- No monthly plans or seats
- Immediate refund for failed synthesis
- No minimum spend requirements
SDK Compatibility
The request structure matches the OpenAI speech endpoint exactly. Teams can use official OpenAI SDKs by simply changing the base URL to https://api.playtop99.com/v1. This ensures broad compatibility with existing HTTP clients and libraries without requiring a proprietary SDK download.
Rate Limits
New accounts start with a limit of 10 requests per minute. After the first top-up, the limit increases to 60 requests per minute per key. Requests are processed sequentially, meaning high concurrency may introduce slight queuing delays during peak loads.
- 60 requests/minute after top-up
- 10 requests/minute initially
- Sequential processing queue
Voice Presets Analysis
Web Speech Logic provides eight distinct voice presets designed for diverse SaaS notification and interface needs. The selection spans warm narrators to energetic promo voices, ensuring your application sounds professional and engaging without requiring custom design work.
8 Preset Variety
The API offers eight presets: Aria, Nova, Luna, and Sage for female voices, alongside Felix, Milo, Atlas, and Orion for male voices. Each preset is tuned for specific use cases, from storytelling to news delivery.
- Aria: Warm, clear narrator
- Nova: Bright, upbeat
- Luna: Soft, storytelling
- Sage: Calm, instructional
- Felix: Energetic, promo
- Milo: Friendly, conversational
- Atlas: Neutral, news
- Orion: Deep, documentary
Gender and Tone
Voices cover a spectrum from deep and documentary-style to bright and conversational. This variety allows SaaS teams to match the tone of notifications to the context, whether it is a friendly reminder or a serious alert.
Licensing Source
Every generated file carries an inaudible watermark marking it as synthetic speech. The voices are based on licensed recordings: LibriTTS-R (CC BY 4.0), from LibriVox public-domain audiobook readings.
Language Support
Our API supports 23 languages, ensuring broad coverage for global SaaS notifications and user interface voiceovers. This allows teams to deploy localized audio content without managing multiple voice providers.
The system handles language detection automatically for Latin-script text, defaulting to English. For other Latin-based languages, explicitly setting the language parameter ensures accurate synthesis.
23 Languages List
We support Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, and Turkish.
Any voice can speak any of these languages, providing flexibility in tone while maintaining linguistic accuracy.
- Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, Turkish
Unsupported Languages
Vietnamese, Indonesian, Thai, Ukrainian, Romanian, Czech, Bengali, and other regional dialects are not supported. Teams targeting these markets should verify compatibility before integration.
Auto-Detection
If the language field is omitted, the API guesses the language based on the script. Latin script defaults to English, which may misinterpret non-English Latin text.
For non-English Latin-script text, always set the language parameter to ensure correct pronunciation and prosody.
Pricing Structure
Cloud synthesis 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 incur no charge, ensuring you only pay for successful audio generation. This model scales linearly with volume, making it predictable for large notification systems.
Per Character Cost
Each request processes up to 4096 characters. The cost is strictly per character generated, including spaces. This unit-based approach avoids complex tiered pricing, allowing precise budget forecasting for high-volume SaaS interfaces.
- Rate: $0.01 per 1,000 characters
- Includes spaces and punctuation
- Free on failure
Trial Credit
Signing in with Google provides $0.50 in trial credit, valid for 7 days. This covers approximately 50,000 characters for initial testing. Email-based accounts do not receive this trial credit by default.
Top-Up Method
The USDT top-up model is simple and direct. Payments are made via USDT on the TRON network (TRC-20) only. The minimum top-up amount is $5, with automatic crediting within minutes of transfer. There are no subscriptions, invoices, or VAT charges.
Technical Features
Synthesizing audio for SaaS notifications requires flexibility across playback environments. The API supports five distinct output formats—mp3, wav, opus, flac, and pcm—ensuring compatibility with both legacy systems and modern web clients. This range allows teams to balance file size and fidelity based on specific infrastructure needs.
Output Formats
Each format serves a different use case. MP3 offers efficient compression for web delivery, while WAV and FLAC provide lossless quality for archival or high-fidelity applications. PCM is available for raw audio processing, and OPUS suits low-bandwidth mobile notifications.
- mp3, wav, opus, flac, pcm
Speed Control
Generation speed is adjustable from 0.25x to 4.0x. This allows fine-tuning the playback rate to match UI constraints or user preference without re-synthesizing the entire text. For long notifications, adjusting speed can significantly reduce processing time and API costs.
Watermarking
Every generated audio file includes an inaudible watermark. This marks the content as synthetic speech, providing transparency for end-users and helping distinguish AI-generated notifications from human-recorded messages. The watermark is embedded without affecting audio quality or playback compatibility.
Scalability
Scalability for SaaS notification systems depends on predictable throughput and graceful degradation under load. Our architecture processes requests sequentially, meaning high concurrency requires careful rate management to avoid delays.
Rate Limits
Each API key is capped at 60 requests per minute. New accounts start with a stricter limit of 10 requests per minute until the first top-up is processed. This ensures fair usage during initial scaling phases.
- Standard limit: 60 requests/minute per key
- Initial limit: 10 requests/minute
- Limit resets every 60 seconds
Queue Handling
Requests are processed in order. If you exceed the rate limit, subsequent requests wait in a queue rather than failing immediately. This prevents data loss but increases latency during peak usage.
- Sequential processing ensures audio consistency
- Queues prevent immediate failure
- Latency increases under high load
Request Volume
For large-scale deployments, split long texts into 4096-character chunks and join the resulting audio files. This approach maintains compatibility with the sequential processing model and allows for parallel generation of distinct segments.
- Max 4096 characters per request
- Split long texts manually
- Join audio files post-generation

Data Policy
Input text is used strictly to produce the audio file and is not retained for model training. This ensures your notification content remains proprietary and does not influence future voice generation models. Once the audio is returned in the response, the raw input is discarded, preserving the integrity of your user data.
No Training Usage
Your text inputs are processed solely for the immediate generation of the audio file. We do not use your content to train or improve our TTS engines, ensuring that your specific notification scripts and user data remain isolated from our broader model datasets.
Metadata Retention
We retain request metadata including timestamp, character count, and status for accurate billing and usage tracking. This data is necessary to calculate charges based on the per-character model and to verify that requests were processed correctly, but it does not include the audio content itself.
Privacy
Generated audio files are returned in the response stream and are not stored on our servers after delivery. This minimizes the risk of data leakage for sensitive notifications. Only the metadata required for billing and audit purposes is kept, ensuring a clear separation between operational data and content.
- Text used only for immediate synthesis
- No use of input for training models
- Audio not stored after response delivery
- Metadata kept for billing accuracy
Integration Ease
Integration is straightforward because our API mirrors the OpenAI speech endpoint structure. This allows you to reuse existing OpenAI SDKs by simply updating the base_url to https://api.playtop99.com/v1 and swapping the authentication key. No custom client libraries or complex migration logic are required.
OpenAI SDK Support
Use any official OpenAI SDK by pointing it to our API base. The request shape remains identical, ensuring immediate compatibility with your current integration patterns.
- Identical JSON body structure to OpenAI
- Zero code changes for standard SDKs
- Simple
base_urlconfiguration update
Curl Example
Test the endpoint immediately with a standard HTTP request. Send a POST to /v1/audio/speech with your Bearer token, model, and text input to receive the audio file.
- Standard HTTP POST method
- Bearer token authentication
- JSON payload with
modelandinput
Documentation
Complete reference details are available at /docs/. It covers all request fields, including voice, speed, and response_format options, along with rate limit specifics.
Support and SLA
Our support infrastructure relies entirely on asynchronous communication. When technical issues arise during integration or billing cycles, our team handles all inquiries via email. There is no phone number for immediate voice support, nor is there a live chat widget available on the site. This approach ensures that every ticket is documented and resolved thoroughly without the pressure of real-time expectations.
Email Support Only
All communications are directed to our support email address. We do not maintain a helpdesk phone line or real-time chat interface. This allows us to provide detailed, written responses that can be referenced later in your engineering logs.
No SLA Guarantee
We do not offer a Service Level Agreement (SLA) or uptime guarantee. While our infrastructure is designed for reliability, we do not contractually promise specific availability percentages. There are no enterprise contracts or certified uptime metrics to reference.
Uptime Notes
There is no certified uptime guarantee. Our independent infrastructure is designed for reliability.
Final Recommendation
Choosing the right TTS provider depends on your specific constraints. Our API offers a distinct balance of cost efficiency, voice variety, and integration ease for SaaS notifications.
Cost
The flat rate of $0.01 per 1,000 characters makes this ideal for high-volume notification systems. Failed requests are free, protecting your budget during peak loads or network instability.
Quality
Eight distinct presets provide clear, natural speech without the need for complex configuration. The licensed source material ensures consistent audio quality across all 23 supported languages, suitable for professional interfaces.
Simplicity
Using the standard OpenAI SDK format reduces integration friction. Changing the base URL is all that is needed to switch providers, allowing teams to deploy quickly without learning new endpoints.
Implementation Steps
Moving from evaluation to production requires a structured onboarding process. This guide outlines the three critical steps to integrate our cloud TTS API into your SaaS notification system, ensuring reliable voice generation for your user base.
By following these steps, you can establish a robust pipeline for converting text alerts into clear audio notifications, leveraging our scalable infrastructure and straightforward pricing model.
Get API Key
Navigate to the /get-api-key/ page and sign up using Google or email. Once authenticated, your unique API key is displayed immediately. This key authenticates all subsequent requests to the API base URL.
- Sign up via Google or email
- Retrieve key from dashboard
- Key is active immediately
Make First Request
Send a POST request to https://api.playtop99.com/v1/audio/speech with your JSON payload. Use the OpenAI SDK by setting the base URL to https://api.playtop99.com/v1. Ensure your text is under 4096 characters and specify a voice preset like 'aria' or 'nova'.
- Use POST /v1/audio/speech
- Set base_url for OpenAI SDK
- Keep input under 4096 chars
Monitor Usage
Track your character consumption and balance directly in the account dashboard. Each request consumes credits based on the input length. Failed requests do not incur charges, ensuring you only pay for successful synthesis.
- View real-time balance
- Monitor character count
- Check failed requests
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Your team receives seamless alerts directly within the unified interface for instant awareness and streamlined collaboration.
23 languages
Any voice speaks any of these languages.
Sources and further reading
- Wikipedia
- curl documentation
- Creative Commons Attribution 4.0
- W3C WAI: making audio and video accessible
- LibriTTS-R corpus (OpenSLR 141)
- Node.js documentation
- openai-python on GitHub
- openai-node on GitHub
- ISO 639 language codes
- IETF RFC 7845: Ogg Opus
- OpenAI API reference: create speech
- LibriVox public-domain audiobooks
