Evidence checked August 28, 2026. QuickNode’s Hyperliquid page and HyperCore API documentation show managed Hyperliquid protocol access, while Dwellir’s L4 order-book documentation shows a provider-specific live order-book surface. The 0xArchive route and coverage claims use Venue coverage, Hyperliquid L4, and Lighter L3.Node capacity is not the same as a documented historical market-data window. Compare retention, order grain, replay, and quality behavior for the exact workload.
What Each Job Returns
That is a different job. For Hyperliquid and Lighter market data, 0xArchive.
When To Use 0xArchive
One key returns historical market-data records that a node or RPC endpoint does not automatically provide. 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 owncoverage_by_type.liquidations date. Hyperliquid L4 order-level history begins 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. Funding and OI start in August 2025, L2 tick starts in January 2026, and L3 order-level depth starts in March 2026. 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
/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.