Developer docs
Every order and tick of Hyperliquid and Lighter. One API.
Historical and live market data as clean JSON: L4 order books, trades, candles, funding, and liquidations, with coverage you can verify per symbol. Teams used to get this by paying for an expensive vendor feed or running their own collectors. One call replaces both.
CoverageBoth venues and every Hyperliquid family (core, Spot, HIP-3, HIP-4) plus Lighter. Depth varies by data type, so check it per symbol.
CompletenessHigh where covered, and you can verify it: per-symbol start dates, record counts, and detected gaps.
EaseOne key, one call, clean JSON with named fields. No raw structs and no integer-scaled prices to decode.
PriceEvery signup starts on the Free tier, no card. Upgrade to Build from
$49/mo when you need more; per-schema Parquet exports from $1/GB. See plans and limits.One dataset, three ways to get it
Order books, trades, funding, open interest, candles, liquidationsNormalized, named-field JSON across every venue. Venue is a switch on the page, not a separate API.RESTPull historyBounded queries, cursors, and point-in-time snapshots.
WebSocketStream liveSubscribe to live channels or replay history in order.
ExportBulk filesParquet datasets through the Data Catalog.
Make your first call
Create a key, then run one authenticated request. You get the full response in seconds, no client library required.Surfaces
| Surface | Use it for | Start here |
|---|---|---|
| REST API | Historical snapshots, trades, candles, funding, open interest, liquidations, instruments, data quality, wallet auth | REST API |
| WebSocket | Live subscriptions, historical replay, gap events, connection continuity | WebSocket API |
| SDKs | Typed clients, integration code, order-book reconstruction | SDKs |
| CLI | Shell scripts, cron, CI, incident checks, notebook jobs, JSON output | CLI |
| MCP Server | Typed tool calls inside MCP-capable clients | MCP Server |
| Skill | Reusable SKILL.md workflows for compatible hosts and OpenClaw | Skill |
| OpenAPI | Route and schema contract for generated clients and coding agents | OpenAPI |
| Schemas and responses | Shared envelope, field, pagination, error, decimal, and example-payload rules | Schemas, Responses, Example Responses |
| Examples | Bounded REST, WebSocket, parser, and agent examples | Examples |
| Trust and rights | Coverage, freshness, gaps, limits, credits, and raw-data redistribution boundaries | Data Quality, Venue Coverage, Rate Limits, Data Rights |
Venue families
0xArchive exposes two top-level venue APIs: Hyperliquid and Lighter.xyz. Hyperliquid core perps, Hyperliquid Spot, HIP-3 builder perps, and HIP-4 outcome markets are separate Hyperliquid-scoped market families under/v1/hyperliquid/*, /v1/hyperliquid/spot/*, /v1/hyperliquid/hip3/*, and /v1/hyperliquid/hip4/*; HIP-3 and HIP-4 are not additional top-level venues. Lighter markets use the separate /v1/lighter/* family.
Hyperliquid core
Plain perp symbols such as
BTC and ETH use /v1/hyperliquid/*.Hyperliquid Spot
Spot pair symbols such as
HYPE-USDC use /v1/hyperliquid/spot/*.HIP-3 builder perps
Namespaced builder symbols such as
km:US500 use /v1/hyperliquid/hip3/*.HIP-4 outcome markets
Outcome sides use
/v1/hyperliquid/hip4/*, with probability-priced fields where documented.Lighter.xyz
Lighter markets use the separate
/v1/lighter/* venue family.Check coverage before you trust a number
Coverage is not uniform across data types. Order books and trades reach back to 2023 on Hyperliquid; liquidations, L4 reconstruction, and Lighter L3 start later. Before a backtest, check the exact window and any gaps for the symbols you need on Venue Coverage and Data Quality.Pick your path
Crypto historical data
Route historical market-data work to the right REST and WebSocket surfaces.
Hyperliquid history
Use long-window Hyperliquid history for research, backtests, and migration checks.
HIP-3 data
Work with builder-perp symbols under the Hyperliquid HIP-3 namespace.
HIP-4 outcome markets
Query outcome sides, probability-priced books, trades, and open interest.
Hyperliquid Spot
Query Spot pairs, order books, trades, candles, L4 reconstruction, TWAP, and freshness.
Lighter quickstart
Start with Lighter-specific symbols, L2/L3 depth, and route differences.
Native vs managed
Decide when the native venue API is enough and when a normalized archive earns its place.
Compare options
Evaluate 0xArchive against native APIs, vendors, node providers, indexers, and backtesting needs.
For agents and code generators
Agents read the same sources you do: the OpenAPI contract, the Markdown pages, and the venue taxonomy. Point a coding agent at OpenAPI for exact paths and schemas, and at these docs for route selection, auth, response envelopes, and freshness checks before it writes a line.OpenAPI
Exact REST paths, parameters, auth, response schemas, and examples.
Responses
Parse success, error, pagination, request IDs, and decimal-sensitive fields.
Example responses
Check schema-backed payload examples before writing parsers or tests.
llms.txt
A high-level map for AI clients and retrieval systems.
Choose an interface
Decide between CLI, MCP Server, Skill, SDKs, OpenAPI, REST, WebSocket, and Markdown.
What to carry into your code
Carry five things from the first call into the client or runbook: the route family, the auth header (X-API-Key), the response envelope, a data-quality check, and your plan’s limits. That is what turns one correct request into a workflow you can run every day.