0xArchive · Rate Limits

0Xarchive Rate Limits

0Xarchive Rate Limits is the machine-readable rate-limit profile for 0xArchive on the APIs.io network, in the API Commons Rate Limits shape.

It captures 6 rate-limit definitions.

Limit state is signalled in the {‘header’: ‘X-RateLimit-Limit’, ‘type’: ‘integer’, ‘meaning’: ‘Requests per second limit’, ‘source’: ‘openapi/0xarchive-openapi.json components.responses.RateLimited.headers’, ‘observed_anonymously’: False}, {‘header’: ‘X-RateLimit-Remaining’, ‘type’: ‘integer’, ‘meaning’: ‘Remaining requests this second’, ‘source’: ‘openapi/0xarchive-openapi.json components.responses.RateLimited.headers’, ‘observed_anonymously’: False}, {‘header’: ‘X-RateLimit-Reset’, ‘type’: ‘integer’, ‘meaning’: ‘Unix timestamp when the limit resets’, ‘source’: ‘openapi/0xarchive-openapi.json components.responses.RateLimited.headers’, ‘observed_anonymously’: False}, and {‘header’: ‘Retry-After’, ‘meaning’: ‘Documented as the authoritative retry signal on 429 - “Honor Retry-After when the response includes it” - but the docs are explicit that it is not always present, and it does not appear in the OpenAPI 429 response headers block.’, ‘source’: ‘https://docs.0xarchive.io/errors’, ‘observed_anonymously’: False, ‘conditional’: True} response headers.

Tagged areas include Market Data, Historical Data, Crypto, DeFi, and Perpetuals.

6 Limits {'header': 'X-RateLimit-Limit', 'type': 'integer', 'meaning': 'Requests per second limit', 'source': 'openapi/0xarchive-openapi.json components.responses.RateLimited.headers', 'observed_anonymously': False}{'header': 'X-RateLimit-Remaining', 'type': 'integer', 'meaning': 'Remaining requests this second', 'source': 'openapi/0xarchive-openapi.json components.responses.RateLimited.headers', 'observed_anonymously': False}{'header': 'X-RateLimit-Reset', 'type': 'integer', 'meaning': 'Unix timestamp when the limit resets', 'source': 'openapi/0xarchive-openapi.json components.responses.RateLimited.headers', 'observed_anonymously': False}{'header': 'Retry-After', 'meaning': 'Documented as the authoritative retry signal on 429 - "Honor Retry-After when the response includes it" - but the docs are explicit that it is not always present, and it does not appear in the OpenAPI 429 response headers block.', 'source': 'https://docs.0xarchive.io/errors', 'observed_anonymously': False, 'conditional': True}
Transcribed from the provider's documentation on 2026-09-01 — docs.0xarchive.io/rate-limits.
View Source
Market DataHistorical DataCryptoDeFiPerpetualsDerivativesOrder BookHyperliquidLighterHIP-3HIP-4Prediction MarketsWebSocketStreaminghistorical-replayParquetBulk DataMCPAgent-Nativex402OpenAPIRESTA2A

Limits

per-account
· per 1 second
{"Build" => 50, "Enterprise" => "from 1,000", "Free" => 15, "Pro" => 150, "Scale" => 500}/1 second
Burst rate across REST calls. The docs prescribe backoff and queuing rather than a stated burst allowance.
per-account
· per instantaneous
{"Build" => 10, "Enterprise" => "from 500", "Free" => 3, "Pro" => 20, "Scale" => 20}/instantaneous
Applies to long-running or heavy history calls; the docs advise bounding worker pools.
per-account
· per calendar month
{"Build" => 80000000, "Enterprise" => "unlimited", "Free" => 50000, "Pro" => 400000000, "Scale" => 2000000000}/calendar month
Credits are consumed by data volume and route cost, not by request count. L3/L4, replay and deep-history routes cost materially more than shallow market-state routes.
per-account
· per concurrent
{"Build" => 500, "Enterprise" => "unlimited", "Free" => 10, "Pro" => 3000, "Scale" => 20000}/concurrent
per-account
· per per replay stream
{"Build" => "50x", "Enterprise" => "from 500x", "Free" => "10x", "Pro" => "100x", "Scale" => "300x"}/per replay stream
Hyperliquid core l4_diffs and l4_orders replay ignores the speed parameter entirely - it uses a checkpoint-anchored bulk stream.
per-account
· per per request or per replay
{"Build" => "full retained archive", "Enterprise" => "full retained archive", "Free" => "most recent rolling 30 days, maximum 30-day span per request or replay", "Pro" => "full retained archive", "Scale" => "full retained archive"}/per request or per replay
The only route-shaped restriction in the plan model. Every tier including Free reaches every route family, schema and served depth; only the reachable time range differs.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit
curl "https://apis.io/api/v1/rate-limits/0xarchive-rate-limits"
All rate limits
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.