Skip to main content
Start with the venue, then choose the market type. This prevents a valid-looking symbol from being sent to the wrong API namespace. 0xArchive covers two venues: Hyperliquid and Lighter. Hyperliquid includes core perpetuals, Spot, HIP-3 builder perpetuals, and HIP-4 outcomes. Lighter uses its own namespace and market types.

​
Market types and API namespaces

​
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. Store the venue, market type, and API namespace with records, examples, exports, warehouse tables, and generated client calls.

​
Classification rules

1

Name the venue

Decide whether the job belongs to Hyperliquid or Lighter before choosing a route.
2

Choose the market type

Inside Hyperliquid, decide core perps, Spot, HIP-3, or HIP-4.
3

Preserve symbol semantics

Keep pair separators, HIP-3 prefixes, and HIP-4 outcome IDs intact.
4

Check schema and freshness

Use Schemas, Responses, and Data quality before downstream automation trusts the result.

​
Request checklist

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

REST API

Choose the API namespace and REST endpoint for a request.

Data catalog

Choose a market, data types, and dates for a Parquet export.

Choose venue and market type

Select one namespace and make a bounded request.

Venue coverage

Available data types and observed history by market type.
Last modified on September 3, 2026