Rate Limits & Budgets
Enterprise Router enforces rate limits and budget controls at both the key and organization level.
Per-key rate limits
Each proxy key can have a requests per minute (RPM) limit. When the limit is exceeded, the gateway returns 429 Too Many Requests with "error": "rate_limited".
Set this when creating or editing a key in the dashboard, or via the management API.
Organization rate limits
Organization-wide RPM limits are configured through budget configs. These apply across all keys in the org. When exceeded, the gateway returns 429 with "error": "organization_rate_limited".
Rate limit headers
When a key has a rate limit configured, the gateway includes these headers in every response:
For org-level limits, additional headers are included:
Budget controls
Budget configs let you set spending limits for your organization:
Hard budget
When the organization’s spend reaches the max budget for the current period, all requests are denied with 403 budget_exceeded.
Soft budget
When spend reaches the soft budget threshold, requests are still allowed but the gateway adds a warning header:
Use this to trigger alerts in your application before hitting the hard limit.
Budget periods
Budgets reset automatically based on the configured duration:
Per-key spend limits
Individual keys can also have spend limits:
- Spend limit ($) — maximum dollar amount this key can spend
- Reset period — daily, weekly, monthly, or never
When a key exceeds its spend limit, requests are denied with 403 spend_exceeded.
Credit balance
Your organization maintains a credit balance. Every request deducts from this balance based on token usage and model pricing. When credits run out, requests are denied with 403 insufficient_credits.
Purchase credits in Settings > Billing in your dashboard.