Rate Limiting - OpenModex

Rate Limits

Rate limits are enforced per API key based on your subscription tier:

Tier	Requests/min	Tokens/min
Free	30	60,000
Pro	120	500,000
Enterprise	300+	Custom

Rate Limit Headers

Every response includes rate limit headers:

X-RateLimit-Limit: 120
X-RateLimit-Remaining: 115
X-RateLimit-Reset: 1700000060

Header	Description
`X-RateLimit-Limit`	Maximum requests per window
`X-RateLimit-Remaining`	Requests remaining in window
`X-RateLimit-Reset`	Unix timestamp when the window resets

Handling 429 Errors

When rate limited, you’ll receive a 429 Too Many Requests response:

{
  "error": {
    "message": "Rate limit exceeded. Please retry after 2 seconds.",
    "type": "rate_limit_error",
    "code": "rate_limit_exceeded"
  }
}

Automatic Retries

All official SDKs automatically retry on 429 errors with exponential backoff:

const client = new OpenModex({
  apiKey: 'omx_sk_...',
  maxRetries: 3, // default: 2
});

The retry delay follows: min(500ms × 2^attempt, 5000ms)

Best Practices

Use exponential backoff — the SDKs handle this automatically
Monitor remaining quota — check X-RateLimit-Remaining headers
Use streaming — streaming requests count as one request regardless of response length
Upgrade your tier — if you consistently hit limits, consider upgrading
Distribute load — use multiple API keys for different services