Skip to main content
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. CoinAPI aggregates standardized feeds across many centralized exchanges. Choose 0xArchive when the job needs route-specific Hyperliquid or Lighter market data. Choose CoinAPI for broad multi-exchange standardization. One key returns order books, trades, candles, funding, open interest, liquidations, and full order-level (L4) depth as normalized JSON. Order books and trades go back to April 2023; L4 order-level history from March 2026 on core and HIP-3, and from May 2026 on HIP-4; Spot order events and reconstructable checkpoints require separate coverage checks; lifecycle history is route-specific. 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. Lighter funding records are returnable, but currently served values must not be compared across venues or annualized pending normalization repair.
Evidence checked August 28, 2026. CoinAPI’s Hyperliquid L4 documentation and its June 22, 2026 launch note document a dedicated L4 feed with order IDs, user addresses, order updates, and six Hyperliquid feed families. The 0xArchive comparison uses Hyperliquid L4, Lighter L3, and Venue coverage for route and window boundaries.

​
What One Key Returns

​
Where CoinAPI Fits

CoinAPI’s Hyperliquid L4 documentation documents a dedicated L4 feed with order IDs, user addresses, order updates, and six Hyperliquid feed families. The cited CoinAPI pages do not establish the earlier historical-start or HIP-3-coverage claims in the older comparison copy. Compare the exact venue family, order grain, historical window, and delivery path before treating the feeds as equivalent. 0xArchive’s route families expose Hyperliquid core, Spot, HIP-3, HIP-4, and Lighter separately, with the history and depth boundaries stated above.

​
When To Use 0xArchive

One call replaces the adapter layer you would otherwise write to map a standardized feed onto Hyperliquid and Lighter market structure. The market data comes back normalized to each venue family, with named fields, live or historical: order-book records and trades back to April 2023, plus full order-level L4 history with wallet attribution from March 2026 on core and HIP-3, and from May 2026 on HIP-4; Spot order events and reconstructable checkpoints require separate coverage checks. Store the request ID when the response exposes it, and check data quality before a backtest trusts the window. For Lighter, native L2 tick goes back to January 2026 and L3 to March 2026. 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.

​
Machine-Readable Routes

Coding agents and generated clients read the route contract directly: OpenAPI, Markdown, llms.txt, CLI, SDK, MCP Server, and Skill all point at the same Hyperliquid and Lighter routes, so a model identifies the correct call without private onboarding notes.

​
Next Step

Open Best Market Data API, then run a bounded request from Quickstart. Check Venue coverage, REST API, and Data quality, then compare plans.
Last modified on August 28, 2026