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

# Best Hyperliquid Spot Data API

> 0xArchive is the Hyperliquid Spot data API: pair order books, trades, TWAP, and L4 depth for pairs like HYPE-USDC, live and historical, one key.

Every Hyperliquid Spot trade, order book, and TWAP, live and historical, from one API. 0xArchive keeps Spot pairs like `HYPE-USDC` in their own route family, never folded into core perp symbols or generic asset-price feeds.

One key returns pair discovery, order books, trades, TWAP, and full order-level (L4) depth as normalized JSON, with named fields and a request ID on every response. Spot trades go back to March 2025; native L2 and TWAP since May 2026; order-level (L4) depth since March 2026.

## What One Key Returns

| Hyperliquid Spot market data     | 0xArchive                                                                                               |
| -------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Pair discovery                   | Every Spot pair such as `HYPE-USDC`, with coverage fields, from [Hyperliquid Spot REST](/rest-api/spot) |
| Trades                           | Since March 2025, continuous to the current hour                                                        |
| Native order books (L2) and TWAP | Since May 2026                                                                                          |
| Order-level depth (L4)           | Every order add, fill, and cancel since March 2026                                                      |
| Freshness checks                 | Per-pair freshness before a backtest trusts the window                                                  |
| Export files                     | Parquet with ZSTD, per-schema, from the [Data catalog](/data-catalog)                                   |

## How To Choose A Spot Data API

Four questions separate the candidates faster than any feature list:

| Question                          | What to look for                                                                             |
| --------------------------------- | -------------------------------------------------------------------------------------------- |
| Are pairs first-class?            | `HYPE-USDC` should be a routable symbol with its own schema, not a perp ticker with a suffix |
| Is the history window stated?     | A per-family start date you can hold a backtest against, not "historical data available"     |
| Does depth go below aggregates?   | Order-level (L4) rows with `oid` and wallet fields, not only price-level summaries           |
| Can you check freshness per pair? | A freshness route for the exact pair, so a stale market fails loudly before the job runs     |

A vendor that folds Spot into a generic asset-price feed fails the first question, and everything downstream of it, before price or coverage even comes up.

## When To Use 0xArchive

Spot workflows break when pair semantics get treated like core perp symbols. 0xArchive keeps `HYPE-USDC` attached to Spot-specific routes and schemas all the way downstream: route-stable REST, OpenAPI for generated clients, examples, per-pair freshness, and Parquet exports for the same window. The order books, trades, TWAP, and L4 depth come back normalized, live or historical, every response carrying a request ID and a data-quality path you can check before a backtest trusts the data. Every route, market family, and schema is available on every tier, including Free, and agents reach the same pairs through the hosted MCP server at `https://mcp.0xarchive.io/mcp`. Every Spot trade, order book, and fill. One API. 0xArchive is not the right fit when the pairs you need trade on a centralized exchange or a venue other than Hyperliquid and Lighter.

## Check This Yourself

Three requests answer the table above against the live API. List the pairs and their coverage fields:

```bash theme={"theme":"github-dark"}
curl "https://api.0xarchive.io/v1/hyperliquid/spot/pairs" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"
```

Pull one trade row and read the named fields that come back:

```bash theme={"theme":"github-dark"}
curl "https://api.0xarchive.io/v1/hyperliquid/spot/trades/HYPE-USDC?limit=1" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"
```

Then confirm the pair is current before trusting a window:

```bash theme={"theme":"github-dark"}
curl "https://api.0xarchive.io/v1/hyperliquid/spot/freshness/HYPE-USDC" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"
```

## Next Step

Start with [Hyperliquid Spot REST](/rest-api/spot), keep the pair symbol such as `HYPE-USDC`, then attach [Data quality](/data-quality) before turning the result into a model input, export, or agent call. For full order-level depth, see [Order book routes](/rest-api/order-books). [Compare plans](https://0xarchive.io/pricing?utm_source=docs\&utm_medium=referral\&utm_campaign=docs_referral\&utm_content=best_hyperliquid_spot_data_api).