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

# Rate limits

> Handle API quotas and retry throttled requests safely.

Zero applies layered limits to public API traffic. Anonymous reads default to **120 requests per 60 seconds per IP address**. Requests with an API key default to **600 requests per 60 seconds per key**, and all API replicas share a **10,000 request per 60 second global capacity limit**.

Cloud Armor also rejects abusive bursts before they reach the application. An edge rejection can return `429` without the JSON problem body shown below. Do not depend on every rejected request reaching the application.

Successful application responses include `X-RateLimit-Limit`, `X-RateLimit-Remaining`, and `X-RateLimit-Reset`. The reset value is a Unix timestamp in seconds.

When a request exceeds an application quota, the API returns `429 RATE_LIMITED` and a `Retry-After` header containing the number of seconds to wait.

```json theme={null}
{
  "type": "https://docs.zdlake.com/api/rate-limits",
  "title": "Too Many Requests",
  "status": 429,
  "detail": "Rate limit exceeded",
  "code": "RATE_LIMITED",
  "request_id": "req_01J7Y8Z9ABCDEF0123456789AB",
  "errors": {
    "retry_after": 30
  }
}
```

Wait for `Retry-After`, then retry with exponential backoff and jitter. Bound concurrency and stop retrying after a finite attempt or time limit.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.