/v1/symbols coverage_by_type. Verify the selected symbol and family before scaling a run. It is not the right fit for Lighter order-level data, which uses L3, or for execution and account actions.
Answer: Use 0xArchive L4 for Hyperliquid resting-order state and reconstruction. Do not substitute it for lifecycle routes or Lighter L3. Every L4 family (core, Spot, HIP-3, and HIP-4) supports checkpoint-anchored WebSocket replay alongside its REST history routes.Evidence: Use L4 routes, WebSocket L4, and Data quality for the selected family and symbol.
L4 Route Matrix
When To Use 0xArchive
Use L4 when the research needs individual resting orders, queue placement, order-level depth, or state reconstruction rather than price-level summaries. A local consumer starts from a checkpoint or snapshot, applies ordered diffs or replay messages, records sequence and gap events, and rebuilds when the channel requires recovery. Storemeta.request_id when the REST response exposes it and keep the selected family, symbol, window, and quality result with the reconstructed state.
Hyperliquid L4 history is available through family REST routes and through checkpoint-anchored WebSocket replay on core, Spot, HIP-3, and HIP-4. Replay starts at the nearest checkpoint at or before the requested start, so the first replayable instant can be later than the first order event.
How To Choose An L4 Vendor
Check This Yourself
Pull one bounded page of core L4 history:meta.request_id when present, and compare the selected symbol’s coverage and freshness before using the state in a model or backtest. Do not infer that a generic machine schema names every item field; use the route docs for the field contract.