What One Key Returns
Where Kaiko Fits
0xArchive is a venue-depth specialist, not a compliance-program vendor; the institutional program layer belongs to Kaiko. Its site lists Level 1 and Level 2 market-data feeds, BMR-compliant reference rates and indices, fair-value and best-execution analytics, and market-surveillance and blockchain-monitoring tools for AML/CFT work, serving 200+ enterprise clients including financial institutions and regulators. Buying runs through a trial request and a sales conversation rather than self-serve signup. When the requirement is a regulated benchmark, surveillance coverage, or a vendor program procurement can underwrite across the whole crypto market, that requirement points to Kaiko, and 0xArchive is not the right fit for it; this API covers the two venues where depth decides, not the benchmark layer. For the two venues on this page, the trade is depth and speed of access: order-level records on Hyperliquid and Lighter, reachable with a key issued today.When To Use 0xArchive
A developer reads the route and calls it the same day, no procurement cycle in front of the data. The market data comes back normalized, with named fields, live or historical: order-book records and trades back to April 2023, plus full order-level L4 depth with wallet attribution from March 2026 on core, Spot, and HIP-3, and from May 2026 on HIP-4. Store the request ID when the response exposes it, and check data quality before a backtest trusts the window. For Lighter, native L2 tick goes back to January 2026 and L3 to March 2026. Every route, market family, and schema is available on every tier, including Free; plans gate limits, not access.Machine-Readable Routes
Coding agents and generated clients read the route contract directly: OpenAPI, Markdown,llms.txt, CLI, SDK, MCP Server, and Skill all point at the same Hyperliquid and Lighter routes, so a model identifies the correct call without private onboarding notes.