Rate Limits

The API enforces rate limits to ensure fair usage and platform stability.

Current Limits

Each API key is limited to 100 requests per 60-second sliding window. The limit is keyed on the authenticated API key (not the caller IP), so requests from multiple machines that share a key count against the same budget.

Limits are enforced per Cloudflare isolate, so very bursty traffic that lands on different isolates may briefly exceed the nominal cap before backing off.

Rate Limit Headers

When a request is throttled, the 429 response includes these headers so you can back off cleanly.

Header	Description
`X-RateLimit-Limit`	Maximum requests allowed per window (100)
`X-RateLimit-Remaining`	Number of requests remaining in the current window
`X-RateLimit-Reset`	Unix timestamp when the rate limit window resets

429 Too Many Requests

When you exceed the rate limit, the API returns a 429 status code. Wait until the reset time before retrying.

429 Response

{
  "error": {
    "code": "rate_limited",
    "message": "Too many requests. Please wait before retrying.",
    "retry_after": 32
  }
}

Note: These limits are actively enforced. If you need a higher ceiling for a production integration, contact support.