> ## 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.

# Guides

> Practical 0xArchive implementation guides for choosing venues, pulling history, managing limits, monitoring freshness, and handling gaps.

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.

<CardGroup cols={2}>
  <Card title="First authenticated request" icon="rocket" href="/guides/first-authenticated-request">
    Make one request and inspect the envelope.
  </Card>

  <Card title="Evaluate a market data API" icon="clipboard-check" href="/guides/evaluate-market-data-api">
    Compare route coverage, schema evidence, freshness, exports, rights, and agent support.
  </Card>

  <Card title="Choose venue family" icon="route" href="/guides/choose-venue-family">
    Classify Hyperliquid core, Spot, HIP-3, HIP-4, and Lighter before selecting routes.
  </Card>

  <Card title="Historical market data" icon="database" href="/guides/historical-market-data">
    Pull bounded history for research and backtesting.
  </Card>

  <Card title="Export historical data" icon="file-archive" href="/guides/export-historical-data">
    Choose markets, schemas, ranges, credits, checkout, delivery, and rights for files.
  </Card>

  <Card title="Point-in-time backtesting" icon="history" href="/guides/point-in-time-backtesting">
    Build reproducible runs with route, window, quality, and request-ID metadata.
  </Card>

  <Card title="Monitor freshness" icon="activity" href="/guides/monitor-freshness">
    Add freshness and incident gates before downstream workflows trust data.
  </Card>

  <Card title="Build an agent workflow" icon="bot" href="/guides/build-agent-market-data-workflow">
    Route agents through OpenAPI, docs, CLI, SDKs, MCP, Skill, and response parsing.
  </Card>

  <Card title="Migrate from a native API" icon="move-right" href="/guides/migrate-from-native-api">
    Move historical data workflows while keeping native execution and official venue behavior native.
  </Card>

  <Card title="Choose a tooling workflow" icon="wrench" href="/guides/tooling-workflow">
    Pick REST, WebSocket, CLI, SDKs, MCP, Skill, OpenAPI, or Markdown by runtime.
  </Card>

  <Card title="Venue coverage" icon="layers" href="/guides/venue-coverage">
    Choose Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter correctly.
  </Card>

  <Card title="Limits and throughput" icon="gauge" href="/guides/limits-and-throughput">
    Keep jobs inside rate, concurrency, and credit envelopes.
  </Card>

  <Card title="Reliability and gaps" icon="shield-check" href="/guides/reliability-and-gaps">
    Gate jobs on coverage, incidents, and freshness.
  </Card>
</CardGroup>

## 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](/guides/historical-market-data), [Point-in-time backtesting](/guides/point-in-time-backtesting), and [Reliability and gaps](/guides/reliability-and-gaps). For shell and agent jobs, pair [Choose a tooling workflow](/guides/tooling-workflow) with [Choose an interface](/tooling). For any job that crosses Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, and Lighter, start with [Venue coverage](/guides/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](/guides/first-authenticated-request)                                                                     | [Authentication](/authentication), [Responses](/responses), [Errors](/errors)                 |
| Venue family may be wrong                           | [Choose venue family](/guides/choose-venue-family) and [Venue coverage](/guides/venue-coverage)                                        | [Venue taxonomy](/core-concepts/venue-taxonomy), [REST API](/rest-api)                        |
| Historical output may be incomplete or stale        | [Historical market data](/guides/historical-market-data), [Reliability and gaps](/guides/reliability-and-gaps)                         | [Data quality](/data-quality), [Data gaps](/core-concepts/data-gaps)                          |
| Backtests need reproducible windows                 | [Point-in-time backtesting](/guides/point-in-time-backtesting)                                                                         | [Responses](/responses), [Rate limits](/rate-limits)                                          |
| Files are better than repeated calls                | [Export historical data](/guides/export-historical-data)                                                                               | [Data catalog](/data-catalog), [Export schemas](/export-schemas), [Data rights](/data-rights) |
| Agents or scripts need the right surface            | [Build an agent market data workflow](/guides/build-agent-market-data-workflow), [Choose a tooling workflow](/guides/tooling-workflow) | [Interface surface map](/agent-surfaces), [OpenAPI](/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.