> ## 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

> Understand 0xArchive data families, venue namespaces, product surfaces, route support, freshness checks, and export boundaries.

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](https://www.0xarchive.io/data). The docs surface explains how that data maps to API routes, export schemas, response schemas, examples, and downstream boundaries.

## 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](/markets) and the live [Data explorer](https://www.0xarchive.io/data).                                                                          |
| Programmatic market-data calls  | Choose [REST API](/rest-api), [WebSocket](/websocket), [SDKs](/sdks), [CLI](/cli), [MCP Server](/mcp-server), or [Skill](/skill) based on the execution environment. |
| Route and schema review         | Use [OpenAPI](/openapi), [Schemas](/schemas), [Responses](/responses), and [Example Responses](/response-examples).                                                  |
| Historical files                | Use [Data Catalog](/data-catalog), [Export Schemas](/export-schemas), and [Export Checkout](/export-checkout).                                                       |
| Downstream publishing or resale | Review [Data Rights](/data-rights) before exposing raw records outside the organization.                                                                             |
| Reliability-sensitive output    | Attach [Data Quality](/data-quality), coverage, freshness, incident, and request-ID context to the job.                                                              |

## Data Workflow

<Steps>
  <Step title="Choose venue family">
    Use [Venue Coverage](/venue-coverage) before choosing a REST path or WebSocket channel.
  </Step>

  <Step title="Confirm data availability">
    Check instruments, pairs, outcomes, coverage, or freshness before running wide historical jobs.
  </Step>

  <Step title="Inspect schema and response shape">
    Use [Schemas](/schemas), [Responses](/responses), and [Export Schemas](/export-schemas) before parsing fields into typed code or warehouse tables.
  </Step>

  <Step title="Run a bounded example">
    Use [Examples](/examples) with one symbol and one small window before widening.
  </Step>

  <Step title="Check rights before redistribution">
    Use [Data Rights](/data-rights) before public exports, resale, customer-facing delivery, or partner feeds.
  </Step>
</Steps>

## Product Surface Versus API Surface

The live [Data explorer](https://www.0xarchive.io/data) is for visual browsing and market inspection. The REST API, WebSocket API, SDKs, CLI, MCP Server, Skill, and OpenAPI are for programmatic use. They should agree on venue family, freshness, and field meaning, but they serve different jobs.

If a user asks for a chart page, start with [Markets](/markets). If they ask for code, start with [REST API](/rest-api), [WebSocket](/websocket), [OpenAPI](/openapi), or [Examples](/examples). If they ask for raw file delivery, start with [Data Catalog](/data-catalog), [Export Schemas](/export-schemas), [Export Checkout](/export-checkout), and [Data Rights](/data-rights).

## Next Step

Open [Data Catalog](/data-catalog) for export product routes, [Schemas](/schemas) for JSON field and envelope rules, [Export Schemas](/export-schemas) for Parquet datasets, [Responses](/responses) for payload parsing, and [Examples](/examples) for copyable request patterns.