A2A agents and approvals

Enterprise only

Not included in DVARA Open Source.

The A2A pages let your workspace govern the agent-to-agent hops your agents make — registering the peers they may delegate to, and resolving the approvals that pause sensitive hops. This is the workspace-scoped view of the A2A plane; everything here is filtered to your workspace.

Roles

• Admin / developer — register and edit A2A agents, approve or deny hops.
• Viewer — read-only: see the registry, the pending queue, and the decision history, but cannot register agents or resolve approvals.

A2A agents

Open A2A → Agents in Flightdeck. This is the registry of peer agents your workspace is allowed to reach — a hop can only target an agent registered here, and you only ever see your own workspace's agents.

Register a peer with its Agent ID (unique in your workspace), Endpoint URL, auth scheme and credential, auth mode (STORED or DELEGATED), and an optional skills allow-list that bounds what discovery advertises for it.

From 1.8.5 an active agent's endpoint must be https://, as the A2A specification requires; anything else is refused with A2A_ENDPOINT_NOT_HTTPS. An agent saved over http:// before 1.8.5 is marked Not HTTPS in the list, and the gateway sends it nothing until you move it to https:// or disable it.

From 1.8.4 the auth scheme defaults to From the Agent Card for a new agent: DVARA reads the peer's card and takes the one scheme it declares. If the card cannot be read or declares more than one kind, the save is refused and you choose. A scheme you choose is checked against the card, and a mismatch is shown as a warning, never a refusal. An agent ID your workspace already uses is refused on the form with A2A_AGENT_DUPLICATE, keeping what you typed, and a new ID that contains :: is refused with A2A_AGENT_ID_INVALID.

SSRF protection

The endpoint URL is validated when you save it. It must be a public https endpoint — loopback, private, link-local, and cloud-metadata addresses (e.g. 127.0.0.1, 10.0.0.0/8, 169.254.169.254) are rejected. DVARA connects to this URL server-side on every hop, so this prevents a registered agent being used as a server-side request-forgery primitive.

Approvals

Open A2A → Approvals in Flightdeck. When a hop matches your workspace's approval rules — by requested skill or by target agent — it pauses here until someone decides. Nothing is delegated to the peer until you approve.

Pending

Every hop awaiting a decision, with the caller, the target agent, the requested skill, and when it was raised. Approve releases the hop to the peer; Deny rejects it. The queue auto-refreshes, and a nav badge shows the pending count.

The decision is durable and cross-pod: it releases the paused hop on whichever gateway pod is holding it, so it does not matter which pod served your click.

History

The decision log for your workspace — every resolved hop with its action, who decided it, and when.

Isolation

You only see and resolve your own workspace's A2A approvals. A hop raised for another workspace is never listed here, and an attempt to resolve one is rejected. Platform operators use the cross-workspace A2A approval queue.

If a paused hop is not resolved before its timeout, your workspace's default action applies (deny, unless configured otherwise). From 1.8.5, if the hop's session is killed while it waits, the approval is denied at once and the hop is refused with A2A_SESSION_KILLED.

A2A delegation

A workspace admin sets the delegation guard on Agents → A2A Delegation: the mode, the cycle rule, the maximum depth and whether agents must send their chain. From 1.8.5 the page also sets:

• Preset — standard (the default) or hardened. hardened requires the chain from agents, uses the agent cycle rule and always has a session hop budget (200 unless you set one). Mode and maximum depth still apply, so you can observe it first.
• Max hops per session — the most hops one session may forward. Blank uses the gateway default, which is no limit unless your operator set one. 0 means no limit, except under hardened, which then uses 200. A hop past it is refused with 409.

An agent that must start work of its own needs its key marked May start chains on the API Keys page. See Use the hardened preset.

Where to go next

• A2A Governance Plane — what a governed hop is and what it checks.
• A2A Governance — platform-wide registry, policies, hop audit, and approvals.