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 where do I find it?
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, so a complete and accurate card improves routing quality. You can find it at Settings → Agent card, and it’s available on standard domains only (orchestrators do not have one).
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 full-sentence 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 field, type a topic and press Enter to add it to the chip list. Topics are meant to capture the key subjects the domain covers (for example, “autopilot” or “battery”).
What warning appears if I link a source domain that has no agent card configured?
If you link a source domain without an agent card configured, the Sources page shows a warning message. The warning reads: "No agent card configured… Add one to improve routing."
Why should I fill out an agent card even if I don’t use orchestrators today?
Filling in a complete agent card improves routing accuracy as your organization grows and more domains are added. Once the card reflects the domain’s scope, it requires no maintenance. Completing it now helps ensure better routing later.