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

# Rate limits

> The Neo API rate limit, the headers that report it, and how to handle 429 responses.

The API is rate limited per tenant to keep it responsive for everyone. The limit is shared across all of a tenant's API keys and dashboard sessions — it's not per key.

|            |                          |
| ---------- | ------------------------ |
| **Limit**  | 1,200 requests           |
| **Window** | per 60 seconds (sliding) |
| **Scope**  | per tenant               |

## Rate-limit headers

Every response carries your current budget, so you can pace requests without guessing:

| Header                  | Description                                  |
| ----------------------- | -------------------------------------------- |
| `X-RateLimit-Limit`     | Maximum requests allowed in the window.      |
| `X-RateLimit-Remaining` | Requests left in the current window.         |
| `X-RateLimit-Reset`     | When the window resets (Unix epoch seconds). |

## Handling 429

When you exceed the limit, the API responds `429 Too Many Requests` with a `Retry-After` header (seconds to wait). Pause for that long, then retry. Build this into your client rather than hammering the endpoint:

```
HTTP/1.1 429 Too Many Requests
Retry-After: 12
```

<Tip>
  Watch `X-RateLimit-Remaining` and slow down before you hit zero, and prefer fewer large pages over many small ones — request up to `page_size=200` and follow the [pagination cursor](/developers/quickstart#paginate-through-a-list) instead of polling tight loops.
</Tip>

## What's next

<Card title="Explore the endpoints" icon="code" href="/developers/quickstart#explore-the-endpoints">
  Browse the full API reference with live schemas and a request console.
</Card>