Skip to main content
Use this page to confirm which data types are available for a market and how far back each dataset can go. 0xArchive covers two venues: Hyperliquid and Lighter. Hyperliquid includes core perpetuals, Spot, HIP-3 builder perpetuals, and HIP-4 outcomes. Lighter uses its own API namespace. Lighter has two deployments: mainnet and Robinhood Chain. Lighter mainnet is served under /v1/lighter/* and Lighter on Robinhood Chain under /v1/rh-lighter/*. See Venues and market types for the source hierarchy and symbol rules. For an overview of each venue, open Hyperliquid data or Lighter data. For one request or export, confirm the exact market, data type, and history window below.

​
Available data by market type

This matrix reflects the current OpenAPI contract. Available means that an endpoint exists for the market type. It does not guarantee coverage for every market, a universal history start, freshness, matching WebSocket or export support, or account capacity. Check /v1/symbols and the data-quality routes for the selected market.
  • Lighter funding records are returnable. Retrieve current funding separately for each venue and retain each source’s units and timestamp.
Lighter on Robinhood Chain candles cover the deployment from 2026-06-26 once they are enabled; until then the route returns a message instead of candles. Funding, open interest, and liquidations on Robinhood Chain exist for perpetual markets only. Hyperliquid L4 resting-order depth is a separate data type from native L2. Its checkpoint, ordered diff, and history routes are separate from order-history and order-flow lifecycle routes. Lighter exposes tick-level L3 individual-order depth from March 5, 2026, capped at 250 orders per side per tick. Lighter has no L4 route in this contract, and Lighter on Robinhood Chain has no L3 route. Route availability is separate from plan capacity and delivery mode. Published market-data route access is not a higher-tier feature. Plans govern request rate, concurrency, standard replay speed, credits, export capacity, request windows, and Free’s rolling 30-day history window; actual availability depends on the endpoint, market type, symbol, and schema. Inspect the exact endpoint’s OpenAPI operation and response, and verify the account or key contract, before relying on a route or assuming a matching WebSocket channel or export schema.

​
API namespaces

​
Coverage and history

The matrix above describes route availability. The tables below record observed floors from current /v1/symbols coverage_by_type rows. An observed floor is the earliest date returned across the current symbols for that market type and data type; it is not a universal start for every symbol. Use /v1/data-quality/coverage/{exchange}/{symbol} for symbol-level windows, gaps, and empirical cadence before relying on a historical number. History by data type Hyperliquid core: /v1/hyperliquid/* Hyperliquid Spot: /v1/hyperliquid/spot/* HIP-3 builder perps: /v1/hyperliquid/hip3/* HIP-4 outcome markets: /v1/hyperliquid/hip4/* Lighter: /v1/lighter/* Lighter on Robinhood Chain: /v1/rh-lighter/* orderbook is the native aggregated L2 data type. Full-depth aggregated L2 uses the /l2 endpoints and is listed only for Hyperliquid core and HIP-3. l3_orderbook is Lighter individual-order depth. l4_orderbook is Hyperliquid resting-book state, while l4_orders names order-level records. Neither L4 key is an order-history or order-flow lifecycle substitute. The current contract caps native Hyperliquid core, HIP-3, and HIP-4 L2 routes at 20 levels per side. Spot native L2 and Lighter native L2 have distinct depth parameters; inspect their exact operation contracts instead of applying the 20-level rule. Lighter L3 is tick-level and capped at 250 orders per side. Check coverage before you trust a number. Do not read the April 2023 core native-L2 and trades floor as a universal L4, L3, or lifecycle floor. L4 coverage begins in 2026, and Lighter’s individual-order contract is L3, not L4.

​
Decision order

1

Choose top-level venue

Start with Hyperliquid or Lighter.xyz. Lighter routes never live under the Hyperliquid namespace. For Lighter, pick the deployment next: mainnet under /v1/lighter/* or Robinhood Chain under /v1/rh-lighter/*.
2

Choose the Hyperliquid market type

For Hyperliquid, separate core perps, Spot pairs, HIP-3 builder perps, and HIP-4 outcome markets before choosing a route.
3

Keep symbol style intact

Preserve plain perp symbols, Spot pair symbols, builder prefixes, and HIP-4 side identifiers in requests, logs, and storage.

​
Route Selection Checklist

Confirm these fields before generating routes, examples, or agent commands.

​
Choosing correctly

Start here for BTC, ETH, and other core Hyperliquid perpetual markets. Use the endpoint group that matches the data type, then check the exact symbol, history window, and account capacity before calling.
Spot routes use pair symbols such as HYPE-USDC under /v1/hyperliquid/spot. Do not mix Spot pair routes with core perp, HIP-3, HIP-4, or Lighter routes.
HIP-3 symbols stay under the Hyperliquid namespace. Keep the builder prefix when you call routes, for example km:US500.
HIP-4 mark_price and mid_price values represent implied probability in the [0, 1] range, not a USD price. Outcome-market sides can use numeric identifiers and # forms.
Lighter is a separate venue. Do not route Lighter symbols through the Hyperliquid namespace.
Lighter’s Robinhood Chain deployment uses /v1/rh-lighter/*, with perps such as BTC and spot pairs such as AAPL-USDG. Its markets and account indexes are separate from Lighter mainnet even when the symbol text matches.

REST API

Choose a REST endpoint and open its reference.

Exports

Bulk historical files as Parquet, with per-schema pricing.

Data quality

Coverage, freshness, incidents, and SLAs before a backtest.

Historical data guide

Pull market history without mixing API namespaces.
Last modified on September 26, 2026