Guides - 0xArchive

Guides help you make decisions before code hardens around the wrong venue, route, or freshness assumption. Start with the guide that matches the risk in your workflow. If the risk is wrong auth, use the first-request guide. If the risk is wrong market family, use venue coverage. If the risk is a slow or expensive job, use limits and throughput. If the risk is bad historical output, use reliability and data gaps before the first export or backtest run.

First authenticated request

Make one request and inspect the envelope.

Evaluate a market data API

Compare route coverage, schema evidence, freshness, exports, rights, and agent support.

Choose venue family

Classify Hyperliquid core, Spot, HIP-3, HIP-4, and Lighter before selecting routes.

Historical market data

Pull bounded history for research and backtesting.

Export historical data

Choose markets, schemas, ranges, credits, checkout, delivery, and rights for files.

Point-in-time backtesting

Build reproducible runs with route, window, quality, and request-ID metadata.

Monitor freshness

Add freshness and incident gates before downstream workflows trust data.

Build an agent workflow

Route agents through OpenAPI, docs, CLI, SDKs, MCP, Skill, and response parsing.

Migrate from a native API

Move historical data workflows while keeping native execution and official venue behavior native.

Choose a tooling workflow

Pick REST, WebSocket, CLI, SDKs, MCP, Skill, OpenAPI, or Markdown by runtime.

Venue coverage

Choose Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter correctly.

Limits and throughput

Keep jobs inside rate, concurrency, and credit envelopes.

Reliability and gaps

Gate jobs on coverage, incidents, and freshness.

Guide Selection

Guides are job-shaped. They do not replace Endpoint Reference; they tell you how to combine route families, parameters, data-quality checks, and tooling choices into a workflow that survives production use. For research and backtesting, pair Historical market data, Point-in-time backtesting, and Reliability and gaps. For shell and agent jobs, pair Choose a tooling workflow with Choose an interface. For any job that crosses Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, and Lighter, start with Venue coverage before writing route-specific code.

Guide Routing Checklist

Use this checklist when the reader has a workflow but not the right docs path yet.

Workflow risk	Guide path	Reference path
First request may fail on auth or envelope handling	First authenticated request	REST authentication, Responses, Errors
Venue family may be wrong	Choose venue family and Venue coverage	Venue taxonomy, REST API
Historical output may be incomplete or stale	Historical market data, Reliability and gaps	Data quality, Data gaps
Backtests need reproducible windows	Point-in-time backtesting	Responses, Rate limits
Files are better than repeated calls	Export historical data	Data catalog, Export schemas, Data rights
Agents or scripts need the right surface	Build an agent market data workflow, Choose a tooling workflow	Interface surface map, OpenAPI

Review Rule

If a guide is used to generate code, the resulting implementation should still link back to the generated route reference for exact parameters and schemas. Guides explain how to think; OpenAPI defines the contract. When in doubt, use the guide for workflow order and the generated endpoint page for the concrete request. Use both before committing shared client code.