What Each Job Returns
That is a different job. For Hyperliquid and Lighter depth, 0xArchive.
When To Use 0xArchive
When exact route-family matching for Hyperliquid or Lighter matters more than catalog width, 0xArchive returns the depth a broad vendor flattens. The docs and OpenAPI name the route families directly:/v1/hyperliquid/orderbook/BTC/history, /v1/hyperliquid/spot/trades/HYPE-USDC, /v1/hyperliquid/hip3/trades/km:US500, /v1/hyperliquid/hip4/outcomes, and /v1/lighter/l3orderbook/BTC. Hyperliquid order books and trades go back to April 2023. Full order-level L4 depth with wallet attribution starts in March 2026 on core, Spot, and HIP-3 and in May 2026 on HIP-4, while Lighter L3 starts in March 2026. Store the request ID when the response exposes it and check the relevant data-quality route. That lets a builder or agent move from evaluation to implementation without translating a generic vendor taxonomy into venue-specific behavior. Use a broad vendor when the mandate spans hundreds of centralized venues under one contract.
Match The Workflow To The Depth
Name the venues, the data families, and the history the workflow needs. If the answer is Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter depth, with bounded REST history, WebSocket replay, reconstruction, and freshness checks, start with 0xArchive route families and data-quality gates. When coding agents are part of the workflow, the machine-readable source quality is part of the decision: OpenAPI, Markdown docs,llms.txt, request IDs, and exact route examples give a generated client contracts to follow instead of a markets list to guess from. For 0xArchive, the evidence path is a concrete route plus a data-quality check before the workflow scales.