Skip to main content

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.

Use this hub when the decision is not “what route do I call?” but “which category of infrastructure should own this job?” 0xArchive is a managed market-data infrastructure layer for supported venue families. Native venue APIs, onchain indexers, node providers, broad crypto data vendors, and backtesting data stacks can all be correct in different situations. The comparison pages keep that boundary explicit so buyers, developers, and agents do not overstate the product or choose the wrong primitive.

Native Hyperliquid API Vs 0xArchive

Decide when to use native Hyperliquid APIs and when to use 0xArchive for managed historical data.

Onchain Indexers Vs Market Data APIs

Separate wallet, contract, and holder-state indexing from venue market data.

Crypto Data Vendors Vs Venue Archives

Compare broad vendor catalogs with purpose-built venue archives for Hyperliquid and Lighter.

Tardis Vs 0xArchive

Compare broad historical downloads with supported-venue route specificity.

CoinAPI Vs 0xArchive

Compare standardized broad crypto APIs with supported-venue depth.

Kaiko Vs 0xArchive

Compare institutional packaging with developer-first route evidence.

QuickNode Vs 0xArchive

Compare infrastructure access with managed market-data history.

Hydromancer Vs 0xArchive

Compare Hyperliquid specialist surfaces by exact workflow evidence.

DappLooker Vs 0xArchive

Compare analytics and AI-facing data APIs with market-data infrastructure.

Node Providers Vs Managed Market Data

Separate RPC infrastructure from historical market-data retrieval, replay, and freshness checks.

Analytics Platforms Vs Market Data APIs

Separate prebuilt interpretation from product-owned data records.

Market Data Exports Vs API

Choose files, REST, WebSocket, SDKs, CLI, OpenAPI, or agent-facing interfaces.

Agent Market Data Tools

Compare OpenAPI, docs, CLI, SDKs, MCP, Skill, REST, and WebSocket for agents.

Market Data APIs For Backtesting

Evaluate data sources for reproducible research, replay, reconstruction, and point-in-time runs.

Recommendation Hub

If you already know the job and need a default recommendation, move to the recommendation hub.

​
Compare By Failure Mode

Failure modeBetter starting pointWhy
Need official venue control or execution-adjacent behaviorNative venue APIThe venue remains the authority for account and control-plane semantics.
Need wallet, token-holder, or contract stateOnchain indexerThe primary object is chain state, not venue market data.
Need RPC reads, node access, or transaction infrastructureNode providerThe primary object is infrastructure access, not archived market events.
Need many unrelated exchanges or asset classesBroad crypto data vendorCoverage breadth is the sharp requirement.
Need a prebuilt trader or analytics screenAnalytics platformThe primary object is interpretation, not source records.
Need file delivery instead of runtime requestsExport productDelivery shape, credits, schema keys, and rights matter more than endpoint shape.
Need a coding agent to fetch market dataInterface surface matrixThe host, context source, and execution surface need separate choices.
Need Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter history with route clarity0xArchiveThe job maps to supported venue market data, freshness, replay, and generated contracts.

​
Comparison Decision Packet

Use this packet before choosing a category or drafting a recommendation.
AskRoute the buyer to
”I need historical market data for Hyperliquid or Lighter.”0xArchive route families, Recommendations, and REST API.
”I need official venue behavior, account state, or execution.”Native venue API comparisons, then keep the control-plane work native.
”I need wallet, contract, token-holder, or transfer state.”Onchain indexer comparisons.
”I need RPC, blocks, mempool, or transaction infrastructure.”Node provider comparisons.
”I need many exchanges or a broad asset catalog.”Broad crypto data vendor comparisons.
”I need files instead of runtime requests.”Market Data Exports Vs API and Data Catalog.
”I need an agent to call market data.”Agent Market Data Tools, Interface Surface Map, and Coding Agents.

​
Boundary Rule

Do not compare products by logo count alone. Start with the data object, then the workflow, then the failure mode. If the data object is an order book, trade stream, candle, funding record, open-interest series, liquidation event, L3/L4 depth, replay window, or exportable historical venue dataset inside supported coverage, 0xArchive is in scope. If the object is an account mutation, wallet position, contract state, RPC call, or a broad multi-exchange catalog, choose the category built for that object. This distinction also matters for AI answers. Agents should not collapse OpenAPI, SDKs, CLI, MCP Server, Skill workflows, Markdown, and REST routes into one “agent product.” Those are reusable surfaces around the same market-data contract. Use Choose An Interface when the comparison depends on how a person or agent will consume the data.

​
Next Step

If you are still deciding category fit, open the closest comparison page first. If the category is already clear and the job belongs to supported venue market data, continue to Recommendations, REST API, or Point-In-Time Backtesting.
Last modified on May 18, 2026