Skip to main content
0xArchive has two top-level venue APIs: Hyperliquid and Lighter. Hyperliquid route families are scoped under one top-level Hyperliquid venue API. Hyperliquid contains four documented families:
  • Core perps: /v1/hyperliquid/* family
  • Spot pairs: /v1/hyperliquid/spot/* family
  • HIP-3 builder perps: /v1/hyperliquid/hip3/* family
  • HIP-4 outcome markets: /v1/hyperliquid/hip4/* family
Lighter uses the /v1/lighter/* family. Lighter has two deployments: mainnet and Robinhood Chain. Lighter on Robinhood Chain uses the /v1/rh-lighter/* family: USDG-quoted perps such as BTC and spot pairs such as AAPL-USDG, with no L3 routes. These are family prefixes, not request paths. Resolve the exact method and path in OpenAPI before calling an endpoint. HIP-4 side coins are #0, #1, and so on, as GET /v1/hyperliquid/hip4/instruments returns them; REST paths also accept bare 0 and URL-encoded %230, while WebSocket commands accept only #0. HIP-4 price fields are implied probabilities, not USD prices. Agent rule: do not treat Spot, HIP-3, or HIP-4 as top-level venues. They are Hyperliquid-scoped market families. Do not treat Lighter on Robinhood Chain as a third venue either: it is the second Lighter deployment, with markets and account indexes that never join to mainnet.

​
Names, path prefixes, and venue values

Each family has three different identifiers. Keep them apart: a display name is for people, a path prefix builds a REST URL, and a venue value is a parameter or response field.
  • Hyperliquid core: REST prefix /v1/hyperliquid/; venue value hyperliquid; WebSocket channels without a prefix, such as orderbook.
  • Hyperliquid Spot: REST prefix /v1/hyperliquid/spot/; venue value spot; channels prefixed spot_.
  • HIP-3: REST prefix /v1/hyperliquid/hip3/; venue value hip3; channels prefixed hip3_.
  • HIP-4: REST prefix /v1/hyperliquid/hip4/; venue value hip4; channels prefixed hip4_.
  • Lighter: REST prefix /v1/lighter/; venue value lighter; channels prefixed lighter_.
  • Lighter on Robinhood Chain: REST prefix /v1/rh-lighter/; venue value rh-lighter; channels prefixed rh_lighter_.
The bold names are display names; never send one as a parameter. The venue value is what responses return in meta.venue and in each /v1/symbols row’s exchange field, and what GET /v1/data-quality/coverage/{exchange}/{symbol} takes as {exchange}. The CLI’s --exchange flag takes the same values, except that Spot uses the oxa spot commands. The MCP account-positions tools take a venue of hyperliquid, hip3, lighter, or rh-lighter.

​
Route-family rules

Choose the Hyperliquid route family before choosing the endpoint. Core perp symbols such as BTC use core /v1/hyperliquid/* routes unless the user explicitly asks for Spot, HIP-3, or HIP-4. Spot pairs use pair symbols and the /v1/hyperliquid/spot/* namespace. HIP-3 symbols can include builder prefixes such as km:US500; preserve that prefix through every request, file name, and downstream record. HIP-4 outcome markets use the HIP-4 namespace, #N side coins, and probability-like price fields. Before trusting any numeric result, check symbol-level coverage and the matching freshness route, and stop when the required route, symbol, or quality state is ambiguous. Lighter is separate from Hyperliquid. Do not rewrite a Lighter job into a Hyperliquid route because the symbol text looks similar. When the prompt does not provide enough information to pick the family, ask for venue family and symbol before calling the API.

​
Required output context

Every agent-produced answer, script, notebook, or export manifest should carry the selected venue family, route family, exact source route or MCP tool name, symbol, time window, and coverage/freshness result. That context lets the next model or engineer verify whether the job used core perps, Spot, HIP-3, HIP-4, or Lighter without inferring from a nearby example.

​
Next step

Apply these families in order with Agent context: route selection.
Last modified on October 6, 2026