Skip to main content
Every order, trade, and fill on Hyperliquid and Lighter, live and historical, from one API. Velo Data is a trader-facing analytics UI for reading heatmaps, CVD, and desk-style charts. For the underlying market data, the kind you store, backtest, and feed to a model or agent, you call 0xArchive. One key returns order books, trades, candles, funding, open interest, liquidations, and full order-level (L4) depth as normalized JSON, live or historical. Order books and trades go back to April 2023; order-level depth and lifecycle since March 2026. No collectors, no backfill, no rebuilding the book behind the chart.

What One Key Returns

Market-data jobTrader analytics UI0xArchive
Prebuilt heatmaps and desk chartsReady-made visual workflowNot the lead product job
Order books (L2), live and historical---20-level snapshots about every 1.2 seconds since April 2023, 24.6B+ records, 176 Hyperliquid symbols
Trades, funding, open interest---Trades since April 2023, funding and open interest since May 2023, continuous to the current hour
Liquidations---Since December 2025
Order-level depth (L4) and lifecycle---Every order add, fill, cancel, and TP/SL, with wallet attribution, since March 2026
Lighter coverage---Trades and funding since August 2025, L3 order-level since March 2026
Live stream and replay---WebSocket subscriptions and exact-window replay on one socket
Developer-owned access---REST, WebSocket, SDK, CLI, OpenAPI, one API key

Where Velo Data Fits

0xArchive returns tick-level records, not desk charts; the cross-exchange charting layer is Velo’s product. Its docs describe futures, options, and spot data at one-minute-or-coarser resolution across venues such as Binance Futures and Bybit, with Python and Node clients, CSV downloads from the webapp, and unauthenticated product listing on the /futures, /options, and /spot endpoints. API keys are $199 a month; monthly billing includes 3 months of history, yearly billing the full history. When the job is desk charts and minute-level metrics across many venues, that workflow is Velo’s, and 0xArchive is not the right fit for it; this API supplies the raw resolution a chart cannot give back. The resolution decides the reverse case: a one-minute cross-exchange series cannot answer tick-level Hyperliquid or Lighter order-book questions, and no dashboard export rebuilds the book behind the chart.

When To Use 0xArchive

One call replaces the collector you would otherwise build and run behind a dashboard. The market data comes back normalized, with named fields, live or historical: more than 24 billion order-book records and trades back to April 2023, plus full order-level (L4) depth with wallet attribution since March 2026, and Lighter L3 since March 2026. Every response carries a request ID and a data-quality path you can check before a backtest trusts the window. When the output has to become rows in a warehouse, inputs to a model, a replayable backtest, an API-backed feature, or a coding-agent task, you build on the data, not on a screenshot of it. Every route, market family, and schema is available on every tier, including Free, and agents reach the same routes through the hosted MCP server at https://mcp.0xarchive.io/mcp. Every order, trade, and fill. One API.

Next Step

Open Historical market data, then add Data quality and Data rights. When you are ready to build, compare plans.
Last modified on July 4, 2026