> ## 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 builder-perp market data under /v1/hyperliquid/hip3/*, with schema-specific trade, order-book, funding, OI, liquidation, oracle, and L4 routes.

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

Observed HIP-3 trade coverage across current symbol rows begins October 13, 2025, with exact starts varying by market. Native L2, funding, and open interest begin February 16, 2026; L4 coverage begins March 10, 2026 where the selected symbol exposes the relevant key. Funding rows are captured at roughly 10-second resolution. Use the selected symbol's coverage and freshness metadata for the exact window rather than inferring a venue-wide history.

```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>

## Route Scope

The current contract keeps builder-perp routes under `/v1/hyperliquid/hip3/*`. It includes order books, trades, candles, funding, open interest, CVD, liquidations, liquidation levels, oracle context, and order-history routes. A listed route does not establish non-empty coverage for every symbol; use the selected operation's coverage and freshness checks before relying on its window. Liquidation routes can return valid empty pages when no rows match the symbol and window.

## Implementation Pattern

For a builder-perp backtest, monitor, report, or generated client, 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. Keep the prefix in storage and logs. 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.

See the [Hyperliquid market data API](https://0xarchive.io/hyperliquid) for other data types.

Read the [HIP-3 L4 research workflow](https://0xarchive.io/resources/market-data-guides/hip3-l4-order-data) to analyze order-level data.

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

## Symbol Boundary

If the request is only `US500` without a prefix, identify the source venue before generating code. If it includes a builder prefix, keep it intact through URL construction, storage, dashboards, exports, and model features.


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