> ## 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 task guides for selecting a market family, making a bounded request, and recording a usable result.

Follow a guide end to end for one job: pull a bounded history, export files, check a window before use, run a job inside your limits, evaluate fit, or move a read off a native venue API. Each guide starts from one market and one window, and ends with output you can reproduce.

## Before you start

* Know the record you need: a snapshot, historical rows, a file export, a freshness decision, or a replay.
* Name one venue and market type, and one symbol or market identity. Keep the original symbol spelling; [Venues and market types](/core-concepts/venue-taxonomy) shows the namespace for each.
* Load an API key from the runtime environment for authenticated market-data routes. The public `/v1/symbols` discovery route does not need a key. [REST authentication](/rest-api/authentication) covers the request header, and each endpoint page lists its final parameters and response fields.
* Keep each run bounded. Start with one market, one route, and one short window, and widen only after the first run has a clear result and request IDs.

## Pull and check data

<CardGroup cols={2}>
  <Card title="Pull historical market data" icon="history" href="/guides/historical-market-data">
    Page through one bounded window with cursors, and save the request IDs and quality decision with the rows.
  </Card>

  <Card title="Check one window before use" icon="shield-check" href="/data-quality#check-one-window-before-use">
    Read freshness, coverage, and incidents for the same market and window before a backtest or alert depends on it.
  </Card>

  <Card title="Export historical data" icon="file-down" href="/guides/export-historical-data">
    Create one bounded Data Catalog export selection and keep a traceable order record for the files.
  </Card>

  <Card title="Prepare data for a reproducible backtest" icon="rotate-ccw" href="/guides/point-in-time-backtesting">
    Freeze a window, check it, and pull it through REST or WebSocket replay with a run manifest.
  </Card>
</CardGroup>

## Plan and evaluate

<CardGroup cols={2}>
  <Card title="Limits and throughput" icon="gauge" href="/guides/limits-and-throughput">
    Run one finite job with explicit worker, page, retry, and stop budgets.
  </Card>

  <Card title="Evaluate a market data API" icon="clipboard-check" href="/guides/evaluate-market-data-api">
    Decide whether an API returns the record one job needs, with route, quality, capacity, and rights evidence.
  </Card>

  <Card title="Migrate from a native venue API" icon="arrow-right-left" href="/guides/migrate-from-native-api">
    Move one historical order-book read to 0xArchive and keep execution and account calls where they are.
  </Card>

  <Card title="First bounded request for coding agents" icon="bot" href="/coding-agents#first-bounded-request">
    Give a coding agent one exact route, a bounded window, and a stop condition.
  </Card>
</CardGroup>

## What every guide records

Every guide ends with the same record beside its output: the method, path, and query; the venue and market type; the symbol; the response status; the request IDs; and the quality or coverage decision that controls the next action. A second engineer should be able to repeat the same bounded call from that record without guessing. Keep the response body separate from the record so recorded inputs are never mistaken for returned data.

If a request fails, the [Errors](/errors) page lists each `error_code` and what to do next. A stale or incomplete quality result means narrowing, delaying, or marking the output, never filling in missing rows.

## Next step

Start with [Pull historical market data](/guides/historical-market-data) for your first bounded pull.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.