Rate limited

What it means

This credential used up its request budget for the current window.

Common causes

• Too many requests from one principal in a short time.
• Searches, which cost more than one unit each.
• Many failed credential checks from one network.

What to do

Wait for the seconds in Retry-After, then retry. Spread requests out and cache reads you repeat. See Rate limits.

Retry: safe after a pause. Back off between attempts, and reuse the same Idempotency-Key for a write.

This response also carries Retry-After, the number of seconds to wait before you try again.

Over MCP, the same failure is a tool result with isError: true, the code rate_limited and retryable: true.

Example

A response body for this problem. The detail and instance vary with the request.

{
  "type": "https://api.tobie.team/problems/rate_limited",
  "title": "Rate limited",
  "status": 429,
  "detail": "Rate limit exceeded for the read policy",
  "code": "rate_limited",
  "instance": "/v1/tasks",
  "requestId": "01JC0S7Z5F3X9QK2M4N6P8R0TV"
}