AgentRoute

How a requested capability or intent resolves to the agents eligible to serve it.

Why it exists#

More than one agent can claim the same capability — during a migration, an A/B test, or a per-region split. A route is where you express which of them are eligible and in what order, without redeploying anything or changing the caller.

A capability route#

apiVersion: agentfleet.io/v1alpha1
kind: AgentRoute
metadata:
  name: refund-processing-route
  namespace: agentfleet-demo
spec:
  routeType: capability
  capabilities:
    - refund-processing
  priority: 100
  enabled: true

Priority breaks ties, health decides eligibility#

Routing runs in two stages. First the registry narrows to agents that declare the capability and are healthy. Then the scheduler ranks what is left, using route priority, and returns a reason for the choice. That reason travels back on the response as route.reason, so a selection can always be explained after the fact.

Turning a route off#

Setting enabled: false takes a route out of selection without deleting it, which is the safe way to drain traffic from an agent you are about to change.