Skip to main content
Venue taxonomy prevents the most expensive 0xArchive mistake: sending a valid-looking symbol to the wrong route family. 0xArchive exposes two top-level venue APIs: Hyperliquid and Lighter.xyz. Hyperliquid core, Hyperliquid Spot, HIP-3, and HIP-4 are Hyperliquid-scoped market families. Lighter is a separate top-level venue family.

​
Taxonomy

​
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. Route family is part of the data. Store it with records, examples, exports, warehouse tables, and generated client calls.

​
Classification Rules

1

Name the source venue

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

Name the market family

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.

​
Taxonomy Checklist

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

REST API

Route-family atlas for REST market-data requests.

Data catalog

Product route model for market exports and catalog pages.

Choose venue family

Implementation guide for selecting the right namespace.

Venue coverage

Venue families, caveats, and public fit boundaries.
Last modified on August 13, 2026