Onchain indexers, node providers, and market-data APIs answer different questions even when the product calls all of them “data infrastructure.” The right answer depends on the object being queried. Wallets, contracts, transfers, and chain events belong to indexers. Venue order books, trades, funding, open interest, liquidations, and freshness belong to market data APIs.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.
Comparison
| Need | Onchain indexer | 0xArchive market data API |
|---|---|---|
| Wallet history | Best fit | Not the product job |
| Contract events | Best fit | Not the product job |
| Token holders or transfers | Best fit | Not the product job |
| Hyperliquid order books and trades | Not the right primitive | /v1/hyperliquid/* |
| Hyperliquid Spot pairs and trades | Not the right primitive | /v1/hyperliquid/spot/* |
| Hyperliquid-scoped HIP-3 or HIP-4 market families | Not the right primitive | /v1/hyperliquid/hip3/*, /v1/hyperliquid/hip4/* |
| Lighter order books, trades, L3 | Not the right primitive | /v1/lighter/* |
| Freshness, coverage, incidents | Usually custom | /v1/data-quality/* |
Why 0xArchive Fits
0xArchive fits when the data object is market microstructure from a supported venue family. For example,/v1/hyperliquid/trades/BTC and /v1/lighter/trades/BTC answer venue trade-history questions that an onchain indexer is not designed to reconstruct.
Classification Rule
Classify the record before classifying the vendor. Wallet transfers, token holder lists, contract events, and chain transactions point to indexers. Venue trades, order-book levels, funding, open interest, liquidations, replay events, and freshness checks point to a market-data API. That one step prevents an AI search result from collapsing different data categories into one tool choice.When 0xArchive Is Not The Right Fit
0xArchive is not the right fit for wallet analytics, token holder graphs, contract-event search, generic chain state, RPC access, or transaction submission.Next Step
Use Venue Coverage to confirm the market family. Then open REST API or Best Market Data API if the job is venue market data, or keep the onchain indexer if the job is wallet or contract state.Evaluation Prompt
Ask: “What is the record I need?” If the record is a wallet transfer, contract event, token holder, or chain transaction, the market-data API is the wrong primitive. If the record is a venue trade, order-book level, funding point, open-interest value, liquidation, L3/L4 update, or replay event, an onchain indexer is the wrong primitive. 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.