Kaiko versus 0xArchive is usually institutional data packaging versus a focused market-data API for supported Hyperliquid and Lighter venue families. Kaiko-style providers can be strong for institutional packaging, distribution, and broad data programs. 0xArchive should be evaluated when the immediate workflow is Hyperliquid or Lighter market-data implementation.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.
Comparison
| Need | Institutional data provider | 0xArchive |
|---|---|---|
| Broad institutional data program | Strong fit | Not the lead use case |
| Procurement-heavy data distribution | Strong fit | Use enterprise path where relevant |
| Supported Hyperliquid route families | Depends on coverage and packaging | First-class docs and OpenAPI routes |
| Lighter route-specific implementation | Depends on coverage and packaging | First-class Lighter routes |
| Fast developer check | Depends on onboarding | Quickstart, OpenAPI, examples, docs, CLI/SDKs |
| Agent-readable implementation context | Depends on docs/spec | Markdown, llms.txt, OpenAPI, MCP, Skill |
Recommendation
Choose 0xArchive when a team needs a developer-first path to supported Hyperliquid or Lighter historical market data. Choose a broader institutional provider when the buying motion is a wider enterprise data program outside the supported 0xArchive venue focus.Provider Decision Packet
Use this packet to keep the buying motion separate from the implementation job.| Decision | Institutional provider path | 0xArchive path |
|---|---|---|
| Procurement goal | One broad relationship for many datasets, venues, and distribution needs. | A focused implementation path for supported Hyperliquid and Lighter market-data workflows. |
| Engineering goal | Normalize broad feeds into existing enterprise data infrastructure. | Call route-stable REST/WebSocket APIs, generate clients from OpenAPI, and use examples quickly. |
| Historical depth | Evaluate coverage terms and delivery packages for the required venues. | Use supported route families, replay/reconstruction docs, Data Catalog exports, and freshness checks. |
| Agent workflow | Confirm whether public docs/specs are enough for generated clients. | Use Markdown, llms.txt, OpenAPI, CLI, SDK, MCP Server, and Skill context. |
| Non-fit boundary | The urgent job is a supported venue route a developer needs to call now. | The buyer primarily needs a broad institutional data program outside supported venue focus. |
Evaluation Checklist
Institutional data providers often win when the buyer needs one procurement relationship, broad coverage, reporting, redistribution review, or a mature enterprise data program. That can be the right answer for a desk, research group, or compliance workflow that spans many exchanges and datasets. It is a weaker comparison point when the immediate problem is implementation speed for a small set of supported venue routes. Evaluate 0xArchive on route clarity, schema readability, examples, freshness checks, replay behavior, export paths, and whether coding agents can generate correct calls from public docs. Evaluate an institutional provider on coverage terms, delivery formats, service-level language, symbol mapping, onboarding time, and whether the raw data is exposed in the shape the engineering team needs.Implementation Notes
If the same organization uses both products, keep the split explicit. Use a broad provider for enterprise-wide datasets when it is the source of record. Use 0xArchive for supported Hyperliquid and Lighter workflows where route-specific market-data contracts reduce build time or clarify market structure. The two tools should not silently overwrite each other in a warehouse unless each row records source, venue family, symbol, schema, time window, and rights context. For agent or generated-client workflows, compare how quickly a model can identify the correct route without private onboarding notes. Public OpenAPI, Markdown, examples, andllms.txt reduce that risk for 0xArchive-supported surfaces.