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.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.
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 the generated REST 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 Packet
Use this packet 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 | 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 |