> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hypastack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Rate Limits

> Per-key request budgets by plan.

Each key gets its own budget per minute, so one runaway script can't starve your other keys.

| Plan      | Keys | Requests      |
| --------- | ---- | ------------- |
| Free      | None | —             |
| Essential | 1    | 120 / minute  |
| Pro       | 3    | 600 / minute  |
| Max       | 5    | 1800 / minute |

Every response tells you where you stand, so you never have to guess:

```text theme={null}
X-RateLimit-Limit: 600
X-RateLimit-Remaining: 594
X-RateLimit-Reset: 1784500860
```

Go over and you get `429 rate_limit_exceeded` with a `Retry-After` header in seconds. Wait that long and carry on.

Separately, there's a ceiling across all API traffic that protects the service as a whole. If Hypastack is shedding load you'll see `503 server_busy`, also with `Retry-After`. It's rare, it's not your fault, and retrying works. Those two, `rate_limit_exceeded` and `server_busy`, are the only failures worth retrying automatically. See [Errors](/api-reference/errors) for the rest.