← All IntelClip / AI AgentsUsing Google's A2A spec as the internal front-end/back-end contract
From Agents in Production: How OpenGov Built and Scaled OG Assist - Gabe De Mesa, OpenGov · ≈7:46
Shows a non-obvious use of the agent-to-agent protocol: not for cross-vendor interop but as a schema contract that keeps internal teams aligned.
What’s in it
- Shows a non-obvious use of the agent-to-agent protocol: not for cross-vendor interop but as a schema contract that keeps internal teams aligned.
Clip transcript
for the team as well, to have full agency over this this loop. Another thing I wanted to mention is the agent-to-agent protocol. So, here on the agents team we've had a lot of success with this protocol. So, this protocol being the protocol that Google created. Um kind of an open protocol for agents to intercommunicate, but um we found this very useful for uh defining our agent routes. So, for example, in the back end and our model and our schema to follow this kind of agent protocol. So, we modeled So, for example, there's this thing called an agent card which you see here and it's got the name of the agent, a description, etc., right? And having this kind of rigorous protocol, this rigorous spec really helped drive our development and drive alignment because, you know, all we had to do was um align with this spec and follow this spec and we knew that this was kind of the contract that our front end and back end would both consume and and produce. So, um this uh I would say also has been uh very helpful for us. And And what's really cool is A2A has a lot of extensions, right? So, you could extend the protocol uh add in like metadata. Uh
Comments
Checking sign-in…
Loading comments…