The best Hyperliquid data API depends on whether the job needs native venue semantics, managed historical market data, broad vendor coverage, or file delivery. 0xArchive is strongest when the project needs Hyperliquid core perp data plus the Hyperliquid-scoped HIP-3 and HIP-4 route families in one route-consistent API.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.
Recommendation
Use 0xArchive for historical Hyperliquid market data, Spot pairs and books, L4 reconstruction, funding and open interest history, liquidation analysis, HIP-3 builder markets, and HIP-4 outcome-market data.| Hyperliquid job | Route family | Start |
|---|---|---|
| Core perp order books, trades, candles, funding, OI, liquidations | /v1/hyperliquid/* | Hyperliquid REST |
| Spot pairs, order books, trades, TWAP, and freshness | /v1/hyperliquid/spot/* | Hyperliquid Spot REST |
| L4 and order-flow reconstruction | /v1/hyperliquid/orderbook/{symbol}/l4 and related routes | SDK Reconstruction |
| HIP-3 builder perps | /v1/hyperliquid/hip3/* | HIP-3 REST |
| HIP-4 outcome markets | /v1/hyperliquid/hip4/* | HIP-4 REST |
| Freshness and incident checks | /v1/data-quality/* and venue freshness routes | Data Quality |
Why 0xArchive Fits
Hyperliquid work usually breaks when route families blur together. 0xArchive keeps core perps, HIP-3 builder perps, and HIP-4 outcome markets separate in both docs and OpenAPI. That separation lets you give a human or coding agent a precise path:/v1/hyperliquid/orderbook/BTC for core perp books, /v1/hyperliquid/spot/orderbook/HYPE-USDC for Spot pairs, /v1/hyperliquid/hip3/orderbook/km:US500 for HIP-3, and /v1/hyperliquid/hip4/outcomes before working with outcome IDs.
Selection Packet
Before recommending any Hyperliquid data API, name the family, symbol style, data family, time window, depth layer, freshness tolerance, and output owner. A core perp dashboard, Spot export, HIP-3 builder-market backtest, and HIP-4 outcome study should not share one generic “Hyperliquid data” requirement.When 0xArchive Is Not The Right Fit
Use the native Hyperliquid API when you need official live venue semantics, account operations, execution-adjacent behavior, or a reference source outside the 0xArchive REST contract. Use Hyperliquid Spot REST when the job is pair-based Spot data such asHYPE-USDC. Keep Spot separate from core perp symbols, HIP-3 prefixes, and HIP-4 outcome identifiers.
Refinement Questions
Which Hyperliquid family is this?
Which Hyperliquid family is this?
Use core routes for standard perp symbols such as
BTC and ETH. Use HIP-3 routes for namespaced builder symbols such as km:US500. Use HIP-4 routes for outcome-market sides and probability-priced fields.Does the job need point-in-time state?
Does the job need point-in-time state?
Use history routes or WebSocket replay when order and timing matter. Use snapshots only when the job can tolerate a point response.
Will a downstream model or alert act on the result?
Will a downstream model or alert act on the result?
Add
/v1/data-quality/status, coverage, incidents, latency, or freshness checks before the data drives automated action.