Agent2Agent

That's real convergence, and a year or two ago it wasn't obvious that would happen.

And A2A, agent to agent, has been picking up governance traction through this year as a complementary protocol for agents talking to other agents.

Those two are starting to standardize the communication layer.

But neither of them touches memory.

Neither of them touches memory or state.

You can have two agents that speak perfect MCP and perfect A2A and still have no way to hand one agent's memory to another.

The protocol standardized how agents talk.

They didn't standardize what agents remember or how they store it.

So, yeah, they are building systems using both MCP and So they shared, you know, some of the things they reviewed.

Companies like Tencent, who makes WeChat, for example, they use A2A pretty heavily.

But like, yeah, companies like Tencent that makes WeChat, they use A2A pretty heavily there.

Also Huawei, they use it in their stack as well.

And so it was fascinating hearing the talks and essentially seeing the diagrams and where they plug these protocols in.

Yeah.

So that's one angle, but it's really fascinating to see.

And then I'm also exploring A2A a lot lately.

So that's what we're gonna be tackling.

So on today's show, stick with me for the next 20 minutes and you're gonna learn why Salesforce told 25 years of CRM users that the browser login is p-pretty much over, uh, how MCP and A2A protocols became the new open protocols that every enterprise agent now runs on.

You're gonna know why interfaceless software or headless software could likely be where the majority of work gets done in the future.

And ultimately, where does this leave your company, your CRM contracts, your IT spend, and all of those customer-facing workflows? All right, let's dive into it.

It is interface-less software, right? So they are literally just rebuilding their software at the core, uh, to make sure that it works agentically, right? So headless just means the software still works, but there's no actually, uh, you know, there's no real user interface required to use it, right? And who knows? Maybe y- you know, the fact that, um, you know, we're almost four years into the generative AI era and the fact that we still have, um, you know, normal user interface software, right, software built for humans, maybe we'll look back at this time and be like, "What took so long? This is crazy." Or who knows? Uh, maybe headless software will be something that is more of a trend or more of a drop in the bucket.

I will say probably not, right? Because, you know, whether you're talking about ...

And there's different ways that headless software kind of presents itself, right? And I'll break this down in a little bit, but, uh, I think once you start using it, whether it's through command line interface, uh, APIs, right, been around forever, or the new, uh, agent-based, right, um, model context protocol, A2A, agent-to-agent protocol, right? The more you use this, once you get it to work, you're like, "Why would I ever log into my software again?" Right? There's so many pieces of software I just don't use anymore, right? I've, I've used ...

This isn't an exaggeration.

A total of 173 companies have publicly put their name to the same thing.

A web standard, an emerging one called A2A, agent to agent for ai agents belonging to different companies to find each other and talk to each other so i looked at most of those companies i took the web address the project itself a2a lists next to each name of the company and i asked every one of them the question that the standard is built around are you there what can you do only four of them answered in a way that the standard describes This is no hacks with me, Slobodan Manic.

Nobody asked any of us if we wanted the internet changed.

So check what AI is actually doing to it.

And I don't mind plain or boring.

But a lot of what we are being told is, and sold actually, is for a visitor that has not turned up yet.

Including this A2A stuff.

So I went looking.

... and maybe this interface is running an agent locally or is talking to some remote agent, and, uh, that can be done through various protocols.

There's, like, A2A and ACP-

Mm-hmm

... um, that are out there for communicating with agents.

So a hu-

Right

... there's a human, then right now we can't talk in those A2A or A- [chuckles] ACP protocols.

It, there has to be a UI.

It's on both sides, really.

We are an infrastructure and we're built MCP native, which again, I think maybe to put that up front, we do believe that within the next 12 to 18 months or 24 months at the latest, the travel consumer behavior will change towards A2A.

So you need to be ready to, in our opinion, 50% of all bookings will happen that way.

So you need to be ready.

That will happen in Q4.

We're currently in beta testing, and we're testing all connectivity scenarios, from the manual one to the semi-automated to the fully automated scenarios.

And we're also in the process of building out our own AI agent to then fit with the A2A connectivity.

But on both sides, it is if either the supplier or the distributor wanted to fully based on AI.