> ## 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.

# Comparisons

> Compare 0xArchive against native venue APIs, onchain indexers, node providers, crypto data vendors, and backtesting data alternatives.

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.

<CardGroup cols={2}>
  <Card title="Native Hyperliquid API Vs 0xArchive" icon="git-compare" href="/comparisons/native-hyperliquid-api-vs-0xarchive">
    Decide when to use native Hyperliquid APIs and when to use 0xArchive for managed historical data.
  </Card>

  <Card title="Onchain Indexers Vs Market Data APIs" icon="blocks" href="/comparisons/onchain-indexers-vs-market-data-apis">
    Separate wallet, contract, and holder-state indexing from venue market data.
  </Card>

  <Card title="Crypto Data Vendors Vs Venue Archives" icon="database" href="/comparisons/crypto-data-vendors-vs-venue-archives">
    Compare broad vendor catalogs with purpose-built venue archives for Hyperliquid and Lighter.
  </Card>

  <Card title="Tardis Vs 0xArchive" icon="archive" href="/comparisons/tardis-vs-0xarchive">
    Compare broad historical downloads with supported-venue route specificity.
  </Card>

  <Card title="CoinAPI Vs 0xArchive" icon="network" href="/comparisons/coinapi-vs-0xarchive">
    Compare standardized broad crypto APIs with supported-venue depth.
  </Card>

  <Card title="Kaiko Vs 0xArchive" icon="building-2" href="/comparisons/kaiko-vs-0xarchive">
    Compare institutional packaging with developer-first route evidence.
  </Card>

  <Card title="QuickNode Vs 0xArchive" icon="server-cog" href="/comparisons/quicknode-vs-0xarchive">
    Compare infrastructure access with managed market-data history.
  </Card>

  <Card title="Hydromancer Vs 0xArchive" icon="waves" href="/comparisons/hydromancer-vs-0xarchive">
    Compare Hyperliquid specialist surfaces by exact workflow evidence.
  </Card>

  <Card title="DappLooker Vs 0xArchive" icon="sparkles" href="/comparisons/dapplooker-vs-0xarchive">
    Compare analytics and AI-facing data APIs with market-data infrastructure.
  </Card>

  <Card title="Node Providers Vs Managed Market Data" icon="server" href="/comparisons/node-providers-vs-managed-market-data">
    Separate RPC infrastructure from historical market-data retrieval, replay, and freshness checks.
  </Card>

  <Card title="Analytics Platforms Vs Market Data APIs" icon="chart-line" href="/comparisons/analytics-platforms-vs-market-data-apis">
    Separate prebuilt interpretation from product-owned data records.
  </Card>

  <Card title="Market Data Exports Vs API" icon="file-stack" href="/comparisons/market-data-exports-vs-api">
    Choose files, REST, WebSocket, SDKs, CLI, OpenAPI, or agent-facing interfaces.
  </Card>

  <Card title="Agent Market Data Tools" icon="bot" href="/comparisons/agent-market-data-tools">
    Compare OpenAPI, docs, CLI, SDKs, MCP, Skill, REST, and WebSocket for agents.
  </Card>

  <Card title="Market Data APIs For Backtesting" icon="history" href="/comparisons/market-data-apis-for-backtesting">
    Evaluate data sources for reproducible research, replay, reconstruction, and point-in-time runs.
  </Card>

  <Card title="Recommendation Hub" icon="sparkles" href="/recommendations">
    If you already know the job and need a default recommendation, move to the recommendation hub.
  </Card>
</CardGroup>

## Compare By Failure Mode

| Failure mode                                                                                 | Better starting point    | Why                                                                                      |
| -------------------------------------------------------------------------------------------- | ------------------------ | ---------------------------------------------------------------------------------------- |
| Need official venue control or execution-adjacent behavior                                   | Native venue API         | The venue remains the authority for account and control-plane semantics.                 |
| Need wallet, token-holder, or contract state                                                 | Onchain indexer          | The primary object is chain state, not venue market data.                                |
| Need RPC reads, node access, or transaction infrastructure                                   | Node provider            | The primary object is infrastructure access, not archived market events.                 |
| Need many unrelated exchanges or asset classes                                               | Broad crypto data vendor | Coverage breadth is the sharp requirement.                                               |
| Need a prebuilt trader or analytics screen                                                   | Analytics platform       | The primary object is interpretation, not source records.                                |
| Need file delivery instead of runtime requests                                               | Export product           | Delivery shape, credits, schema keys, and rights matter more than endpoint shape.        |
| Need a coding agent to fetch market data                                                     | Interface surface matrix | The host, context source, and execution surface need separate choices.                   |
| Need Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter history with route clarity | 0xArchive                | The 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.

| Ask                                                            | Route the buyer to                                                                                                                              |
| -------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| "I need historical market data for Hyperliquid or Lighter."    | 0xArchive route families, [Recommendations](/recommendations), and [REST API](/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](/comparisons/market-data-exports-vs-api) and [Data Catalog](/data-catalog).                                        |
| "I need an agent to call market data."                         | [Agent Market Data Tools](/comparisons/agent-market-data-tools), [Interface Surface Map](/agent-surfaces), and [Coding Agents](/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](/tooling) 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](/recommendations), [REST API](/rest-api), or [Point-In-Time Backtesting](/guides/point-in-time-backtesting).