Core Concepts

Domain

The top-level problem area in AgentRouter

View as Markdown

A domain is the highest-level bucket in AgentRouter.

It describes the problem area an agent is trying to solve, not the vendor the agent happens to call.

Examples:

  • email
  • enrichment
  • social
  • web
  • search
  • post
  • broadcast
  • finance
  • geo
  • document
  • media
  • models
  • travel
  • speech
  • translation
  • chain

Why Domains Exist

Agents reason better about tasks such as:

  • send an email
  • extract data from a page
  • answer a grounded search query
  • publish a post to a target channel
  • quote a public broadcast before approving the real post
  • run a finance lookup or market-data action
  • get current time or convert a datetime between locations
  • run model chat completion, code completion, or model listing
  • enrich a person record

than about vendors such as Resend, Brave, Firecrawl, or Apollo.

So AgentRouter is domain-first, not provider-first.

What A Domain Gives You

Each domain exposes:

  • a stable key such as email
  • a human label and description
  • a domain status such as live or pending
  • a path to its capabilities
  • a path to its route catalog

Example:

1{
2  "domainKey": "email",
3  "label": "Email",
4  "description": "Programmatic outbound email and inbox lifecycle management for agents.",
5  "status": "live",
6  "capabilitiesPath": "/api/agentic-api/domains/email/capabilities",
7  "routesPath": "/api/agentic-api/domains/email/routes"
8}

How To Use A Domain

1

Map the task to one domain

Choose the domain that best matches the user’s intent.

2

List capabilities

Call GET /domains/{domainKey}/capabilities.

3

Inspect one capability contract

Call GET /domains/{domainKey}/capabilities/{capabilityId}/contract when you need the exact request shape.

Design Rule

Do not create top-level domains for every provider or every thin endpoint variation.

Good:

  • search.answer
  • web.extract
  • email.send

Bad:

  • exa-answer
  • firecrawl-scrape
  • resend-send

Those provider-specific choices belong at the route layer.