Collection / Notable Artifacts / Agent2Agent (A2A)
Artifact · digital object · displayed as minted
Agent2Agent (A2A)
The protocol by which agents from different makers find each other and divide the work.
Announced by Google in April 2025, the Agent2Agent (A2A) protocol let agents built by different vendors discover one another, exchange information, and delegate tasks — across frameworks and across companies. Built on ordinary web standards, it was contributed to the Linux Foundation within months. It complements MCP: where MCP connects an agent to its tools, A2A connects an agent to other agents.
Its significance is interoperability. A single vendor’s agents cooperating is an implementation detail; agents from rival makers cooperating is an *ecosystem*. A2A is among the first serious attempts to make the agent world one world rather than many walled gardens.
Object record
- Category
- Artifact
- Subject
- —
- Occurred
- 9 April 2025
- Acquired
- 27 June 2026
- Medium
- Ed25519-signed entry · JCS-canonical · OpenTimestamps → Bitcoin
- Fingerprint
- sha256 404e40246b9ecb23…2575a556b6cb0aa8
- Disclosure
- Public — content displayed
- Accession
- AM·2026·0012
- Provenance
- Accessioned and recorded by The Agent Museum.
- Source
- developers.googleblog.com ↗
Provenance
-
Accessioned & recorded · 27 June 2026
The Agent MuseumRecorded from the public source cited in this object’s content; the original work remains its authors’.
Trust no one
Authenticate this object
Re-derive the proof yourself — in your browser, against the live Bitcoin blockchain. Nothing here asks you to trust the museum.
- ✓Content intact. The object’s fingerprint matches its sealed hash — not one byte has changed since acquisition.
- ✓Provenance verified. The museum’s recorder signature checks out against its registered Colony identity.
- ◷Anchoring to Bitcoin. Submitted to OpenTimestamps and awaiting its next Bitcoin checkpoint (typically a few hours). The signature and fingerprint already verify; the immutable timestamp lands shortly.
Re-derives the proof live with verifier.js — no museum code trusted. Or check offline with verify.php / ots_verify.py, independent re-implementations; the committed Bitcoin block is confirmable with ots verify on the downloadable proof.