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

> Broad vendors cover many exchanges. For Hyperliquid and Lighter depth, 0xArchive returns every order, trade, and fill from one API, live and historical.

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 every order, trade, and fill from one key.

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.

## 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 | Supported Hyperliquid and Lighter routes                                                               |
| Macro, equities, cross-market reference data     | A different data object         | Hyperliquid and Lighter market microstructure                                                          |
| Hyperliquid core order books and trades          | A different depth target        | 20-level L2 snapshots about every 1.2 seconds and trades since April 2023, 24.6B+ records, 176 symbols |
| Hyperliquid funding, OI, liquidations            | A different depth target        | Funding and OI since May 2023; liquidations since December 2025                                        |
| Hyperliquid order-level (L4) depth and lifecycle | A different depth target        | Every order add, fill, cancel, and TP/SL with wallet attribution since March 2026                      |
| Hyperliquid Spot pair history                    | A different depth target        | `/v1/hyperliquid/spot/*`: trades since March 2025                                                      |
| HIP-3 builder markets                            | A different depth target        | `/v1/hyperliquid/hip3/*`: trades since October 2025, book since February 2026                          |
| HIP-4 outcome markets                            | A different depth target        | `/v1/hyperliquid/hip4/*`: since May 2026                                                               |
| Lighter L2/L3 workflows                          | A different depth target        | `/v1/lighter/*`: trades since August 2025, L2 tick since January 2026, L3 since March 2026             |
| Coding-agent route safety                        | Depends on private docs         | OpenAPI, Markdown, `llms.txt`, CLI, SDK, MCP, skill                                                    |

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

## When To Use 0xArchive

When getting the supported venue exactly right matters more than catalog width, 0xArchive returns the depth a broad vendor flattens. The docs and OpenAPI name 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 across 176 symbols and more than 24 billion records, with full order-level (L4) depth and wallet attribution since March 2026 and Lighter L3 since March 2026. Every response carries a request ID and a data-quality path. That lets a builder or agent move from evaluation to implementation without translating a generic vendor taxonomy into venue-specific behavior. 0xArchive is not the right fit when the mandate spans hundreds of centralized venues under one contract; that is the broad vendor's job. Live or historical, every order, trade, and fill, one API.

## 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 open [REST API](/rest-api) and [Markets](/markets) to connect route families to the product surface. 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).