Agent-to-agent wrapping

Shivanath Devinarayanan · Updated

On this page

Agent-to-agent wrapping: an upstream broker posts an A2A task. The wrapper maps it to Agentforce sessions and messages. contextId and taskId scope the hop. Conversational memory only when identity is stable and the wire contract is honest. Do not advertise streaming, push, or history the wrapper does not implement.

The first Service Agent has to exist before you wrap it. That work is Agentforce setup in the org . On-behalf-of and token exchange are identity . The wrapper does not invent token exchange inside the Mule app. The gateway does OBO.

Caller An upstream broker posts an A2A task. It does not open an Agentforce session as itself.
Wrapper Maps the task to Agentforce sessions and messages. Scopes with contextId and taskId. Conversational memory only when identity is stable and the wire contract is honest.
Agentforce Agent API The Salesforce runtime. The wrapper does not invent token exchange inside the Mule app. The gateway does OBO.

Caller, wrapper, Agent API

Caller posts the task. Wrapper maps sessions and messages. Agentforce Agent API is the Salesforce runtime. If the wrapper claims streaming or push that it does not implement, the wire contract is a lie, and conversational memory will not be honest either.

The A2A lane on the gateway is a separate door from the LLM lane. Detail is on one front door . The network hub is Agentforce Network .

How to hire

Hiring starts with a governed production agent on one documented job, then a consultation.

Start at stand up production AI agents , then book a consultation . These pages are the operating model. The nine services remain the paid catalog.

SHIVANATH DEVINARAYANAN · SALESFORCE MVP HALL OF FAME ·

Stand up the first production agent

Hiring starts with a governed production agent on one documented job, then a consultation.

Also in this file: Home · About · Services · Portfolio · Success Stories · Writing · Events · Contact · Media kit · Privacy Policy