A2A Protocol
Agents that can talk to other agents.
A2A is the Agent2Agent protocol: one agent discovers and calls another. A CrewAI invoice crew, an ADK helpdesk agent and Agentforce stop being silos, with identity and an audit trail between them.
Founded 2022 · Founder in the Salesforce MVP Hall of Fame · Dubai HQ · Kochi studio
- 01Models · Claude, Gemini, OpenAI, Bedrock
- 02Agentic systems · Agentforce, CrewAI, ADK, A2A
- 03Agentic memory · Neo4j, Cognee, IndyKite
- 04Automation and voice · n8n, Retell
- 05Deployment and governance · identity, evals, policy, audit
What we put in
The work on this layer.
The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.
How it flows
One agent hands work to another.
Ask
A customer asks Agentforce about an invoice
The answer lives in the finance system, not the org.
Find
Agentforce finds the invoice agent
From its published agent card, not a hand-built API.
Hand off
The task travels with the identity
The invoice agent sees only that customer’s invoices.
Return
The answer comes back, both sides logged
A reviewer can follow the whole chain.
Use cases
Where this shows up in the work.
These are the use cases we usually pair with A2A Protocol.

AI IT Support Transformation
Ticket routing and a knowledge desk. An agent on the repeats. A person on the exceptions.

AI Customer Service Transformation
Cases, knowledge, and the channel the customer already uses. An agent on the repeats. A person on the exceptions.

Supply chain
Inventory and orders between ERP and Salesforce when that is the job. Real-time or batch from the desk.
Related reading
From the blog.
Research-led notes that back this page.
Questions
What we actually say.
- What is A2A?
- Agent2Agent is a protocol for one agent to discover and invoke another. It is the interop layer. MCP is how an agent calls tools and data. You usually want both.
- Do we need A2A if we only have one agent framework?
- Not on day one. It becomes useful the moment a second runtime appears: Agentforce plus CrewAI is the usual trigger.
- How do you stop agents from calling anything they can see?
- Capability cards, identity (often IndyKite or your IdP), and an allow-list. Discovery is not the same as permission.
- Does delegation escalate privilege?
- Not if on-behalf-of identity travels with the request. When agent A asks agent B, the user’s authority goes too, and hop budgets stop cyclic delegation. That is the runtime plane working as designed.
The brief
More than one agent runtime already?
We will map the agents you have, what they should be allowed to call, and whether A2A is the right glue. The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days.