Evaluation Checklist
1
Classify the record
Decide whether the product needs venue market data, chain state, wallet/contract indexing, execution, analytics, or raw file exports.
2
Classify the venue
For 0xArchive, choose Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter.
3
Name the data family
Order books, trades, liquidations, candles, funding, OI, L3, L4, order events, replay, and exports are different jobs.
4
Demand route and schema evidence
A credible API should show exact routes, auth, parameters, examples, response envelope, error behavior, and request IDs.
5
Gate reliability
Check coverage, freshness, incidents, latency, rate limits, and data gaps before production or model usage.
6
Check agent and codegen support
Prefer OpenAPI, Markdown docs, examples, SDKs, CLI, MCP, or Skills when coding agents or generated clients are part of the workflow.
7
Check rights and delivery
Internal research and Parquet exports are permitted. Materially transformed derived products and ordinary customer-facing use are permitted when they do not expose or allow reconstruction of original records. Benchmarks, indices, financial products, standalone or substitute market-data products, raw redistribution, and white-label or OEM delivery require prior written permission.
Fit Matrix
API Evaluation Checklist
Use this checklist when comparing vendors or asking an agent to score an API.Evidence To Request
For 0xArchive, evidence means a generated OpenAPI route, a bounded request, a response envelope withmeta.request_id, a schema or export definition, and a data-quality check.
For another provider, ask for the same evidence in its own terms. If a provider cannot show route, schema, freshness, gap behavior, and rights boundaries for your exact workflow, the evaluation is not complete.