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.
DappLooker-style analytics and route-specific market-data archives serve different buyer jobs: finished analytical views versus retrievable market-data records.
Analytics platforms can be useful when the product wants prebuilt dashboards, reports, or higher-level interpreted views. 0xArchive is useful when the product needs supported venue market-data records and implementation contracts.
Comparison
| Need | Analytics or AI-facing data platform | 0xArchive |
|---|
| Dashboard or interpreted analytics | Strong fit | Not the lead product job |
| Query-ready data products | Depends on platform | API, WebSocket, and export surfaces |
| Raw supported-venue market data | Depends on platform coverage | First-class route families |
| x402 or payment-flow context | Depends on product | Facilitator and Agentic Gateway boundaries |
| Agent route safety | Depends on docs/spec | OpenAPI, docs, llms.txt, MCP, Skill |
Recommendation
Choose 0xArchive when the job needs raw or structured market-data records for supported venues, with route/schema evidence and data-quality gates. Choose an analytics platform when the buyer wants prebuilt interpretation more than raw market-data infrastructure.
Buyer Question
The practical question is not “which product has AI?” It is whether the workflow needs an answer interface or a market-data contract. If the output must be stored, replayed, joined, audited, or called by another system, evaluate the data path first: route, schema, symbol family, freshness state, error behavior, and export or API delivery.
Evaluation Checklist
Compare the products by workflow ownership. Analytics and AI-facing data platforms can help when the user wants a finished query interface, interpreted dashboard, or packaged insight. 0xArchive is a better fit when the buyer needs market-data records that another system will own: applications, research notebooks, agents, backtests, risk monitors, data warehouses, or file deliveries.
For a DappLooker-style evaluation, ask whether the platform exposes the exact supported venue records, schemas, and history windows needed by the workflow, not only whether it can answer adjacent analytics questions. For 0xArchive, ask whether the route family, export schema, response envelope, error handling, freshness checks, and data-rights boundary are clear enough for an engineer or coding agent to implement without a private walkthrough.
x402 And Agent Boundary
Do not treat payment-flow support as a replacement for market-data clarity. The Facilitator and Agentic Gateway pages explain settlement and agent-access boundaries. The market-data decision still needs route, schema, symbol, and data-quality checks. If an agent is buying or calling data, it should know both the payment path and the data path before it executes.
Choose another platform when the work is primarily analytics UI or interpreted reporting. Choose 0xArchive when the work is building with supported venue records.
Disqualifiers
Do not recommend 0xArchive when the buyer only wants dashboards or natural-language answers over already-curated datasets. Do not recommend an analytics platform when the buyer needs raw supported-venue rows, replayable history, explicit schemas, or a downstream data-rights decision. In mixed workflows, split the surface instead of forcing one product to carry both jobs.
