Add an external agent
1 min · 4 steps
Paste an AgentCard URL, see the card preview, confirm. Two clicks.
Each remote A2A agent publishes an 'AgentCard' — a small JSON document describing its name, version, skills, and endpoints. You give Avery the agent's base URL; we resolve the well-known card path (`/.well-known/agent-card.json` per RFC 8615) and cache the response. The card preview shows you exactly what you're registering before you commit. Outbound traffic flows directly from your device to the URL you supplied — Avery's central service is never in the path.
Steps
- Drop an 'External agent' node onto the canvas.
Builder palette → Compose section → External agent. Connect it from a trigger or upstream node like you would any other node.
- Click '+ Add…' in the node's picker.
The first time you use this node, the picker is empty. The '+ Add…' button opens a dialog asking for the AgentCard URL.
- Paste the AgentCard URL and click 'Add agent'.
Base URLs work — Avery appends the well-known suffix. The dialog shows the card preview on success (name, skills, modes); errors surface inline with the worker-side error code (E_A2A_PRIVATE_URL / E_AGENT_CARD_FETCH / E_A2A_TRANSPORT).
- Write the message template.
The 'Message' textarea is the prompt forwarded to the remote agent. It supports the same `{{nodes.x.output.y}}` bindings every other node accepts — chain the external agent off any upstream node's output.
Live recipes need the desktop
This article is a static preview. The in-app Help sidecar inside Avery NXR can fire each step against your live project — install the desktop to use it interactively.