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, post, finance, document, media, travel, speech, translation, and chain, with routes across direct billing, x402, and Tempo/MPP-backed rails.

Start Here

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.

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.