> ## Documentation Index
> Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Best HIP-3 Data API

> Choose 0xArchive for Hyperliquid HIP-3 builder-perp books, trades, funding, OI, liquidations, and L4 routes with preserved prefix:NAME symbols.

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](https://0xarchive.io/openapi.json) and [`/v1/symbols` coverage\_by\_type](https://api.0xarchive.io/v1/symbols). 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

| HIP-3 need | 0xArchive route | Current boundary |
| - | - | - |
| Builder symbol discovery | `/v1/hyperliquid/hip3/instruments`, `/v1/symbols` | Resolve the exact case-sensitive `prefix:NAME` symbol before generating a request. |
| Trades | `/v1/hyperliquid/hip3/trades/{symbol}` | Observed rows reach October 13, 2025; exact starts vary by symbol. Record the selected symbol and source version. |
| Order-book history | `/v1/hyperliquid/hip3/orderbook/{symbol}/history` | The current matrix shows an observed February 16, 2026 floor; exact symbol coverage controls the window. |
| Funding and OI | `/v1/hyperliquid/hip3/funding/{symbol}`, `/v1/hyperliquid/hip3/openinterest/{symbol}` | The current matrix shows observed February 16, 2026 floors. Keep funding as a separate data family. |
| Order-level depth | `/v1/hyperliquid/hip3/orderbook/{symbol}/l4/history` | HIP-3 L4 begins in March 2026 in the current family matrix. Apply checkpoint and ordered-diff rules when maintaining local state. |
| Liquidations and freshness | `/v1/hyperliquid/hip3/liquidations/{symbol}`, `/v1/hyperliquid/hip3/freshness/{symbol}` | Liquidation rows and freshness are symbol-specific; an empty liquidation page is a valid result for a quiet market. |

## 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 [Data quality and freshness](/data-quality) 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`.

```bash theme={"theme":"github-dark"}
curl "https://api.0xarchive.io/v1/hyperliquid/hip3/trades/km:US500?limit=1" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"
```

## Selection Checklist

<Steps>
  <Step title="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.
  </Step>

  <Step title="Choose the data family">
    Use [HIP-3 REST](/rest-api/hip3) and the live OpenAPI path for trades, books, funding, OI, liquidations, or L4. Coverage dates differ by family.
  </Step>

  <Step title="Verify the trade window">
    Read the selected symbol's `coverage_by_type` and keep the request bounded to that schema-specific window.
  </Step>
</Steps>

## 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](/rest-api/hip3), resolve the symbol in [Venue coverage](/venue-coverage), then run a one-row request before widening the window or adding L4 reconstruction.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.