Join our daily and weekly newsletters for the latest updates and exclusive content on industry-Leading Ai Coverage. Learn More
Interoperability Among Ai Agents is Sloly Gaining Traction as Organizations Begin to Build Networks of agents.
In the past few months, at least two agentic interoperability standard emerged: Anthropic’s Model context protocol (MCP) and AGNTCYFrom a collective Led by CiscoAs the importance of agents-competely that Built on different frameworks and large-language models (lLMS)-Talking to each other and getting a fulller picture of an enterprise’s data gains ground, another new protocol is vying for adoption.
Today, Google is unveiling a new interoperability protocol called 2AGENT, or a2a, that it hopes will become a standard with a standard with a standard with,
Partnering with more than 50 companies, Including Atlassian, Box, Cohere, Intuit, Langchain, Mongodb, Senseforce, Sap, Servicenow, UKG and Workday, Agent2Gent aims to be the interoperability language For agents and ai applications.
In an exclusive interview, rao suraapaneni, Vice President and General Manager of Google Cloud’s Business Application Platform, Told Venturebeat that A2A Makers IT Easier for agents with different Specializations and data nodes to get needed context.
“Everyone has a certification of person’s own a data node or a logic node, or the current user base is focused on that Particular Task,” Surapaneni Said. “You expect these frameworks to evolve with a very specialized focus. IF I’m A Customer and I’M Deploying these Multiple Platforms and Multiple Frameworks, I Don’t to do Swivel Chairrous Them. “
Surapaneni said part of the reason google worked with more than 50 partners and customers is to build a2a to have “an ability to interoperate to interoperate in an enterprise-house, security and Trustable Manner.”
Building on Existing Standards
A2A Facility Communication Between What Google Calls A CLIENT AGENT and A Remote Agent. The client agent formulates and communicates the task from the end user, and the remote agent acts on the task.
In a separate blog post, google said a2a depends on Several Key Capabilits Built on the Protocol.
- Capability discovery: Agents can “Advertise their capability” through an agent card in json format, so the client agent can determin the best remote agent to complete a task.
- Task Management: Ensuring Communication Between agents is oriented only towards completeing requests and defines the lifecycles for tasks.
- Collaboration: Sending Messages Around Context Replies, Artifacts (Output of Tasks), or instructions.
- User Experience Negotiation: Specify the content types and formats the agents are reading.
Surapaneni said google designed a2A as an open protocol, meaning the larger open source communication can contribute to the a2a project and sugges code updates.
“We are opening it up as a Community-Driven Efort and One that is properly open source,” He said. “There’s a governance board around it, but we do want it to be truly open and communication-Dr.”
In Developing A2A, Google focused on enabling agents to work “in their natural, unstructured modalities, even when they don’t share memory, tools, tools, tools, and context.” The protocol also builds on existing standards like http and json, so it’s emier to integrate with existing tech stacks and is secure by default.
Rise of interoperability protocols
Of course, A2A is not the only interoperability protocol in the market. Agentcy, from a collective of Cisco, Langchain, Galileo, LLAMAINDEX and Glean, AIMS to Create a Standard means of Communication Between agents. Langchain, which is also a partner in agent2agent, developed the Agent protocolMicrosoft updated its autogen framework to help Make interopeable agents,
On the other hand, many companies, including microsoft, have alredy embraced Mcp. Even Google Added Support for Mcp Through Its New Agent Development Kit. Surapanenin assured that A2A would run parallel with mcp.
“We see mcp and a2a as complementary capability,” SuraPaneni said. “The way we are looking at agent2Gent is at a higher layer of abstraction to enable applications and agents to talk to
Surapaneni did not close the door on possible collaboration with other consortia working on agent interoperability protocols. He Said A2A is Always Open for New Members, and the Protocol will be a living code constructed updated based on community suggestions and needs.
“We will look at how to align with all of the protocols,” Surapaneni said. “There will always be some protocol with a good idea, and we want to figure out how to how to brings all there that good ideas in.”
Interoperability Needs Arise
Organizations and AI Companies Agree That The World will Run on Multiple Ai Models Rather than one model ruling them all, so it makes senses that agents will also be Built on different languages and frameworks.
However, a fully realized agent ecosystem requires agents to talk to agents from other companies. But that is an emier said than done. Industry Standards often take time to take hold and require buy-in from a large portion of companies.
If A2A, MCP, or Angtcy hopes to successed in creating a standard way for all ai agents, no matter who built them or which framework they’re built on, there Must Be Must Be Must Be Mass Adoption and Depliyment.
Surapaneni Acknowledged that even with more than 50 partners work on a2A, adoption is still not at a tipping point.
“All of these protocols will evolve, especially the way rate ai is changing, and we’ll find new use cases and Scenarios to Tackle so it will continue to grow,” He Said.