Rate Limits, Quotas & Plans
Requests are limited per plan to ensure fair access. Limits apply per account: all of an account's API keys share the same limits. There are three plans: Free, Premium, and Custom (a contract agreed with AyaData, described below).
Per-Endpoint Rate Limits
Each endpoint has a sliding-window rate limit (maximum requests per 60-second window):
| Endpoint | Free (req/min) | Premium (req/min) |
|---|---|---|
| /transcribe | 10 | 60 |
| /translate | 30 | 150 |
| /synthesize | 5 | 25 |
| /transcribe_and_translate | 5 | 25 |
| /translate_and_synthesize | 3 | 15 |
Authentication endpoints are also rate-limited: 3 requests per 60 seconds per IP address.
Daily Request Caps
Maximum requests per day, per model:
| Model | Free | Premium |
|---|---|---|
| ASR | 50 | 500 |
| MT | 50 | 1,000 |
| TTS | 50 | 1,000 |
Monthly Volume Caps
Maximum consumption per 30-day cycle, counted from when your key was activated (or your plan last changed):
| Model | Unit | Free | Premium |
|---|---|---|---|
| ASR | minutes | 60 | 3,000 |
| MT | characters | 50,000 | 2,000,000 |
| TTS | characters | 30,000 | 2,000,000 |
Rate Limit Headers
Responses on every plan include:
X-RateLimit-Limit: 25 # requests allowed per 60-second window X-RateLimit-Remaining: 24 # left in the current window X-RateLimit-Tier: premium
When Limits Are Exceeded
The error code is RATE_LIMIT_EXCEEDED and the message says which limit was hit (per-minute window, daily cap or monthly volume) and when it resets. Per-minute limits also send a Retry-After header with the seconds to wait. See Error Handling.
Custom Plans
A custom plan is a contract agreed with AyaData for a set amount of processing over a set period, for example "100 hours of speech-to-text and 2 million characters of text-to-speech from 1 October to 31 December". It is set up by our team; your API keys don't change.
| Term | How it works |
|---|---|
| Dates | Calls work from the start date through the end date (inclusive). Outside those dates they return 403 CONTRACT_NOT_STARTED or 403 CONTRACT_ENDED. |
| Allocation | A total for the whole contract, per service: ASR in audio minutes, MT and TTS in input characters. It doesn't reset monthly. A request that doesn't fit what's left returns 429 CONTRACT_ALLOCATION_EXHAUSTED and isn't charged; smaller requests may still fit. |
| Services | Only the services in your contract are available; others return 403 SERVICE_NOT_IN_CONTRACT. Pipelines check every step first, so nothing is run or charged if a step isn't included. |
| Monthly limit | Optional. When set, usage per 30-day period (from the start date) is capped too; over it returns 429 CONTRACT_MONTHLY_LIMIT with the reset date. |
| Throughput | Same per-minute rate limits and request sizes as Premium. No daily request caps: the allocation is the limit. |
| Failed requests | Requests that fail on our side (errors, timeouts, busy) are refunded automatically. |
Balance headers
Every successful call on a custom plan tells you what's left, so your system can track its balance without a separate request:
X-Quota-Remaining: mt-characters=1998000 X-Plan-Expires: 2026-12-31 # Pipelines charge two services and report both: X-Quota-Remaining: mt-characters=1997870, tts-characters=499870
Units are asr-minutes, mt-characters and tts-characters. X-Plan-Expires is the last day of the contract. Both headers are readable from browsers (CORS-exposed).
Need higher limits or a custom plan?
Contact support@ayadata.ai for Premium, the Custom tier, a top-up or a renewal.