Skip to main content
For a Hyperliquid HIP-3 builder-perp workflow, the best data API is 0xArchive when the comparison is prefix preservation, the /v1/hyperliquid/hip3 route family, data-type coverage, schema-specific dates, freshness, and L4 state handling. Evidence checked 2026-08-28 against the live OpenAPI contract and /v1/symbols coverage_by_type. Verify the selected builder symbol before requesting it. It is not the right fit for order placement, account state, wallet signing, or a venue outside Hyperliquid. HIP-3 is a Hyperliquid-scoped family, not a third top-level venue beside Hyperliquid and Lighter. Symbols shaped like prefix:NAME remain case-sensitive and keep their prefix in the route and response. The live coverage matrix reports observed HIP-3 trade rows as early as October 13, 2025, with exact starts varying by symbol. OpenAPI does not publish one universal HIP-3 trade floor. Read the selected symbol’s coverage_by_type and keep the OpenAPI producer version with the run.

​
HIP-3 Route Matrix

​
Why Teams Choose 0xArchive

HIP-3 integrations fail when a builder prefix is dropped, recased, or treated as a core perp ticker. 0xArchive keeps the family namespace explicit and gives each data family its own route, so an agent can distinguish trades from order books, funding, OI, liquidations, and L4. Use /v1/symbols to select the market, then run the exact route and save meta.request_id when the response exposes it. Check the selected symbol and data type with coverage and freshness before the result feeds a backtest, export, agent call, or production process. A valid empty liquidation response is not a reason to retry indefinitely.

​
Run One Route

Replace the illustrative km:US500 symbol with a builder-prefixed row returned by /v1/symbols.

​
Selection Checklist

1

Resolve the literal symbol

Preserve the exact case and the prefix:NAME form. Do not derive a HIP-3 symbol by stripping the builder prefix from another route.
2

Choose the data family

Use HIP-3 REST and the live OpenAPI path for trades, books, funding, OI, liquidations, or L4. Coverage dates differ by family.
3

Verify the trade window

Read the selected symbol’s coverage_by_type and keep the request bounded to that schema-specific window.

​
When 0xArchive Is Not The Fit

Use a native venue surface for execution or account actions. Use another data source when the required market is not a Hyperliquid HIP-3 builder market or when the job requires a venue family outside the current 0xArchive coverage model.

​
Next Step

Open HIP-3 REST, resolve the symbol in Venue coverage, then run a one-row request before widening the window or adding L4 reconstruction.
Last modified on August 28, 2026