Skip to main content

​
Limits

MetricValue
Requests per minute100
Window typeSliding window
ScopePer user (not per key)
The rate limit is shared across all endpoints and all keys belonging to the same user.

​
Response headers

Every authenticated response includes rate limit headers: 
X-RateLimit-Limit: 100
X-RateLimit-Remaining: 87
X-RateLimit-Reset: 1774450631
HeaderDescription
X-RateLimit-LimitMaximum requests per minute
X-RateLimit-RemainingRequests remaining in current window
X-RateLimit-ResetUnix timestamp when the window resets

​
Rate limit exceeded

When you exceed the limit, you’ll receive a 429 response: 
{
  "object": "error",
  "error": {
    "code": "rate_limited",
    "message": "Rate limit exceeded. Retry after 12s.",
    "doc_url": "https://0xinsider.com/docs/api#rate-limits"
  }
}
The Retry-After header tells you how many seconds to wait: 
Retry-After: 12

​
Best practices

  • Cache responses — most data updates every 30-120 seconds
  • Use cursor pagination instead of re-fetching full lists
  • Backoff on 429 — respect the Retry-After header
  • Batch your reads — fetch what you need in fewer, larger requests (higher limit)