> ## 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.

# CoinAPI Vs 0xArchive

> Compare CoinAPI's broad exchange coverage with 0xArchive's live and historical Hyperliquid and Lighter market data, Hyperliquid L4, and Lighter L3.

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.

> **Evidence checked August 28, 2026.** CoinAPI's [Hyperliquid L4 documentation](https://www.coinapi.io/products/market-data-api/docs/websocket-ds/hyperliquid) and its [June 22, 2026 launch note](https://www.coinapi.io/blog/coinapi-introduces-hyperliquid-l4-data) document a dedicated L4 feed with order IDs, user addresses, order updates, and six Hyperliquid feed families. The 0xArchive comparison uses [Hyperliquid L4](/rest-api/order-books-l4), [Lighter L3](/rest-api/order-books-l3), and [Venue coverage](/venue-coverage) for route and window boundaries.

## What One Key Returns

| Hyperliquid and Lighter market data | CoinAPI | 0xArchive |
| - | - | - |
| Order books (L2), live and historical | Many CEXs | 20-level snapshots about every 1.2 seconds since April 2023 |
| Trades | Many CEXs | Since April 2023, continuous to the current hour |
| Funding and open interest | Many CEXs | Since May 2023 |
| Liquidations | Many CEXs | Completed events from each symbol's `coverage_by_type.liquidations` start |
| Hyperliquid L4 resting-order depth and separate lifecycle routes | Hyperliquid L4 with wallet attribution, launched June 2026 | 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 |
| Lighter order books | Broad multi-exchange aggregation | L2 tick since January 2026, L3 since March 2026 |
| Live stream and replay | Broad multi-exchange aggregation | Live subscriptions; timed replay on supported standard channels; checkpoint-anchored bulk replay for L4 on Hyperliquid core, Spot, HIP-3, and HIP-4 |
| Spot, HIP-3, HIP-4 | HIP-3 deployer contracts listed | Separate Hyperliquid-scoped families for Spot, HIP-3, and HIP-4, each with its own history |

## Where CoinAPI Fits

CoinAPI's [Hyperliquid L4 documentation](https://www.coinapi.io/products/market-data-api/docs/websocket-ds/hyperliquid) 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](/recommendations/best-market-data-api), then run a bounded request from [Quickstart](/quickstart). Check [Venue coverage](/venue-coverage), [REST API](/rest-api), and [Data quality](/data-quality), then [compare plans](https://0xarchive.io/pricing?utm_source=docs\&utm_medium=referral\&utm_campaign=docs_referral\&utm_content=coinapi_comparison_pricing).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.