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

# Agentic gateway

> Use 0xArchive as a controlled market-data gateway for agents without confusing agent access, SIWE verification, and product API routes.

Older "agentic gateway" links map to controlled agent access for 0xArchive market data: route map, auth boundaries, data-quality gates, and a narrow execution surface instead of free-form endpoint guessing.

This is not the same as SIWE verification. SIWE verification is for wallet-signature account ownership checks before issuing `X-API-Key` credentials or browser sessions. An agentic gateway can use API keys, OpenAPI, docs, CLI, MCP Server, Skill, SDKs, REST, or WebSocket depending on the host.

## Gateway Layers

| Layer                | Role                                                     | Docs                                                      |
| -------------------- | -------------------------------------------------------- | --------------------------------------------------------- |
| Route map            | Prevent endpoint and namespace guessing                  | [OpenAPI](/openapi) and [Venue coverage](/venue-coverage) |
| Context              | Tell the agent how to choose routes and interpret fields | [AI clients](/ai-clients)                                 |
| Execution surface    | Give the host a safe way to call or generate calls       | [AI interface map](/agent-surfaces)                       |
| Auth boundary        | Keep keys out of prompts and checked-in config           | [Authentication](/authentication)                         |
| Data gate            | Stop stale or incomplete data from becoming output       | [Data quality](/data-quality)                             |
| Account verification | Use wallet-signature verification only when needed       | [SIWE verification](/wallet-automation)                   |

## Gateway Boundary Checklist

Use this checklist before an agent writes a script, configures a tool, or widens a market-data job.

| Boundary                 | Public rule                                                                                                                                                                                                             |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Market-data route        | Choose the venue family in [Venue coverage](/venue-coverage), then use [OpenAPI](/openapi) or the matching REST family for the exact path and parameters.                                                               |
| Credential handling      | Put keys in the host environment or secret manager, then send REST requests with `X-API-Key`; do not paste keys into generated source or prompts.                                                                       |
| Execution surface        | Pick one surface for the first run: REST, CLI, SDK, MCP Server, Skill, WebSocket, or OpenAPI codegen.                                                                                                                   |
| First request            | Use one route family, one symbol, one small window, and request-ID logging before adding loops, storage, dashboards, or models.                                                                                         |
| Payment and wallet flows | Use [Facilitator](/facilitator) for x402 payment infrastructure and [SIWE verification](/wallet-automation) for wallet-signature account checks. Neither changes market-data route shape, schemas, or freshness checks. |
| Stop condition           | If venue family, symbol format, credential path, route shape, or data-quality requirement is missing, resolve that before execution.                                                                                    |

## When To Use This Pattern

Use an agentic gateway pattern when a coding agent, analyst assistant, dashboard builder, or internal automation should fetch market data but should not invent routes, run unlimited loops, or ignore freshness. The gateway is the combination of context, auth, route contract, and bounded execution.

Do not use this page to claim a separate hosted agent product unless a live product surface shows it. The public docs should describe the integration pattern and point readers to the concrete surfaces that exist.

## Implementation Rules

<Steps>
  <Step title="Pin route context">
    Give the agent OpenAPI plus the page matching the job, such as Venue Coverage, Data Quality, REST, or WebSocket.
  </Step>

  <Step title="Choose one execution surface">
    Use CLI for terminal jobs, MCP Server for MCP-capable hosts, Skill for reusable workflows, SDKs for application code, or REST for direct HTTP.
  </Step>

  <Step title="Limit the first call">
    Require one route family, one symbol, one small window, and request-ID logging before widening.
  </Step>

  <Step title="Separate wallet access">
    Use SIWE verification only when the user explicitly needs wallet-owned account verification.
  </Step>
</Steps>

## Next Step

Open [AI interface map](/agent-surfaces) to choose the surface, then [Coding agents](/coding-agents) for host rules. Use [SIWE verification](/wallet-automation) only for wallet-owned account verification workflows.