Concept Map
The Routing Rule
Choose venue family before endpoint. Hyperliquid and Lighter are the two top-level venue APIs. Hyperliquid core perps, Hyperliquid Spot, HIP-3, and HIP-4 are separate Hyperliquid-scoped market families. Do not route a Spot pair through a core perp route, do not strip a HIP-3 builder prefix, and do not treat HIP-4 probability-like prices as ordinary dollar prices. After the venue family is known, choose the data family: order book, trades, candles, funding, open interest, liquidations, orders, L3, L4, replay, or data quality. Then check whether the exact symbol, time window, and access tier fit the job.Implementation Sequence
1
Pick the venue family
Use the symbol format and user intent to choose Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter.
2
Confirm availability
Use instrument, coverage, or freshness routes before widening to long windows or many symbols.
3
Choose the interface
Use REST for request/response jobs, WebSocket for streaming or replay, SDKs for application code, CLI for shell jobs, MCP Server for MCP-capable hosts, and Skill for reusable agent workflows.
4
Save trace fields
Store route, parameters, time window, data-quality result, and
meta.request_id with every output that another system will trust.Concept Decision Checklist
Before moving from concepts into code, write down the decision checklist that controls the request.When This Page Is Enough
This page is enough when the question is “where do I start?” or “which concept decides the route?” It is not enough when you are writing code. For code, move from this page into REST API, Endpoint reference, OpenAPI, or WebSocket.Data availability
Decide whether a venue, symbol, data family, and time window are available.
Venue taxonomy
Classify top-level venues and Hyperliquid-scoped market families before routing.
Order book depth
Separate L2, L3, L4, diffs, order events, history, and reconstruction.
Historical market data
Plan windows, routes, quality gates, replay, and export choices.
Replay and reconstruction
Decide when sequence, local state, and gap handling require stricter workflows.
Rate limits
Design around request rate, concurrency, credits, and route gates.
Free tier
Use a starter key to confirm route fit without implying production capacity.
Data gaps
Treat stale or incomplete windows as explicit data-quality decisions.