prefix:NAME, and returns every order, trade, and fill as normalized JSON. One key covers order books, trades, funding, open interest, liquidations, and full order-level (L4) depth across 124 to 221 symbols.
HIP-3 is a Hyperliquid-scoped market family in 0xArchive, served under /v1/hyperliquid/hip3. It is not a third peer venue next to Hyperliquid and Lighter, and 0xArchive does not strip or recase the prefix.
What One Key Returns
| HIP-3 need | 0xArchive path | What you get |
|---|---|---|
| Trades | /v1/hyperliquid/hip3/trades/km:US500 | Builder-perp tape since October 2025 |
| Order book and OI | /v1/hyperliquid/hip3/orderbook/km:US500/history, /v1/hyperliquid/hip3/openinterest/km:US500 | Book, funding, and OI since February 2026 |
| Order-level depth (L4) | /v1/hyperliquid/hip3/orderbook/km:US500/l4/history, /v1/hyperliquid/hip3/orders/km:US500/flow | Every add, fill, cancel, and TP/SL with wallet attribution since March 2026 |
| Funding | /v1/hyperliquid/hip3/funding/km:US500 | Since February 2026 |
| Liquidations | /v1/hyperliquid/hip3/liquidations/km:US500 | Builder-market liquidations as published |
| Freshness and coverage | /v1/hyperliquid/hip3/freshness/km:US500 | Per-symbol freshness state to gate a window |
Why Teams Choose 0xArchive
HIP-3 implementations break at the namespace. HIP-3 symbols are case-sensitive, and a source, agent, or buyer that drops the builder prefix from a symbol shaped likeprefix:NAME can silently point a backtest at the wrong market. 0xArchive keeps the prefix intact end to end, from the route to the response.
0xArchive returns each HIP-3 data family on its own route so coverage is explicit, not inferred from one successful endpoint. Order books, trades, funding, OI, liquidations, and L4 each have a route and a start date: trades since October 2025, book and OI since February 2026, and order-level depth with wallet attribution since March 2026. Liquidation routes can return valid empty pages, which is normal for a thin builder market and not an error to retry.
Every response carries a request ID and a freshness path you can check before the result feeds a backtest, agent workflow, export, or production job. Every order, trade, and fill. One API.
Run One Route
Evaluation Questions
Keep the builder prefix
Start with the exact symbol. HIP-3 symbols are case-sensitive, so preserve the
prefix:NAME form before generating any call.Confirm the data family
Check the route you need in HIP-3 REST: order books, trades, funding, OI, liquidations, and L4 each have their own start date.