> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.agentrouter.to/llms.txt.
> For full documentation content, see https://docs.agentrouter.to/llms-full.txt.

# Welcome

AgentRouter gives agents and agent builders one routed surface for discovering, paying for, and executing paid APIs.

Instead of wiring each vendor separately, learning a new billing model each time, and guessing which provider is cheapest or most reliable, you integrate once with AgentRouter and work in a stable capability-first model:

<Steps>
  <Step title="Discover the catalog">
    Call `GET /domains` and `GET /domains/{domainKey}/capabilities` to find the problem space you need.
  </Step>

  <Step title="Recommend a route">
    Call `POST /domains/{domainKey}/capabilities/{capabilityId}/recommend` when you want AgentRouter to choose the best supply path for cost, reliability, speed, or quality.
  </Step>

  <Step title="Execute the capability">
    Call `POST /domains/{domainKey}/capabilities/{capabilityId}/execute` with the exact request body for the chosen capability.
  </Step>

  <Step title="Track spend and usage">
    Use one AgentRouter wallet and inspect `GET /wallet` and `GET /usage` instead of reconciling many provider-side payment flows.
  </Step>
</Steps>

<Note>
  AgentRouter covers domains such as `email`, `enrichment`, `social`, `web`, `search`, `post`, `finance`, `document`, `media`, `travel`, `speech`, `translation`, and `chain`, with routes across direct billing, `x402`, and Tempo/MPP-backed rails.
</Note>

## Start Here

<CardGroup cols={3}>
  <Card title="Introduction" icon="duotone compass" href="/introduction">
    Understand what AgentRouter is, why it exists, and how the capability-first model works
  </Card>

  <Card title="Quickstart" icon="duotone bolt" href="/quickstart">
    Go from API key to your first recommend and execute call in a few minutes
  </Card>

  <Card title="Domain" icon="duotone grid-2" href="/core-concepts/domain">
    Learn how AgentRouter groups paid APIs by problem area instead of by vendor
  </Card>

  <Card title="Recommendation" icon="duotone stars" href="/core-concepts/recommendation">
    See how route selection works before you spend credits on execution
  </Card>

  <Card title="CLI" icon="duotone terminal" href="/integrations/cli">
    Run AgentRouter from your terminal to inspect the catalog, reproduce requests, and smoke test recommend and execute flows
  </Card>

  <Card title="SDK" icon="duotone code" href="/integrations/sdk">
    Build directly on AgentRouter with one typed client for catalog discovery, recommendation, execution, wallet, and usage
  </Card>

  <Card title="SKILL.md" icon="duotone file-code" href="/integrations/skills">
    Give an agent a hosted markdown skill it can read, follow, and use over HTTP
  </Card>

  <Card title="MCP" icon="duotone plug" href="/integrations/mcp">
    Install AgentRouter in any MCP-compatible client through the hosted endpoint or the local fallback package
  </Card>
</CardGroup>

## Concrete Surfaces

Use the docs site for integration concepts and contracts. Use the main AgentRouter site when you want concrete domain pages with provider coverage, pricing examples, and execution-focused detail.

<CardGroup cols={3}>
  <Card title="Supporting Domains" icon="duotone grid-2" href="https://www.agentrouter.to/supporting-domains/overview">
    Browse domain-specific docs for email, enrichment, social, web, search, post, finance, travel, and more
  </Card>

  <Card title="Email Domain" icon="duotone envelope" href="https://www.agentrouter.to/supporting-domains/email">
    See concrete email capabilities, route examples, pricing context, and quick-start flows
  </Card>

  <Card title="Get API Key" icon="duotone key" href="https://www.agentrouter.to/agentic-api/install">
    Start the hosted install flow, sign in, and copy the setup block for SDK, CLI, SKILL.md, or MCP
  </Card>
</CardGroup>

## Mental Model

Use this sequence when building with AgentRouter:

1. Start with a **domain** such as `email`, `search`, `web`, or `enrichment`.
2. Pick a **capability** such as `email.send` or `search.answer`.
3. Let AgentRouter choose a **route** unless you have a strict provider requirement.
4. Use **recommend** when you want route selection.
5. Use **execute** when you want the paid operation to happen.
6. Let the AgentRouter wallet and settlement layer handle the underlying payment rails.