Skip to main content
Inferoute enforces rate limits on every API key to ensure fair usage across all customers and to protect system stability. Limits are measured in requests per minute (RPM) and tokens per minute (TPM). When you exceed a limit, the API returns a 429 Too Many Requests response until the window resets.

Default limit tiers

Contact support@inferoute.ai to request a limit increase for your plan.

Rate limit headers

Every API response includes headers that tell you your current limit status:

Handling 429 errors

When you exceed your rate limit, the API responds with:
The Retry-After header tells you the number of seconds to wait before retrying. The safest strategy is exponential backoff with jitter — wait progressively longer between retries, with a small random component to avoid synchronized retry storms.
Inferoute rate limits are separate from any limits enforced by the underlying providers. Even if you are within your Inferoute limits, a provider may throttle the request on their end. Inferoute will surface those errors with the same 429 status code and attempt automatic retries according to your routing configuration.