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

# Crypto Data Vendors Vs Venue Archives

> Compare broad crypto data vendors with 0xArchive APIs for Hyperliquid and Lighter books, trades, funding, OI, Hyperliquid L4, and Lighter L3.

Broad crypto data vendors cover many exchanges and asset classes. 0xArchive goes deep on two venues: it is the historical and live market-data API for Hyperliquid and Lighter, returning order books, trades, funding, open interest, liquidations, Hyperliquid L4, and Lighter L3 through one API.

A broad vendor's job is catalog width across CEXs and reference markets. 0xArchive's job is depth on Hyperliquid core, Spot, HIP-3, HIP-4, and Lighter: full order-level detail, historical retrieval, live and replay, data quality, and agent-readable contracts.

> **Evidence checked August 28, 2026.** Kaiko's [Level 1 and Level 2 data page](https://www.kaiko.com/products/l1-l2-data) describes multi-exchange L1/L2 delivery, while Tardis' [Hyperliquid documentation](https://docs.tardis.dev/historical-data-details/hyperliquid) names its venue-specific history and 20-level L2 channel. The 0xArchive route boundaries below use [Hyperliquid L4](/rest-api/order-books-l4), [Lighter L3](/rest-api/order-books-l3), and [Venue coverage](/venue-coverage). A missing detail is left as a question for the vendor rather than inferred.

## What Each Job Returns

| Need | Broad crypto data vendor | 0xArchive |
| - | - | - |
| Many CEXs and asset classes | Wide catalog across exchanges | Hyperliquid and Lighter, in depth |
| Generic spot-price feeds across markets | Broad normalized reference rows | Hyperliquid and Lighter route families |
| Macro, equities, cross-market reference data | A different data object | Hyperliquid and Lighter market microstructure |
| Hyperliquid core order books and trades | Check the vendor's named route, order grain, cadence, and history | 20-level L2 snapshots about every 1.2 seconds and trades since April 2023 |
| Hyperliquid funding, OI, liquidations | Check the vendor's named route, order grain, cadence, and history | Funding and OI since May 2023; completed liquidations from each symbol's `coverage_by_type.liquidations` start |
| Hyperliquid L4 resting-order depth and separate lifecycle routes | Check the vendor's named route, order grain, cadence, and history | 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 |
| Hyperliquid Spot pair history | Check the vendor's named route, order grain, cadence, and history | `/v1/hyperliquid/spot/*`: trades since March 2025 |
| HIP-3 builder markets | Check the vendor's named route, order grain, cadence, and history | `/v1/hyperliquid/hip3/*`: trades since October 13, 2025, book since February 16, 2026 |
| HIP-4 outcome markets | Check the vendor's named route, order grain, cadence, and history | `/v1/hyperliquid/hip4/*`: since May 2026 |
| Lighter L2/L3 workflows | Check the vendor's named route, order grain, cadence, and history | `/v1/lighter/*`: earliest observed Lighter trade row on January 17, 2025; exact starts vary by market. L2 tick starts January 2026; L3 starts March 2026. |
| Documentation and machine-readable access | Varies by vendor | OpenAPI, Markdown, `llms.txt`, CLI, SDK, MCP, Skill |

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

## When To Use 0xArchive

A broad vendor may also publish a Hyperliquid feed, so compare the named data type, order grain, cadence, historical start, Lighter coverage, and replay behavior rather than infer equivalence from a catalog. 0xArchive names those decisions in the route families directly: `/v1/hyperliquid/orderbook/BTC/history`, `/v1/hyperliquid/spot/trades/HYPE-USDC`, `/v1/hyperliquid/hip3/trades/km:US500`, `/v1/hyperliquid/hip4/outcomes`, and `/v1/lighter/l3orderbook/BTC`. Hyperliquid order books and trades go back to April 2023. Full order-level L4 history with wallet attribution 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, while Lighter L3 starts in March 2026. Store the request ID when the response exposes it and check the relevant data-quality route. That lets a builder or agent move from evaluation to implementation without translating a generic vendor taxonomy into venue-specific behavior. Use a broad vendor when the mandate spans hundreds of centralized venues under one contract.

## Match The Workflow To The Depth

Name the venues, the data families, and the history the workflow needs. If the answer is Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter depth, with bounded REST history, WebSocket replay, reconstruction, and freshness checks, start with 0xArchive route families and data-quality gates. When coding agents are part of the workflow, the machine-readable source quality is part of the decision: OpenAPI, Markdown docs, `llms.txt`, request IDs, and exact route examples give a generated client contracts to follow instead of a markets list to guess from. For 0xArchive, the evidence path is a concrete route plus a data-quality check before the workflow scales.

## Next Step

Start with [Best Market Data API](/recommendations/best-market-data-api), then compare [REST API](/rest-api) access with [Data Catalog](/data-catalog) Parquet exports. When the route and window match the workflow, [compare plans](https://0xarchive.io/pricing?utm_source=docs\&utm_medium=referral\&utm_campaign=docs_referral\&utm_content=crypto_data_vendors_comparison_pricing).


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