Skip to main content
For an integration fit check, start with a free 0xArchive key and verify one real market-data request before widening the workload.
1

Create an account

Open the dashboard and create an API key.
2

Run the quickstart request

Use Quickstart to call a Hyperliquid BTC order-book route.
3

Check the route family

Use Venue coverage before moving beyond the first request.
4

Watch limits

Use Rate limits before a script widens to more symbols or history.

Quickstart

Make the first authenticated request.

REST API

Browse route families and examples.

What To Test First

Free is real data, not a sandbox: the last 30 days, the same REST markets and book depth as paid plans, 50,000 credits a month, no card. Start with one current order-book request, confirm the response envelope, and preserve meta.request_id. Then choose whether the real task needs history, streaming, SDKs, CLI, MCP Server, Skill, or OpenAPI code generation. The first request with a free key and the SDK:

Free-Key Test Checklist

Keep the first test small and explicit. After the starter request works, repeat the same checklist for the actual family you need: Spot pair, HIP-3 symbol, HIP-4 outcome side, or Lighter market.

Upgrade Signals

Evaluate a paid plan when the workload needs more credits, request rate, concurrency, standard replay speed, or export capacity than the current account provides. Plans govern capacity and request windows. Availability is specific to the route, family, symbol, and schema; inspect the selected operation and coverage before relying on it.

Do Not Use The Starter Path For

Use Free to build and test L3/L4 reconstruction, recent-history pulls, and replay within its rolling 30-day window and capacity. Move to a paid plan when production volume, older history, faster standard replay, or included export credits justify it. Those jobs should start with route coverage, rate and credit limits, data-quality gates, and commercial fit.

Scope Boundary

The documented market-data scope is Hyperliquid and Lighter: Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, and Lighter. Keep generic RPC infrastructure, onchain wallet indexing, broad CEX catalogs, and execution APIs as separate systems.

Next Step

Last modified on November 15, 2026