elevenlabs-rate-limits

# ElevenLabs Rate Limits ## Overview Handle ElevenLabs rate limits with plan-aware concurrency queuing, exponential backoff, and quota monitoring. ElevenLabs uses two rate limit mechanisms: concurrent request limits (per plan) and system-level throttling. ## Prerequisites - ElevenLabs SDK installed - Understanding of your subscription plan's limits - `p-queue` package (recommended): `npm install p-queue` ## Instructions ### Step 1: Understand the Two 429 Error Types ElevenLabs returns HTTP 429 for two different reasons: | 429 Variant | Response Body | Cause | Strategy | |-------------|--------------|-------|----------| | `too_many_concurrent_requests` | `{"detail":{"status":"too_many_concurrent_requests"}}` | Exceeded plan concurrency | Queue requests, don't backoff | | `system_busy` | `{"detail":{"status":"system_busy"}}` | Server overload | Exponential backoff | ### Step 2: Plan Concurrency Limits | Plan | Max Concurrent Requests | Characters/Month | |------|------------------------|-------------------| | Free | 2 | 10,000 | | Starter | 3 | 30,000 | | Creator | 5 | 100,000 | | Pro | 10 | 500,000 | | Scale | 15 | 2,000,000 | | Business | 15 | Custom | ### Step 3: Concurrency-Aware Request Queue ```typescript // src/elevenlabs/rate-limiter.ts import PQueue from "p-queue"; type ElevenLabsPlan = "free" | "starter" | "creator" | "pro" | "scale" | "business"; const CONCURRENCY_LIMITS: Record<ElevenLabsPlan, number> = { free: 2, starter: 3, creator: 5, pro: 1...