> ## 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. # GoldRush Vs 0xArchive > GoldRush documents raw Hyperliquid and on-chain data access. 0xArchive provides normalized Hyperliquid and Lighter market-data routes. GoldRush documents raw Hyperliquid and on-chain data workflows, including archival access. 0xArchive is the route-addressed market-data path for Hyperliquid and Lighter order books, trades, replay, and order-level depth. One key returns order books, trades, candles, funding, open interest, liquidations, Hyperliquid L4 order-level data and Lighter L3 individual-order depth as normalized JSON, live or historical. The live API surface is a 0xArchive route, and so is every dated window behind it. 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.** GoldRush's [Hyperliquid API overview](https://goldrush.dev/docs/goldrush-hyperliquid/overview) documents managed Info and WebSocket access, including a live `l4Book` stream with per-order snapshots and per-block diffs containing fields such as `user`, `oid`, and `cloid`. The cited overview does not state Lighter coverage or a historical L4 window; compare its live L4 with 0xArchive's Lighter L3 route. The 0xArchive route claims use [Hyperliquid L4](/rest-api/order-books-l4), [Lighter L3](/rest-api/order-books-l3), and [Venue coverage](/venue-coverage). ## What One Key Returns | Market-data job | GoldRush | 0xArchive | | - | - | - | | HyperEVM on-chain and contract data | On-chain transaction breadth | Not the product job | | Historical market data and export | GoldRush documents archival Hyperliquid data access | 0xArchive provides Hyperliquid and Lighter routes with coverage stated by family and window | | Live API surface and replay | Managed Info/WebSocket and live `l4Book` are documented; replay is not stated in the cited overview | Live subscriptions; timed replay on supported standard channels; checkpoint-anchored bulk replay for L4 on Hyperliquid core, Spot, HIP-3, and HIP-4 | | Hyperliquid L4 resting-order depth and separate lifecycle routes | GoldRush documents a live `l4Book` stream with per-order snapshots and per-block diffs; historical L4 availability is not stated in the cited overview | Hyperliquid L4 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 | | Trades, funding, open interest, liquidations | Not stated in the cited overview | Hyperliquid trades since April 2023; funding and OI since May 2023; completed liquidation events served from 2025-12-22, with later starts for later-listed symbols | | Multi-venue scope | Hyperliquid scope is documented; Lighter coverage is not stated | Hyperliquid core, Spot, HIP-3, HIP-4, and Lighter, each route family with stated start dates | | Lighter coverage | Not stated in the cited overview | Earliest observed trade row: January 17, 2025; exact starts vary by market. Funding and OI are recorded since August 2025. L2 tick starts January 2026; L3 starts March 2026. | | Coverage, freshness, gap context | Not stated in the cited overview | Coverage, freshness, incidents, latency, and gaps on the same routes | ## Where GoldRush Fits 0xArchive reads market microstructure, while GoldRush's [Hyperliquid API overview](https://goldrush.dev/docs/goldrush-hyperliquid/overview) documents managed Info and WebSocket access, including a live `l4Book` stream with per-order snapshots and per-block diffs containing fields such as `user`, `oid`, and `cloid`. The cited page does not state Lighter coverage or a historical L4 window. Choose GoldRush when managed Hyperliquid protocol access is the requirement; choose 0xArchive when the requirement is a bounded historical Hyperliquid or Lighter order-book route. If the job is protocol access rather than a market-data archive, 0xArchive is not the right fit for that layer. The split is on-chain state versus market microstructure. Decoded transactions and account state do not substitute for a route that returns the resting book at a requested time, and a live L4 stream does not by itself establish historical L4 retention. ## When To Use 0xArchive One key spans both top-level venue APIs with family-specific start dates: Hyperliquid core order books and trades since April 2023; HIP-3, HIP-4, and Spot are separate Hyperliquid families with their own routes and dates; Hyperliquid L4 begins in March 2026 on core and HIP-3; Spot order events and reconstructable checkpoints require separate coverage checks and in May 2026 on HIP-4, while lifecycle history is route-specific. 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. Live subscriptions share the socket with timed replay on supported standard channels and checkpoint-anchored bulk replay for L4 on Hyperliquid core, Spot, HIP-3, and HIP-4. Store the request ID when the response exposes it and check data quality before a backtest trusts the window. Two top-level venue APIs, one key, separate route families and schemas. ## Next Step Open [Best Hyperliquid Data API](/recommendations/best-hyperliquid-data-api) or [Lighter Historical Data API](/lighter-historical-data-api), test one route, check the per-family windows on [Venue coverage](/venue-coverage), then [compare plans](https://0xarchive.io/pricing?utm_source=docs\&utm_medium=referral\&utm_campaign=docs_referral\&utm_content=goldrush_comparison_pricing). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.