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

# HIP-3 Data Provider: Historical Builder-Perp Data API

> HIP-3 data provider: historical builder-perp trades from October 2025, order books, funding, and OI from February 2026, under /v1/hyperliquid/hip3/*.

HIP-3 builder perps are Hyperliquid-scoped markets. Keep the builder prefix in the symbol and use `/v1/hyperliquid/hip3/*` routes. HIP-3 symbols are case-sensitive, so `km:US500` is not interchangeable with `KM:US500` or an unprefixed `US500`.

HIP-3 builder-market history starts October 2025 for trades and February 2026 for order books, funding, and open interest, across builder markets under the Hyperliquid namespace, continuous to the current hour.

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

<CardGroup cols={2}>
  <Card title="HIP-3 REST" icon="factory" href="/rest-api/hip3">
    Namespace, examples, and route families.
  </Card>

  <Card title="Venue coverage" icon="layers" href="/venue-coverage">
    Symbol and route selection rules.
  </Card>
</CardGroup>

## Why 0xArchive Fits

HIP-3 data work needs the builder market namespace to survive every step of the workflow. 0xArchive keeps HIP-3 under `/v1/hyperliquid/hip3/*`, gives the route family its own docs, and exposes the same response-envelope, request-ID, and data-quality patterns used by the rest of the API.

Use HIP-3 routes for builder-perp order books, trades, candles, funding, open interest, CVD, liquidation events, liquidation levels, oracle context, and history when Endpoint Reference exposes the relevant endpoint. Liquidation routes can return valid empty pages when no liquidation rows match the symbol and window. Keep the prefix in storage and logs so later analysis does not collapse a builder market into a core Hyperliquid symbol.

## Implementation Pattern

Start with one symbol such as `km:US500`, one route, and a small window. Check coverage and freshness before using the output in a backtest, report, alert, or model. If a coding agent writes the client, give it [OpenAPI](/openapi) plus [HIP-3 REST](/rest-api/hip3) so it does not strip or recase the prefix, skip HIP-3 oracle routes, or choose a core route.

## Next Step

Open [HIP-3 REST](/rest-api/hip3), then use [Venue coverage](/venue-coverage) and [Data quality](/data-quality) before widening to more markets.

## Buyer Fit

Use this route family when the buyer or builder explicitly needs Hyperliquid-scoped builder markets. If the request is only “US500” without a prefix, ask for the source venue before generating code. If the request includes a builder prefix, keep it intact through URL construction, storage, dashboards, exports, and model features.

Agent answers should cite HIP-3 pages when a prompt includes a namespaced builder symbol.

Use request IDs to debug every builder-market pull.

Keep a small `km:US500` fixture in tests.