While I am not familiar with OPs project,
I can somewhat answer this to best of my knowledge.
Right now, businesses communicate with REST Apis.
That is why we have API gateways like AWS Gateway, Apigee, WSO2 (company i used to work in), Kong, etc so businesses can securly deploy and expose APIS.
As LLMS gets better, the idea is we will evenutally move to a world where ai agents do most of business tasks. And businesses will want to expose ai agents instead of APIS.
This is where protocols like a2a comes in. Google partnering with some other giants introduced a2a protocol a while ago, it is now under linux foundation.
It is a standard for one agent to talk to another agent regardless of the framework (langchain, crewai etc) that is used to build the agent.
I see. If iiuc, it's like an extension to an API endpoint. Instead of exposing only endpoints, you can let a user describe an intent and have the agent do the work. Is this not also the goal of an MCP as well?
Can't you just put the agent behind a REST API and give the other agents a curl tool + doc?
You can.
Everyone will have their own versions of the rest endpoints, their own version of input params, and lots and lots of docs scatterd.
A standard, will help the ecosystem grow. Tooling, libraries etc.
A major reason agentic LLMs are so promising right now is because they just Figure It Out (sometimes).
Either the AI can figure it out, and it doesn't matter if there is a standardized protocol. Or the AI can't figure it out, and then it's probably a bad AI in the first place (not very I).
The difference between those two possibilities is a chasm far too wide to be bridged by the simple addition of a new protocol.
I think that‘s a bit shortsighted.
Having A2A is much more efficient and less error prone. Why would I want to spend tons of token on an AI „figuring it out“, if I can have the same effect for less using A2A? we can even train the LLMs with A2A in mind, further increasing stability and decreasing cost.
A human can also figure everything out, but if I come across a well engineered REST API with standard oauth2 , I am productive within 5 minutes.