## Limit

In production, each API key is limited to **100 requests per minute** across authenticated endpoints. If you exceed that limit within a rolling 60-second window, the API returns `429 Too Many Requests`.

## Rate limit error

When the rate limit is exceeded, the API returns a response like this:

```
{
  "error": {
    "status": 429,
    "code": "rate_limit_exceeded",
    "message": "You have exceeded your request limit. Please try again later."
  }
}
```

## Recommended handling

- Implement exponential backoff when you receive `429` responses.
- Cache responses where appropriate to reduce API calls.
- Avoid sending the same request repeatedly in tight loops.
- Spread load across time instead of sending large bursts when possible.

## Reduce avoidable requests

- Reuse search results when the query and context have not changed.
- Batch work where possible instead of requesting one item at a time.
- Avoid polling aggressively from the same integration.

## Next steps

- [Tools Search](/content/docs/api-reference/tools-search/index.html) for the main searchable endpoint
- [Errors](/content/docs/api-reference/errors/index.html) for related failure codes