Avery.Software — Native Execution Runtime
RuntimeUse casesPricingHelpBlog
← Back to helpconcept · agents

What crosses the wire (and what doesn't)

1 min

Only the message + configuration you author. Never secrets, OAuth, or project paths.

Each outbound A2A call sends three things: (1) the prompt text from the node's Message field, after any template substitution against upstream outputs; (2) the optional configuration block (accepted output modes, a push-notification webhook URL); (3) a call-stack header listing agent ids visited so far for loop detection (capped at 4 hops). The handler never forwards your connector credentials, OAuth tokens, encrypted per-agent secrets, project folder paths, or `appReferences`. The remote agent operator is a separate party with its own privacy + acceptable-use posture — review their terms before connecting. Full disclosure lives in §11.4–11.6 of the Terms of Use + §4.5 of the Privacy Policy.


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.

Download desktop →