The data section maps public product surfaces to the route, chart, export, schema, and rights pages behind them. 0xArchive data is organized by venue family, data family, freshness state, delivery surface, and use rights. The live product surface for visual browsing and file exports is 0xArchive Data. The docs surface explains how that data maps to API routes, export schemas, response schemas, examples, and downstream boundaries.Documentation Index
Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
Use this file to discover all available pages before exploring further.
Data Families
| Data family | Common routes | Use it for |
|---|---|---|
| Instruments and pairs | /instruments, /spot/pairs, HIP-4 outcomes | Market discovery and symbol validation |
| Order books | /orderbook/{symbol}, history, L3, L4 | Snapshots, depth, reconstruction, liquidity views |
| Trades | /trades/{symbol} and recent trade routes | Fill history, tape review, backtests, chart inputs |
| Candles | /candles/{symbol} | OHLC-style historical analysis |
| Funding and OI | /funding/{symbol}, /openinterest/{symbol} | Perp funding, exposure, and derivatives research |
| Liquidations and orders | Liquidation, order history, flow, TPSL routes | Risk, flow, and order-level analysis where available |
| TWAP and Spot-specific data | /v1/hyperliquid/spot/twap/{symbol} | Hyperliquid Spot execution-history analysis |
| Data quality | /v1/data-quality/* | Coverage, freshness, incidents, latency, and SLA checks |
| File exports | Data Catalog schemas | Parquet/ZSTD historical datasets, warehouse loads, and offline research |
Venue Scope
0xArchive exposes two top-level venue APIs: Hyperliquid and Lighter.xyz. Hyperliquid core, Hyperliquid Spot, HIP-3, and HIP-4 are separate Hyperliquid-scoped market families. Lighter routes live under/v1/lighter/*.
Do not flatten those families in a data model. Store venue family, symbol, route, time window, and request ID with the records. A BTC perp record, a HYPE-USDC Spot pair, a km:US500 HIP-3 symbol, a HIP-4 outcome side, and a Lighter symbol should stay distinguishable in storage, examples, and generated code.
Data Routing Packet
Use this packet when the request starts from broad data intent instead of a concrete endpoint.| Decision | Public path |
|---|---|
| Visual market inspection | Start with Markets and the live Data explorer. |
| Programmatic market-data calls | Choose REST API, WebSocket, SDKs, CLI, MCP Server, or Skill based on the execution environment. |
| Route and schema review | Use OpenAPI, Schemas, Responses, and Example Responses. |
| Historical files | Use Data Catalog, Export Schemas, and Export Checkout. |
| Downstream publishing or resale | Review Data Rights before exposing raw records outside the organization. |
| Reliability-sensitive output | Attach Data Quality, coverage, freshness, incident, and request-ID context to the job. |
Data Workflow
Choose venue family
Use Venue Coverage before choosing a REST path or WebSocket channel.
Confirm data availability
Check instruments, pairs, outcomes, coverage, or freshness before running wide historical jobs.
Inspect schema and response shape
Use Schemas, Responses, and Export Schemas before parsing fields into typed code or warehouse tables.
Run a bounded example
Use Examples with one symbol and one small window before widening.
Check rights before redistribution
Use Data Rights before public exports, resale, customer-facing delivery, or partner feeds.