The 429 response
A model-specific ceiling says so in the message. Successful responses carry no rate-limit headers.
Retry with backoff after
Retry-After; see Error handling.
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Requests per minute per workspace, per-model ceilings, key limits, and what a 429 response carries.
| Limit | Default | Where it is set |
|---|---|---|
| Requests per minute | 300 per workspace | Raised per account by RedPill; enterprise accounts are exempt |
| Tokens per minute | None unless set | Per account or per model. Counts prompt and completion tokens; cached prompt tokens count less |
| Per-model ceilings | None unless set | Requests or tokens per minute for one model, applied to every account |
{
"error": {
"message": "Rate limit exceeded. Please retry after the reset time.",
"type": "rate_limit_error",
"code": "rate_limit_exceeded"
}
}
| Header | Meaning |
|---|---|
X-RateLimit-Limit | The limit that was hit. |
X-RateLimit-Remaining | 0 |
X-RateLimit-Reset | Unix time, in seconds, when the window resets. |
Retry-After | Seconds until then. |
Retry-After; see Error handling.
Was this page helpful?