Quilzomanual

A2A: agent cards and tasks from other vendors' agents

Tell other agents what yours may do, and take their tasks under your own rules.

A2A (Agent2Agent) is the protocol agents use to describe themselves and hand each other work. Quilzo publishes an agent card for your agents, with a governance extension stating what each may do, and accepts A2A 1.0 tasks, each run as one of your agents under its declaration.

Publish an agent card

quilzo config set site.agent_card true

The public site then serves /.well-known/agent-card.json. Each skill is one of your agents, and the agent governance extension carries what the protocol cannot say: the closed list of capabilities, the autonomy, whether it writes, whether a person approves, its scope, its budget, its delegates, the hosts it reaches and its memory, all read from the enforced declaration.

Accept tasks from other agents

  1. Turn tasks on

    quilzo config set a2a.tasks true

    The card then names the task endpoint, /a2a on the admin, with protocolBinding JSONRPC and protocolVersion 1.0.

  2. Give the sending agent a credential

    A caller authenticates with a Quilzo token or an OAuth connection (see Connect AI apps). Each task runs as one of your agents, under its declaration narrowed by that credential's access.

  3. Let it send work

    The methods are SendMessage, GetTask, ListTasks and CancelTask, over JSON-RPC with the header A2A-Version: 1.0. The run is the task: kept, traced and receipted like any other. A run that stops for a person to approve a step stays working until somebody here decides.

Register other vendors' agents

quilzo fleet add https://agents.example.com/.well-known/agent-card.json

You answer for an agent you register. It appears on the Fleet map, and quilzo fleet check reads every card again and says which changed.

Next