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

# Rate limits

> Request limits by plan and how to handle 429 responses.

## REST API limits by plan

| Plan       | Requests / minute |
| ---------- | ----------------- |
| Growth     | 30                |
| Agency     | 60                |
| Enterprise | 120               |
| Scale      | 120               |
| Unlimited  | 300               |

Limits apply per API key. If you generate multiple keys, each active key receives its own minute bucket, while the plan still caps how many keys you can create.

Provider-backed endpoints, such as Google Business Profile health checks, also have daily safeguards because they can call paid data providers. If one of those daily safeguards trips, the response includes `429`, the plan limit, and `resetAt`.

## Headers

Every API response includes rate limit headers:

| Header                  | Description                                   |
| ----------------------- | --------------------------------------------- |
| `X-RateLimit-Limit`     | Maximum requests per minute for your plan     |
| `X-RateLimit-Remaining` | Requests remaining in the current window      |
| `Retry-After`           | Seconds to wait before retrying after a `429` |

## Best practices

* **Cache responses** — snapshots and competitor data don't change by the minute. Cache for at least 5 minutes.
* **Use bulk endpoints** — `/export` is one request vs. N individual calls
* **Implement backoff** — on `429`, wait for `Retry-After` seconds before retrying
* **Use webhooks** — for real-time events, webhooks are more efficient than polling `/me/alerts`