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

# Analytics Platforms Vs Market Data APIs

> Analytics platforms hand you prebuilt dashboards. For Hyperliquid and Lighter market data, 0xArchive returns every order, trade, and fill from one API.

Analytics platforms hand you finished dashboards. 0xArchive is the historical and live market-data API for Hyperliquid and Lighter, returning every order, trade, and fill as records your system can store, parse, replay, and audit.

A dashboard answers an interpreted question on a screen. 0xArchive supplies the underlying records that a product, model, agent, warehouse, or backtest can own. The two do different jobs.

## What Each Job Returns

| Need                                                    | Analytics platform                             | 0xArchive                                                                                                |
| ------------------------------------------------------- | ---------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| Prebuilt dashboards and screens                         | Renders finished charts and views              | A different data object                                                                                  |
| Interpreted metrics and ranked tables                   | Computes and displays the metric for you       | A different data object                                                                                  |
| No-code visual exploration                              | Point-and-click interface over a fixed dataset | A different data object                                                                                  |
| Hyperliquid order books and trades, live and historical | A finished view, not the rows                  | 20-level L2 snapshots about every 1.2 seconds and trades since April 2023, 24.6B+ records, 176 symbols   |
| Funding, open interest, liquidations                    | A finished view, not the rows                  | Funding and OI since May 2023; liquidations since December 2025                                          |
| Order-level (L4) depth and lifecycle                    | A finished view, not the rows                  | Every order add, fill, cancel, and TP/SL with wallet attribution since March 2026 (Hyperliquid families) |
| Lighter order books, trades, L3                         | A finished view, not the rows                  | Trades since August 2025; L2 tick since January 2026; L3 since March 2026                                |
| Product-owned data pipeline                             | A different data object                        | Route-stable JSON for apps, models, and agents                                                           |
| Backtests and replay                                    | A different data object                        | REST history, WebSocket replay, and reconstruction with request IDs                                      |
| Warehouse files                                         | A different data object                        | Data Catalog exports tied to supported venues                                                            |

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

## When To Use 0xArchive

When the job needs the rows, not the screen, 0xArchive returns supported Hyperliquid and Lighter records: order books, trades, funding, OI, liquidations, candles, L3/L4, replay, reconstruction, and exports. Hyperliquid order books and trades go back to April 2023 across 176 symbols and more than 24 billion records, funding and OI since May 2023, liquidations since December 2025, and full order-level (L4) depth with wallet attribution since March 2026; Lighter trades land from August 2025 and L3 from March 2026. Every response carries a request ID and a data-quality path you can check before a model or liquidation study trusts the window. A dashboard can answer today's question, but only route-addressed records expose the raw rows, sequence, schema, and history another system needs. 0xArchive is not the right fit when the deliverable is the dashboard itself; an analytics platform ships that screen faster than an API will. Live or historical, every order, trade, and fill, one API.

## Name The Artifact You Need

Name the artifact you will need one month from now. If it is a stored dataset, an API-backed feature, a model input, a backtest harness, an export, or an agent workflow, you need route-addressed records: a route family, an example request, a response shape, a freshness or coverage signal, and a downstream parser plan. For 0xArchive, the evidence path is a concrete route plus a data-quality check before the workflow scales beyond a small request. Do not let a screenshot or dashboard label become the record behind a model, a liquidation study, a replay job, or a warehouse dataset.

## Next Step

Start with [Best Market Data API](/recommendations/best-market-data-api), then attach [Data quality](/data-quality) and [Data rights](/data-rights). For files, route the job through [Data catalog](/data-catalog). 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=analytics_platforms_comparison_pricing).