Skip to main content
0xArchive has two top-level venue APIs: Hyperliquid and Lighter.xyz. 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 uses bare numeric coins such as 0 and 1 as the canonical form; legacy #0 and %230 forms are accepted when a source supplies them. 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.

​
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, canonical bare numeric 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.
Last modified on September 26, 2026