Elevenlabs Rate Limits
ElevenLabs throttles on CONCURRENCY, not on a requests-per-minute quota. The docs say so explicitly: "API requests per minute and concurrent requests are different metrics" and no per-minute ceiling is published. The limit that binds is how many requests a plan may have in flight at once, and it differs by model family (Multilingual v2 vs Flash), by Speech to Text (elevated), by realtime STT and by Music. Beyond the ceiling requests are queued rather than rejected — the docs put the added latency at roughly 50ms — and a 429 is returned when the queue itself is exceeded.
Elevenlabs Rate Limits is the machine-readable rate-limit profile for ElevenLabs on the APIs.io network, in the API Commons Rate Limits shape.
It captures 35 rate-limit definitions, measuring concurrent.
Limit state is signalled in the request, response, retryAfter, and retryAfter_note response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled and concurrencyExceeded.
Tagged areas include Rate Limiting, Concurrency, and Speech.
requestresponseretryAfterretryAfter_note
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.