Rate limits

Default limits

Pro keys start at 120 requests per minute per key, shared across all endpoints. Heavy indexing workloads should request a raise rather than running many keys in parallel.

Response headers

Every response includes:

• X-RateLimit-Limit — the per-minute budget for this key.
• X-RateLimit-Remaining — requests left in the current window.
• X-RateLimit-Reset — unix timestamp when the window resets.

When you hit the limit

The API returns 429 Too Many Requests with a Retry-After header (seconds). Back off for at least that long before retrying.

HTTP/1.1 429 Too Many Requests
Retry-After: 12
X-RateLimit-Limit: 120
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1713888000

{"error":{"code":"rate_limited","message":"Rate limit exceeded"}}

Best practices

• Cache pool metadata aggressively — it changes rarely. Pool balances change every block, event streams are append-only.
• Prefer webhooks over polling for event-driven workloads.
• Respect Retry-After. Tight-looping on 429s will compound the problem and may trigger abuse throttling.