Agent card
The agent card is a structured profile of what a standard domain knows. Orchestrators read each source domain's agent card to decide which domains a given question should be routed to, so a complete, accurate card directly improves routing quality. The agent card lives at Settings → Agent card and is available on standard domains only — orchestrators do not have one.
- Description (required, max 600 characters) — one to three sentences describing what the domain covers. Be concrete: name the products, modules, and subject areas the domain answers about.
- Topics — a chip list of the key subjects the domain covers
(e.g.
autopilot,battery). Type a topic and press Enter to add it. - Capabilities — a chip list of the kinds of answers the domain provides
(e.g.
setup guides,troubleshooting). - Example questions — up to five full-sentence example questions the domain handles well. These give the orchestrator concrete routing signals.
- Exclusions — topics the domain explicitly does not cover. Listing exclusions helps prevent the orchestrator from mis-routing questions to this domain.
When you link a source domain that has no agent card configured, the Sources page shows a warning: "No agent card configured… Add one to improve routing."
Tip
Even if you do not use orchestrators today, fill in a complete agent card.
Routing accuracy improves as your organization grows and more domains are added, and the card
requires no maintenance once it reflects the domain's scope.
FAQ
What is an agent card and why does it matter for routing?
An agent card is a structured profile of what a standard domain knows. Orchestrators read each source domain’s agent card to decide which domains a question should be routed to. A complete and accurate agent card directly improves routing quality.
Where do I find the agent card, and which domains have one?
The agent card lives at Settings → Agent card. It is available on standard domains only. Orchestrators do not have an agent card.
What fields are included in the agent card, and what should I put in them?
The agent card includes Description (required, max 600 characters), Topics, Capabilities, Example questions (up to five), and Exclusions. The description should be one to three concrete sentences naming the products, modules, and subject areas the domain covers. Topics and capabilities are chip lists, example questions provide concrete routing signals, and exclusions list what the domain does not cover to prevent mis-routing.
How do I add a topic to the Topics list in the agent card?
In the Topics chip list, type a topic and press Enter to add it. Topics are meant to capture the key subjects the domain covers (for example, “autopilot” or “battery”).
Why do I see a "No agent card configured… Add one to improve routing" warning on the Sources page?
This warning appears when you link a source domain that has no agent card configured. The Sources page shows the message to indicate routing can be improved by adding an agent card. Configuring the card helps orchestrators route questions more accurately.