Skip to navigation
Get Started

Welcome

A capability-first gateway for paid APIs

View as Markdown

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:

1

Discover the catalog

Call GET /domains and GET /domains/{domainKey}/capabilities to find the problem space you need.

2

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.

3

Execute the capability

Call POST /domains/{domainKey}/capabilities/{capabilityId}/execute with the exact request body for the chosen capability.

4

Track spend and usage

Use one AgentRouter wallet and inspect GET /wallet and GET /usage instead of reconciling many provider-side payment flows.

AgentRouter covers domains such as email, enrichment, social, web, search, text, post, broadcast, finance, geo, document, media, models, travel, speech, translation, and chain, with routes across direct billing, x402, and Tempo/MPP-backed rails. As of May 1, 2026, broadcast.message.quote is live while broadcast.message.send remains intentionally gated because it creates a real public post. geo.time.current.abstract-timezone.mpp and geo.time.convert.abstract-timezone.mpp are live after the May 9, 2026 paid smoke. text.analyze.diffbot-nl.mpp is mapped and recommendable, but execution is gated until the Diffbot NL MPP route clears its HTTP 429 before-payment blocker and paid smoke succeeds.

Start Here

Introduction

Understand what AgentRouter is, why it exists, and how the capability-first model works

Quickstart

Go from API key to your first recommend and execute call in a few minutes

Domain

Learn how AgentRouter groups paid APIs by problem area instead of by vendor

Recommendation

See how route selection works before you spend credits on execution

CLI

Run AgentRouter from your terminal to inspect the catalog, reproduce requests, and smoke test recommend and execute flows

SDK

Build directly on AgentRouter with one typed client for catalog discovery, recommendation, execution, wallet, and usage

SKILL.md

Give an agent a hosted markdown skill it can read, follow, and use over HTTP

MCP

Install AgentRouter in any MCP-compatible client through the hosted endpoint or the local fallback package

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.

Supporting Domains

Browse domain-specific docs for email, enrichment, social, web, search, text, post, broadcast, finance, geo, travel, and more

Email Domain

See concrete email capabilities, route examples, pricing context, and quick-start flows

Get API Key

Start the hosted install flow, sign in, and copy the setup block for SDK, CLI, SKILL.md, or MCP

Mental Model

Use this sequence when building with AgentRouter:

  1. Start with a domain such as email, search, web, enrichment, or broadcast.
  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.