0xArchive provides historical and live market-data records for Hyperliquid and Lighter through one API. Coverage depends on venue family, data type, symbol, and time window. QuickNode documents RPC, node, and Hyperliquid HyperCore stream infrastructure for connecting to networks. For route-addressed historical Hyperliquid and Lighter market data, you call 0xArchive: the historical and live market-data API for Hyperliquid and Lighter.
One key returns order books, trades, candles, funding, open interest, liquidations, and order-level (L4) depth as normalized JSON. Hyperliquid order books and trades go back to April 2023. L4 order-level history starts in March 2026 on core and HIP-3 and in May 2026 on HIP-4; Spot order events and reconstructable checkpoints require separate coverage checks. Lifecycle history is route-specific. The earliest observed Lighter trade row is January 17, 2025; exact starts vary by market. 0xArchive removes venue collection and historical backfill work; supported reconstruction routes return a checkpoint/snapshot. A snapshot-only consumer can use that state directly. A continuously updated local L4 book still must apply ordered diffs or replay, detect gaps, and reconstruct state after the checkpoint; the API does not remove those local-state obligations.
Evidence checked August 28, 2026. QuickNode’s Hyperliquid page and Hyperliquid documentation are the first-party sources for its RPC, HyperCore, and stream surfaces. The 0xArchive route claims use Venue coverage, Hyperliquid L4, Lighter L3, and Replay and reconstruction.
What One Key Returns
Where QuickNode Fits
QuickNode documents RPC endpoints and Hyperliquid HyperCore access, including protocol-native market-data stream surfaces. Use that category for RPC or protocol access; use 0xArchive for route-addressed market-data history and replay.
The gap runs the other way for historical market data. A node or protocol stream may expose live state, but the cited QuickNode pages do not state the bounded Hyperliquid and Lighter history, order grain, or data-quality contract needed for a backtest. 0xArchive is not the right fit for RPC, node, or HyperCore stream infrastructure. Compare those axes before treating a stream as an archive.
When To Use 0xArchive
0xArchive removes venue collection and historical backfill work; supported reconstruction routes return a checkpoint/snapshot. A snapshot-only consumer can use that state directly. A continuously updated local L4 book still must apply ordered diffs or replay, detect gaps, and reconstruct state after the checkpoint; the API does not remove those local-state obligations. Hyperliquid order-book records and trades go back to April 2023, and order-level L4 history with wallet attribution starts in March 2026 on core and HIP-3 and in May 2026 on HIP-4; Spot order events and reconstructable checkpoints require separate coverage checks. The earliest observed Lighter trade row is January 17, 2025; exact starts vary by market. Store the request ID when the response exposes it, and check data quality before a backtest trusts the window. Plans govern capacity and request windows. Availability is specific to the route, family, symbol, and schema; inspect the selected operation and coverage before relying on it. Plans can affect credits, request rate, and standard replay speed. Agents use the same routes through the hosted MCP server at https://mcp.0xarchive.io/mcp with client-managed OAuth; it requires no 0xArchive API key. Use the client’s built-in OAuth flow and approve mcp:market.read through https://auth.0xarchive.io.
Run One Route
Next Step
Open REST API, run one BTC request, then add Data quality and Reliability and gaps. Compare plans. Last modified on September 14, 2026
