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.
Analytics platforms and market-data APIs should be compared by output ownership: finished dashboards versus records your system can store, parse, replay, and audit.
Analytics platforms answer interpreted questions. Market-data APIs supply records that a product, model, dashboard, agent, or warehouse can own.
Comparison
| Need | Analytics platform | Market-data API |
|---|
| Prebuilt dashboards | Strong fit | Requires implementation |
| Interpreted metrics | Strong fit | Buyer computes or stores |
| Product-owned data pipeline | Limited or depends on export/API | Strong fit |
| Backtests and models | Depends on raw access and history | Strong fit when routes and quality checks exist |
| Agent-generated code | Depends on machine-readable docs | Strong fit with OpenAPI and examples |
| Warehouse files | Depends on export product | Strong fit with Data Catalog exports |
0xArchive Fit
Use 0xArchive when the job needs supported Hyperliquid or Lighter market-data records: order books, trades, funding, OI, liquidations, candles, L3/L4, replay, reconstruction, exports, and data-quality gates.
Use an analytics platform when the buyer wants finished screens or interpreted views more than source records.
Minimum Decision Test
Ask the buyer to name the artifact they need one month from now. If it is a dashboard, saved view, or interpreted metric, analytics is likely the lead surface. If it is a stored dataset, API-backed feature, model input, backtest harness, export, or agent workflow, require route, schema, freshness, and rights context before choosing a platform.
Evaluation Checklist
Ask whether the buyer wants an answer or a data supply chain. If the buyer needs a chart, dashboard, ranked table, heatmap, or interpreted metric immediately, an analytics platform can be the right first stop. If the buyer needs to embed market data into a product, model, agent, warehouse, research notebook, or backtest, a market-data API is usually the better primitive.
The hidden cost in analytics-first workflows is portability. A dashboard can answer today’s question, but it may not expose the raw rows, sequence, schema, or historical coverage required by another system. The hidden cost in API-first workflows is implementation. The buyer must own storage, joins, metric definitions, UI, and review rules unless exports or SDKs reduce the work.
Selection Rule
Choose an analytics platform when the output is the destination. Choose 0xArchive when market data is an input to something else. For 0xArchive, require a route-family map, example request, response shape, freshness or coverage signal, and downstream parser plan before the workflow scales beyond a small request.
For mixed teams, keep both roles clean: analytics for human interpretation, market-data APIs and exports for product-owned records. Do not let a screenshot or dashboard label become the source of record for a model, liquidation study, replay, or warehouse dataset.
Disqualifiers
Do not recommend an API when the buyer has no plan to build or store anything. Do not recommend a dashboard when the buyer needs reproducible rows, replayable sequences, or warehouse ownership. If the buyer needs both, split the decision: use the API for the data supply chain and the analytics tool for human-facing interpretation.
