How to Handle 429 Rate Limits in LLM API Applications
OpenRouter Blog published a guide to diagnosing and handling 429 Too Many Requests errors returned by OpenAI, Anthropic, and OpenRouter. It recommends reading rate-limit headers, retrying at the server-specified reset time, using model fallbacks, or routing requests to another provider; its Python and TypeScript examples were tested against the OpenRouter API.
In OpenRouter’s test, default OpenAI Python SDK retries still left 23 of 60 requests failing, while retries that honored reset headers, model fallback, and provider failover each completed the tested workloads without reported failures.
LLM API Rate Limits: How to Fix OpenAI and Claude 429 Errors
OpenRouter ·11/11/2026


A 429 Too Many Requests error means you sent more requests or tokens than your limit allows in the current time window. OpenAI, Anthropic and OpenRouter all return it, and it usually shows up the first time an app runs under real load or a batch job fans out across several workers.
Most people reach for a retry, and with default settings that often isn’t enough. When we ran a 60-prompt batch through the OpenAI Python SDK against a per-minute limit, 23 requests still failed after the SDK’s retries. The window reset 4 to 8 seconds after the SDK gave up on each one.