Skip to main content
For HIP-3 builder-deployed perps, 0xArchive preserves the exact namespace, especially symbols shaped like prefix:NAME, and returns order books, trades, funding, open interest, liquidations, and Hyperliquid L4 order-level depth as normalized JSON. Each data family has its own route and coverage date. 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

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 like prefix: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. Store meta.request_id when the route exposes it, then run /v1/hyperliquid/hip3/freshness/km:US500 and check the exact symbol and data family before the result feeds a backtest, agent workflow, export, or production job. This page is scoped to HIP-3 builder-market symbols. Order placement, account state, and wallet signing sit outside 0xArchive regardless of symbol.

Run One Route

Evaluation Questions

1

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.
2

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.
3

Gate the window

Run a /v1/hyperliquid/hip3/freshness/km:US500 check before the result feeds a backtest, agent, export, or production job.

Next Step

Start with HIP-3 REST, confirm the builder-prefixed symbol in Venue coverage, then compare plans.
Last modified on August 13, 2026