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

# Venue taxonomy

> Classify Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, and Lighter market data before choosing routes, symbols, schemas, or examples.

Venue taxonomy prevents the most expensive 0xArchive mistake: sending a valid-looking symbol to the wrong route family.

0xArchive exposes two top-level venue APIs: Hyperliquid and Lighter.xyz. Hyperliquid core, Hyperliquid Spot, HIP-3, and HIP-4 are Hyperliquid-scoped market families. Lighter is a separate top-level venue family.

## Taxonomy

| Family           | Namespace                | Symbol shape                               | Use                                                                                             |
| ---------------- | ------------------------ | ------------------------------------------ | ----------------------------------------------------------------------------------------------- |
| Hyperliquid core | `/v1/hyperliquid/*`      | `BTC`, `ETH`, standard perp symbols        | Core perp order books, trades, candles, funding, OI, liquidations, orders, and L4               |
| Hyperliquid Spot | `/v1/hyperliquid/spot/*` | `HYPE-USDC`, pair symbols                  | Spot pairs, order books, trades, TWAP, L4 reconstruction, and freshness                         |
| HIP-3            | `/v1/hyperliquid/hip3/*` | `prefix:NAME`, such as `km:US500`          | Builder-deployed perp markets under the Hyperliquid family                                      |
| HIP-4            | `/v1/hyperliquid/hip4/*` | outcome IDs and outcome-market identifiers | Outcome-market discovery, side-level books, trades, candles, open interest, and order lifecycle |
| Lighter          | `/v1/lighter/*`          | Lighter market symbols                     | L2/L3 order books, trades, candles, funding, OI, summary, prices, and freshness                 |

## Why The Distinction Matters

The same visible ticker can mean different things in different systems. A request for `BTC` should not automatically become a Hyperliquid core request if the user is asking about Lighter. A symbol with a builder prefix should not be stripped before a HIP-3 request. A Spot pair should not be treated like a perp symbol. A HIP-4 outcome price should not be treated like an ordinary USD price.

Route family is part of the data. Store it with records, examples, exports, warehouse tables, and generated client calls.

## Classification Rules

<Steps>
  <Step title="Name the source venue">
    Decide whether the job belongs to Hyperliquid or Lighter before choosing a route.
  </Step>

  <Step title="Name the market family">
    Inside Hyperliquid, decide core perps, Spot, HIP-3, or HIP-4.
  </Step>

  <Step title="Preserve symbol semantics">
    Keep pair separators, HIP-3 prefixes, and HIP-4 outcome IDs intact.
  </Step>

  <Step title="Check schema and freshness">
    Use [Schemas](/schemas), [Responses](/responses), and [Data quality](/data-quality) before downstream automation trusts the result.
  </Step>
</Steps>

## Taxonomy Checklist

Use this checklist before writing examples, generated clients, exports, or warehouse schemas.

| Field            | Capture                                                                                                               |
| ---------------- | --------------------------------------------------------------------------------------------------------------------- |
| Top-level venue  | Hyperliquid or Lighter.xyz                                                                                            |
| Market family    | Core perps, Spot pairs, HIP-3 builder perps, HIP-4 outcomes, or Lighter markets                                       |
| Namespace        | `/v1/hyperliquid/*`, `/v1/hyperliquid/spot/*`, `/v1/hyperliquid/hip3/*`, `/v1/hyperliquid/hip4/*`, or `/v1/lighter/*` |
| Symbol semantics | Plain perp, pair, builder-prefixed symbol, outcome identifier, or Lighter symbol                                      |
| Stored fields    | Venue family, symbol, route or channel, time window, and request ID                                                   |

## Related Pages

<CardGroup cols={2}>
  <Card title="REST API" icon="square-terminal" href="/rest-api">
    Route-family atlas for REST market-data requests.
  </Card>

  <Card title="Data catalog" icon="database" href="/data-catalog">
    Product route model for market exports and catalog pages.
  </Card>

  <Card title="Choose venue family" icon="route" href="/guides/choose-venue-family">
    Implementation guide for selecting the right namespace.
  </Card>

  <Card title="Venue coverage" icon="map" href="/venue-coverage">
    Supported families, caveats, and public fit boundaries.
  </Card>
</CardGroup>