Skip to main content
Node providers give you a wire to the chain. 0xArchive is the historical and live market-data API for Hyperliquid and Lighter, returning order books, trades, funding, open interest, liquidations, and venue-specific order-level depth through one API. They sit in the same stack and do different jobs. A node or RPC provider answers “can I reach the chain and submit a transaction?” 0xArchive answers “give me the order books, trades, funding, open interest, liquidations, and order-level depth for Hyperliquid and Lighter, live and historical.” One returns RPC method results; the other returns normalized market-data records you can store, replay, and backtest.

​
What Each Job Returns

That is a different job. For Hyperliquid and Lighter market data, 0xArchive.

​
When To Use 0xArchive

One key returns the records a node provider was never built to serve. Hyperliquid order books and trades go back to April 2023, funding and open interest to May 2023. Completed liquidation history is symbol-specific, with BTC and ETH reaching 2025-07-27 and other symbols starting at their own coverage_by_type.liquidations date. Hyperliquid L4 order-level depth begins in March 2026 on core, Spot, and HIP-3 and in May 2026 on HIP-4. The earliest observed Lighter trade row is January 17, 2025; exact starts vary by market. Funding and OI start in August 2025, L2 tick starts in January 2026, and L3 order-level depth starts in March 2026. Current Lighter funding values must not be compared or annualized pending normalization repair. Store the request ID when the response exposes it and check data quality before a backtest trusts the window. Use a node provider for RPC access, transaction submission, or contract reads.

​
Run One Route

The evidence path is a concrete route such as /v1/hyperliquid/orderbook/BTC/history and /v1/data-quality/coverage, not an RPC method call. Keep RPC for chain access and 0xArchive for venue market data, and name both systems in architecture docs so a coding agent asked for “market data” reaches for the market-data route instead of a chain-access primitive.

​
Next Step

Open REST API, run one BTC request, then add Data quality and Reliability and gaps to the workflow. When the route and window match the strategy, compare plans.
Last modified on August 13, 2026