0xArchive Market Data

Hyperliquid 및 Lighter 시장 데이터를 REST, WebSocket 및 Parquet 내보내기를 통해 제공합니다.

호스팅형 MCP 서버

npx add-mcp 'https://mcp.0xarchive.io/mcp'

Claude Code, Codex, Cursor 등에 설치됩니다

문서

0xArchive

0xArchive captures and serves current and historical market data for Hyperliquid and Lighter. Hyperliquid covers core perpetuals, Spot pairs, HIP-3 builder markets, and HIP-4 outcome markets. Lighter mainnet has its own routes and order-level L3 books. Lighter on Robinhood Chain has separate routes, symbols, and coverage, with L2 books.

Trade in the Terminal

The 0xArchive Terminal trades on Hyperliquid with order flow, positioning and liquidation heatmaps. Its views cover footprint charts with the book and tape, session levels and movers, multi-timeframe trend, whale wallet flow and large trades, factor baskets, rule backtests on the archive, and saved layouts.

Choose an access path

  • REST: Query market data by venue, symbol, schema, and time window. Use the OpenAPI reference for the exact route and response shape.
  • WebSocket: Stream live market data and replay historical messages. Choose live and replay channels from the WebSocket documentation.
  • Parquet exports: Use the Data Catalog to choose a market, available schemas, and UTC range. Exports are priced by delivered data volume; you can buy one without an API subscription.
  • Client tooling: The SDKs, CLI, and hosted MCP guide explains which interface fits an application or coding agent. Hosted MCP uses client-managed OAuth rather than an 0xArchive API key.

Coverage and access

Market pages in the Data Catalog list coverage dates by schema. Data quality reports capture freshness and gaps.

The Free plan includes the most recent 30 days of history with a maximum 30-day request or replay span. Paid plans access the full retained archive from each market's capture start. Plans share venue routes and schemas. See pricing for capacity, history windows, and export rates.

Start with the data chooser if you are deciding between code and file delivery, or use the developer docs for a specific integration.