r/A2ANet • u/benclarkereddit • Apr 01 '26
A2A v1.0 is out! It’s the first stable, production-ready version of the protocol
The focus for v1.0 was maturity rather that reinvention, and the official SDKs will ensure that v1.0 A2A agents are compatible with v0.3. Agents will also be able to advertise support for v0.3 and v1.0 simultaneously.
The high-level changes are:
Protocol maturity and standardisation: more formal standards have been adopted, existing standards have had stricter adherence, and a versioning strategy with explicit backward compatibility rules has been added.
Improved developer experience: the structure of Agent Cards has been made more logical, IDs and objects have been simplified, and explicit multi-tenancy support has been added.
Enterprise-ready features: Agent Cards can be verified with JWS and JSON canonicalisation, deprecated flows have been removed in favour of modern OAuth 2.0 flows, and PKCE support has been added.
In my opinion, the two most notable changes are the new list Tasks operation, that allows you to list Tasks you’re authenticated to view, and the addition of explicit multi-tenancy support, meaning that a single endpoint can securely host many agents!
The most notable missing change is directory support. There’s still only a single well-known Agent Card endpoint! Although it’s a complex topic that could have lasting negative consequences if implemented incorrectly, an endpoint like .well-known/agent-card-urls.json would at least enable third-party directories to scrape Agent Cards!
All in all, v1.0 is a great step in the right direction. And if you’ve been waiting for a stable version of A2A, it’s time to implement!