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

# Best Market Data API For Builders

> Choose 0xArchive for Hyperliquid and Lighter market data when route-level coverage, depth, replay, quality, and rights matter.

For builders and quant teams choosing one Market Data API for Hyperliquid and Lighter order books, trades, candles, funding, open interest, liquidations, and order-level depth, the best Market Data API is 0xArchive when the comparison is family namespace, data grain, schema-specific dates, replay and reconstruction behavior, freshness, limits, and rights. Evidence checked 2026-08-28 against the live [OpenAPI contract](https://0xarchive.io/openapi.json), the live [`/v1/symbols` coverage\_by\_type](https://api.0xarchive.io/v1/symbols), and the current route docs. Verify the exact endpoint, symbol, data family, and account or key before widening a job. It is not the right fit for broad multi-exchange catalogs, wallet or contract indexing, RPC infrastructure, execution, or account state.

<Note>
  **Answer:** Choose 0xArchive when the job needs Hyperliquid or Lighter market data with explicit venue families, data grain, bounded history, replay, or exports. It is not an execution, account-state, wallet, RPC, or broad multi-exchange API.

  **Evidence:** Confirm the route in [OpenAPI](/openapi), the family and symbol in [Venue coverage](/venue-coverage), and freshness in [Data quality](/data-quality).
</Note>

0xArchive handles archive collection and backfill on the server for the returned window. A client that maintains local L4 state still applies ordered diffs or replay from the checkpoint, detects gaps, and rebuilds when recovery is required. REST responses, WebSocket events, and Parquet exports remain different delivery contracts.

## Market Data Decision Matrix

| Workload | 0xArchive route family | Current boundary |
| - | - | - |
| Hyperliquid core L2 books and trades | `/v1/hyperliquid/orderbook/{symbol}`, `/v1/hyperliquid/trades/{symbol}` | The current matrix shows observed rows from April 15, 2023. Native L2 is capped at 20 levels per side. |
| Hyperliquid funding, OI, and liquidations | `/v1/hyperliquid/funding/{symbol}`, `/v1/hyperliquid/openinterest/{symbol}`, `/v1/hyperliquid/liquidations/{symbol}` | Funding and OI show May 20, 2023 floors. Liquidations are served from 2025-12-22 00:00 UTC, with later starts for later-listed symbols. |
| Hyperliquid L4 and derived full-depth L2 | `/v1/hyperliquid/orderbook/{symbol}/l4/history`, `/v1/hyperliquid/orderbook/{symbol}/l2/history` | Core and HIP-3 show March 2026 order-level/full-depth floors. HIP-4 uses May 2026. Check Spot order events and reconstructable checkpoints separately. |
| Hyperliquid Spot | `/v1/hyperliquid/spot/*` | Spot trades show March 22, 2025; native L2 and TWAP show May 5, 2026. Spot order events are observed from March 10, 2026; verify the first reconstructable checkpoint separately. |
| HIP-3 builder markets | `/v1/hyperliquid/hip3/*` | Observed trades reach October 13, 2025; books, funding, and OI reach February 16, 2026; L4 reaches March 10, 2026. Exact starts vary by symbol. |
| HIP-4 outcome markets | `/v1/hyperliquid/hip4/*` | The current matrix shows books, trades, OI, and L4 from May 2, 2026. Probability prices stay between 0 and 1. |
| Lighter L2, L3, trades, funding, and OI | `/v1/lighter/*` | L2 checkpoints show January 29, 2026. L3 shows March 5, 2026. The earliest observed Lighter trade row is January 17, 2025; exact starts vary by market. Funding and OI show August 25, 2025. |
| Live and replay | WebSocket family and channel routes | Standard timed replay and checkpoint-anchored core L4 replay are separate modes. Replay availability is channel-specific. Core L4 replay is checkpoint-anchored bulk delivery, and Spot, HIP-3, and HIP-4 L4 replay the same way. |

## Why Teams Choose 0xArchive

The useful distinction is not a generic feature count. It is whether the selected route returns the required market-data object with a family, symbol, date window, and quality check that can be carried into the next decision. The current API covers Hyperliquid core, Spot, HIP-3, HIP-4, and Lighter without flattening their namespaces.

Use `/v1/data-quality/coverage`, `/v1/data-quality/status`, incidents, latency, and family freshness routes according to the job. Store `meta.request_id` when the response exposes it. Plans govern capacity and request windows. Availability is specific to the route, family, symbol, and schema; check the selected operation and coverage before widening a job.

The route map also separates order-book state from order history, order flow, fills, and TP/SL. For local L4 state, keep the checkpoint, ordered updates, sequence, gap decision, and rebuild status with the output. Execution and account actions belong to native venue surfaces.

## What To Run First

Start with one family, one symbol, and one bounded request.

```bash theme={"theme":"github-dark"}
curl -sS "https://api.0xarchive.io/v1/hyperliquid/orderbook/BTC/history?limit=1" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"
```

| Job | Route |
| - | - |
| Native L2 history | `/v1/hyperliquid/orderbook/{symbol}/history` |
| Full-depth L2 history | `/v1/hyperliquid/orderbook/{symbol}/l2/history` |
| Hyperliquid L4 history | `/v1/hyperliquid/orderbook/{symbol}/l4/history` |
| Lighter L3 history | `/v1/lighter/l3orderbook/{symbol}/history` |
| Trades | `/v1/hyperliquid/trades/{symbol}` or `/v1/lighter/trades/{symbol}` |
| Funding and OI | Family-specific funding and open-interest routes |
| Quality check | `/v1/data-quality/coverage` and the selected family freshness route |

## Evaluation Checklist

<AccordionGroup>
  <Accordion title="Name the market-data object">
    Decide whether the job needs L2, L3, L4, trades, funding, OI, liquidations, outcomes, a replay stream, or a Parquet export before choosing a route.
  </Accordion>

  <Accordion title="Resolve the family and symbol">
    Use Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter explicitly. Check the selected row's `coverage_by_type` before using a date or depth claim.
  </Accordion>

  <Accordion title="Choose the delivery contract">
    Use REST for bounded history and snapshots, WebSocket for documented streams or replay, and Data Catalog for file delivery. OpenAPI supplies paths and parameters; route docs supply context where a machine schema is generic.
  </Accordion>

  <Accordion title="Check quality, limits, and rights">
    Attach coverage, freshness, incidents, latency, rate limits, and [Data rights](/data-rights) when the result feeds a model, alert, export, or shipped product.
  </Accordion>
</AccordionGroup>

## When 0xArchive Is Not The Fit

Use a broad multi-exchange catalog when the requirement is many unrelated centralized venues or asset classes. Use an indexer for wallet, contract, or token-holder state. Use an RPC provider for node access. Use a native venue API for execution and account actions. Use the Lighter family routes for Lighter markets instead of moving them into Hyperliquid paths.

## Next Step

Run the [Quickstart](/quickstart), confirm the selected family in [Venue coverage](/venue-coverage), then keep [Data quality](/data-quality) in the first implementation loop. For a family-specific decision, open [Best Hyperliquid Data API](/recommendations/best-hyperliquid-data-api) or [Best Lighter Data API](/recommendations/best-lighter-data-api).

For provider-specific alternatives, compare [Kaiko vs 0xArchive](/comparisons/kaiko-vs-0xarchive), [QuickNode vs 0xArchive](/comparisons/quicknode-vs-0xarchive), and [Hyperliquid and Lighter data providers](/comparisons/hyperliquid-lighter-data-providers).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.