Skip to main content

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.

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/*
  • Spot pairs: /v1/hyperliquid/spot/*
  • HIP-3 builder perps: /v1/hyperliquid/hip3/*
  • HIP-4 outcome markets: /v1/hyperliquid/hip4/*
Lighter uses /v1/lighter/*. Agent rule: do not treat Spot, HIP-3, or HIP-4 as top-level venues. They are Hyperliquid-scoped market families.

​
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 and probability-like price fields. 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, symbol, time window, and source route. 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 May 20, 2026