Skip to main content
Onchain indexers answer questions about wallets, contracts, and token holders. 0xArchive is the historical and live market-data API for Hyperliquid and Lighter, returning order books, trades, funding, open interest, liquidations, Hyperliquid L4, and Lighter L3 through one API. The right tool depends on the record you need. Lighter funding records are returnable, but currently served values must not be compared across venues or annualized pending normalization repair. Wallet histories, contract events, token-holder lists, and chain transfers are an indexer’s job. Venue order books, trades, funding, open interest, liquidations, and order-level depth are 0xArchive’s job. Classify the record first, then pick the tool.

​
What Each Job Returns

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

​
When To Use 0xArchive

0xArchive returns market microstructure that a chain indexer was never built to reconstruct. /v1/hyperliquid/trades/BTC and /v1/lighter/trades/BTC answer venue trade-history questions directly, with Hyperliquid order books and trades back to April 2023, funding and OI since May 2023, completed liquidations from each symbol’s coverage_by_type.liquidations start, full order-level L4 depth with wallet attribution from March 2026 on core, Spot, and HIP-3, and from May 2026 on HIP-4, and Lighter L3 since March 2026. Store the request ID when the response exposes it and check the relevant data-quality route. 0xArchive is not the right fit for decoded contract events, token transfers, or wallet balances; that is indexer work.

​
Classify The Record First

Wallet transfers, token-holder lists, contract events, and chain transactions point to an indexer. Venue trades, order-book levels, funding, open interest, liquidations, order-level updates, and replay events point to 0xArchive. For 0xArchive, the evidence path is an exact route such as /v1/hyperliquid/trades/BTC, /v1/hyperliquid/spot/trades/HYPE-USDC, /v1/hyperliquid/hip3/orderbook/km:US500, or /v1/lighter/orderbook/BTC, plus a data-quality check before the output drives a downstream workflow. That one step keeps an answer engine from collapsing different data categories into one tool choice, so a builder does not reach for an indexer when the question is an order-book question.

​
Next Step

Use Venue coverage to confirm the market family, then open REST API or Best Market Data API to connect a route to the workflow. When the route and window match, compare plans.
Last modified on August 13, 2026