The Supertone API enforces request-rate limits to protect service stability. Limits scale with your plan; if you need higher capacity, an enterprise plan is available.Documentation Index
Fetch the complete documentation index at: https://docs.supertoneapi.com/llms.txt
Use this file to discover all available pages before exploring further.
Limits by tier
Speech generation (text_to_speech, stream_speech)
| Tier | Requests per minute |
|---|---|
| Free & Starter | 20 |
| Creator | 30 |
| Pro | 60 |
| Enterprise | Custom |
Voice cloning (create_cloned_voice)
| Tier | Requests per minute |
|---|---|
| Starter, Creator, Pro | 10 |
| Free | Not available |
| Enterprise | Custom |
When you exceed a limit
The API returns:429 response as a signal to pause and retry — see Retries and backoff.
Handling rate limits in code
- Python
- TypeScript
retry_config / retryConfig option that retries 429 (and transient 5xx) automatically with exponential backoff. See Retries and backoff for a tuned configuration.
Designing for the limit
- Batch upstream. If your app generates many sentences per user action (e.g. translating a paragraph), serialize them through a queue rather than firing them all at once.
- Throttle at the edge. Apply your own per-user limit so a single user’s burst can’t consume your account’s whole minute.
- Long-text auto-chunking. A single 2,000-character call becomes ~7 API calls under the hood. Account for that against your minute budget.
- Streaming chats. Sentence-by-sentence streaming TTS uses one API call per sentence. A multi-paragraph response might burn through the Free tier limit in a few seconds.
Need higher limits?
If you’re hitting the limit consistently or operating a high-traffic service, contact us for an enterprise plan with custom limits, dedicated capacity, and account-level support.Enterprise inquiry
Share your use case and traffic shape — we’ll respond with options.