Rate limits
Limits are assigned by the gateway plan attached to your API key. Inspect the response headers instead of assuming a fixed site-wide quota.
Authoritative values
Successful RPC responses expose the active gateway limit and remaining allowance. These values are authoritative for the key making the request.
| Header | Meaning |
|---|---|
| X-RateLimit-Limit | Request allowance for the current gateway window |
| X-RateLimit-Remaining | Requests remaining in that window |
| X-RateLimit-Reset | Gateway-provided reset value for the current window |
| Retry-After | How long to wait when returned with HTTP 429 |
Handling HTTP 429
- Respect
Retry-Afterwhen the response includes it. - Use exponential backoff with jitter for repeated retries.
- Avoid retrying non-idempotent requests such as sendTransaction without application-level safeguards.
- Monitor remaining allowance and distribute sustained workloads instead of waiting for hard failures.