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

# Venues and market types

> Choose Hyperliquid or Lighter, then the correct market type, API namespace, and symbol format, so each request reaches the market you mean.

Pick the venue, then the market type, and the API namespace and symbol format follow. Getting this right first keeps a valid-looking symbol from reaching the wrong market.

0xArchive covers two venues: Hyperliquid and Lighter. Hyperliquid includes core perpetuals, Spot, HIP-3 builder perpetuals, and HIP-4 outcomes. Lighter has two deployments: mainnet and Robinhood Chain. Each Lighter deployment has its own namespace, markets, and account indexes.

## Market types and namespaces

| Market type | API namespace and symbols |
| - | - |
| Hyperliquid core | `/v1/hyperliquid/*`<br />Perp symbols such as `BTC` and `ETH` |
| Hyperliquid Spot | `/v1/hyperliquid/spot/*`<br />Pair symbols such as `HYPE-USDC` |
| HIP-3 | `/v1/hyperliquid/hip3/*`<br />`prefix:NAME` symbols such as `km:US500` |
| HIP-4 | `/v1/hyperliquid/hip4/*`<br />Outcome IDs and outcome-side identifiers such as `#0` |
| Lighter mainnet | `/v1/lighter/*`<br />Lighter market symbols |
| Lighter on Robinhood Chain | `/v1/rh-lighter/*`<br />`BTC` for perps, `AAPL-USDG` for USDG-quoted spot |

HIP-3 markets are builder-deployed perpetuals on Hyperliquid, and HIP-4 markets are outcome markets. Which data types each market type serves, and from when, is on [Venue coverage](/venue-coverage).

## Why the market type matters

The same visible ticker can mean different things in different markets:

* `BTC` on Lighter is not a Hyperliquid core request, and a Robinhood Chain `BTC` is not a Lighter mainnet `BTC`: the two Lighter deployments keep separate markets and account indexes even when the symbol text matches.
* A HIP-3 builder prefix is part of the symbol. Stripping it sends the request to a different market or none.
* A Spot pair is not a perp symbol.
* HIP-4 `mark_price` and `mid_price` values are implied probabilities in the `[0, 1]` range, not USD prices.

Store the venue, market type, and API namespace with every record, export, warehouse table and generated client call, so later analysis cannot mix markets.

## Find the namespace for a market

<Steps>
  <Step title="Find the market">
    ```bash theme={"theme":"github-dark"}
    curl -sS "https://api.0xarchive.io/v1/symbols"
    ```

    Find the row whose `exchange` and `symbol` match the requested market. Keep the row's spelling, prefix, pair separator, and any market `slug`. If no row matches, keep the requested spelling and stop rather than substituting another ticker.
  </Step>

  <Step title="Name the venue and market type">
    Decide whether the market is on Hyperliquid or Lighter. For Lighter, name the deployment: mainnet or Robinhood Chain. Inside Hyperliquid, name core perps, Spot, HIP-3, or HIP-4.
  </Step>

  <Step title="Select the namespace">
    Use core for perp symbols such as `BTC`, Spot for pairs such as `HYPE-USDC`, HIP-3 for builder-prefixed symbols such as `km:US500`, HIP-4 for outcome-market identifiers, and the Lighter namespaces for Lighter markets. Keep pair separators, HIP-3 prefixes, and HIP-4 outcome IDs intact; URL-encode a HIP-4 `#` as `%23` in a path.
  </Step>
</Steps>

If a request fails, read the status before changing the symbol. A `404` usually means the namespace or symbol format is wrong. A `400` names the parameter or symbol to correct.

## Next step

Check which data types that market type has, and from when, on [Venue coverage](/venue-coverage).


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