One extra requests-per-minute quota per access key.
Every access key can already carry a monthly budget and a requests-per-minute limit. This module adds one more requests-per-minute quota for a chosen key.
What you have without it
Open Gateway as an Owner and create an
access key with a monthly budget and a requests-per-minute cap. When a
limit is reached the Gateway returns 429.
What the module adds
Enable Advanced Rate Limits on Gateway modules, then add a quota on the Gateway page. You choose one access key and a whole number from 1 to 100000 requests per minute. The quota applies to every model on that key. It does not add per-second, per-hour, per-model, or burst limits. Disabling the module removes the quotas that belong to this workspace. The monthly fee is $12.
How it enforces
Rate limits are enforced server-side using a sliding window per access
key. When the limit is reached, the Gateway responds immediately with
HTTP 429 Too Many Requests and a
Retry-After header suggesting when to resume. No request
is forwarded to the provider beyond the quota.
curl https://YOUR-SITE/v1/chat/completions \
-H "Authorization: Bearer kb_live_..." \
-H "content-type: application/json" \
-d '{"model":"gpt-4o","messages":[{"role":"user","content":"Hello"}]}'
# > HTTP 429
# { "error": { "type": "rate_limit_exceeded", "message": "Rate limit reached. Retry after 60s." } }
Status in the dashboard
Gateway → Gateway modules reports whether Advanced Rate Limits is loaded. Each access key on the Gateway page shows its current quota and remaining request count in the current window.
Limits
| Setting | Description |
|---|---|
| Requests per minute | 1 to 100,000 per access key |
| Rules per workspace | One per access key |
| Granularity | Per-minute sliding window; no per-second or burst |
| Per-model limits | Not supported — quota applies to all models on the key |
| Monthly fee | $12 per workspace |