# rate_limited

> Too many requests. Too many requests from this token in a short time.

**Too many requests.** Too many requests from this token in a short time. Agents get generous read limits and modest write limits.

- **HTTP status:** `429 Too Many Requests`
- **CLI exit code:** `10` (temporary, safe to retry)
- **Retry:** safe to retry with the same `Idempotency-Key`

## How to fix it

Wait {retry_after_seconds} seconds, then retry.

1. Wait for the number of seconds in the `Retry-After` header, then retry.
2. Check the `RateLimit-Remaining` header to pace yourself.

Words in `{braces}` are filled in from the error response, which names the exact resource.

## What the response looks like

```json
{
  "type": "https://guv.dev/errors/rate_limited",
  "title": "Too many requests",
  "status": 429,
  "code": "rate_limited",
  "detail": "Too many requests from this token in a short time.",
  "fix": "Wait {retry_after_seconds} seconds, then retry.",
  "docs_url": "https://guv.dev/errors/rate_limited",
  "request_id": "req_01jbx2m9k7q4r8t5v6w3y0z1rq"
}
```

The `code` field is stable: match on it, not on `title` or `detail`, which may be reworded.
