/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/*.
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.| Data type | Core | Spot | HIP-3 | HIP-4 | Lighter |
|---|---|---|---|---|---|
| Order books | ✓ | ✓ | ✓ | ✓ | ✓ |
| Trades | ✓ | ✓ | ✓ | ✓ | ✓ |
| Liquidations | ✓ | — | ✓ | — | ✓ |
| Funding | ✓ | — | ✓ | — | ✓ |
| Open interest | ✓ | — | ✓ | ✓ | ✓ |
| Candles | ✓ | ✓ | ✓ | ✓ | ✓ |
| Order flow | ✓ | — | ✓ | ✓ | — |
| Order history | ✓ | ✓ | ✓ | ✓ | — |
| Take profits & stop losses | ✓ | — | ✓ | ✓ | — |
Route Families
| Family | Namespace | Symbol style | Common use |
|---|---|---|---|
| Hyperliquid core | /v1/hyperliquid/* | BTC, ETH | Perp market data, long-window history, funding, OI, liquidations, L4 |
| Hyperliquid Spot | /v1/hyperliquid/spot/* | Spot pairs such as HYPE-USDC | Spot pairs, order books, trades, candles, L4 reconstruction, TWAP, freshness |
| HIP-3 builder perps | /v1/hyperliquid/hip3/* | builder:MARKET, for example km:US500 | Builder-perp markets under Hyperliquid |
| HIP-4 outcome markets | /v1/hyperliquid/hip4/* | Numeric or # side identifiers | Binary outcome markets with probability-priced books, trades, candles, OI, and sides |
| Lighter.xyz | /v1/lighter/* | Lighter symbols | L2/L3 depth, trades, funding, OI, Lighter-specific reconstruction |
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/*
| Data | History from |
|---|---|
| Order books (L2) | Apr 2023 |
| Trades | Apr 2023 |
| Open interest | May 2023 |
| Funding | May 2023 |
| Liquidations | Dec 2025 |
/v1/hyperliquid/spot/*
| Data | History from |
|---|---|
| Trades | Mar 2025 |
| Transfers | Sep 2025 |
| TWAP | May 2026 |
| Order books (L2) | May 2026 |
/v1/hyperliquid/hip3/*
| Data | History from |
|---|---|
| Trades | Oct 2025 |
| Order books (L2) | Feb 2026 |
| Open interest | Feb 2026 |
| Funding | Feb 2026 |
/v1/hyperliquid/hip4/*
| Data | History from |
|---|---|
| Trades | May 2026 |
| Order books (L2) | May 2026 |
| Open interest | May 2026 |
| Settlements | May 2026 |
/v1/lighter/*
| Data | History from |
|---|---|
| Funding | Aug 2025 |
| Open interest | Aug 2025 |
| Trades | Aug 2025 |
| Order books (tick-level) | Jan 2026 |
| L3 order book (order-level) | Mar 2026 |
Decision Order
Choose top-level venue
Start with Hyperliquid or Lighter.xyz. Lighter routes never live under the Hyperliquid namespace.
Choose Hyperliquid family
For Hyperliquid, separate core perps, Spot pairs, HIP-3 builder perps, and HIP-4 outcome markets before choosing a route.
Route Selection Checklist
Confirm these fields before generating routes, examples, or agent commands.| Field | Capture |
|---|---|
| Top-level venue | Hyperliquid or Lighter.xyz |
| Market family | Core, Spot, HIP-3, HIP-4, or Lighter |
| Symbol style | Plain perp, pair, builder prefix, outcome identifier, or Lighter symbol |
| Route namespace | Exact namespace before endpoint selection |
| First check | Instruments, coverage, freshness, or one bounded market-data request |
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.