/v1/lighter/*, and HIP-3 and HIP-4 are Hyperliquid-scoped families, not separate top-level venues.
0xArchive exposes two top-level venue APIs: Hyperliquid and Lighter.xyz. Hyperliquid core perps, Hyperliquid Spot, HIP-3, and HIP-4 are separate Hyperliquid-scoped market families. Lighter routes stay under /v1/lighter/*.
For the product view, explore Hyperliquid data or Lighter data. Use this page when you need the exact venue, symbol, schema, and history window.
What we cover by venue
One API, five venue families. This grid shows which data type each family serves; on every data-type page, venue is a switch. Coverage windows (how far back) are in the next section.
* Lighter funding records are returnable, but currently served values must not be compared across venues or annualized pending normalization repair.
Order books are L2 on every venue. Hyperliquid L4 resting-order depth begins in March 2026 on core, Spot, and HIP-3 and in May 2026 on HIP-4; its checkpoint, ordered diff, and history routes are separate from order-history and order-flow lifecycle routes. Lighter exposes L3 individual-order depth from March 2026. Each cell is available over REST; most also stream over WebSocket and ship as bulk exports, and each data-type page lists which access methods apply.
Route Families
Coverage and history
How far back each data type goes is below; every window runs from its listed start to the present and updates continuously. Hyperliquid order books run to April 2023; Lighter to January 2026 at tick level, with an order-level L3 book from March 2026. For the current symbol list and live data-quality, use/v1/symbols, /v1/status/coverage, and the data-quality coverage and freshness routes. See Data quality.
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/*
On Hyperliquid, order books are reconstructed to roughly 1.2-second snapshots; Lighter is tick-level. Check a specific market’s current status and gaps with the coverage and freshness routes before a backtest.
Decision Order
1
Choose top-level venue
Start with Hyperliquid or Lighter.xyz. Lighter routes never live under the Hyperliquid namespace.
2
Choose Hyperliquid family
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
Use Hyperliquid core for standard perp symbols
Use Hyperliquid core for standard perp symbols
Start here for
BTC, ETH, and other core Hyperliquid perp markets. Use route families for order books, trades, candles, funding, open interest, liquidations, orders, and L4 depth where your plan allows it.Use Hyperliquid Spot for pair symbols
Use Hyperliquid Spot for pair symbols
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.Use HIP-3 for builder-perp markets
Use HIP-3 for builder-perp markets
HIP-3 symbols stay under the Hyperliquid namespace. Keep the builder prefix when you call routes, for example
km:US500.Use HIP-4 for outcome-market sides
Use HIP-4 for outcome-market sides
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.Use Lighter for Lighter-specific history and depth
Use Lighter for Lighter-specific history and depth
Lighter is a separate top-level venue family. Do not route Lighter symbols through the Hyperliquid namespace.
REST API
Open the route atlas and Endpoint 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 route families.