Official links
Relationships
| From | Type | To | Evidence |
|---|---|---|---|
| evt-ap2-github-spec | DISCUSSES | Observed | |
| evt-google-a2a-2025-04-09 | DISCUSSES | Verified | |
| evt-google-a2a-github | DISCUSSES | Observed | |
| evt-google-ap2-2025-09-16 | DISCUSSES | Verified | |
| evt-techcrunch-google-ap2-2025-09-16 | DISCUSSES | Reported | |
| BUILDS | a2a | Verified | |
| BUILDS | ap2 | Verified |
Recent events
Google publishes the AP2 specification in an open GitHub repo
The google-agentic-commerce/AP2 repository publishes the Agent Payments Protocol specification, including agent authorization. This is maintainer evidence of an implementation surface distinct from x402 HTTP headers.
ObservedSourceGoogle announces the Agent Payments Protocol (AP2)
On 16 September 2025 Google Cloud announced AP2, an open protocol developed with payments and technology firms so agents can initiate payments across methods. Google positions AP2 as usable as an extension of A2A and MCP, and as payment-agnostic rather than a stablecoin-only HTTP 402 overlay.
VerifiedSourceTrade press same-day coverage of AP2 is corroboration, not a primary source
TechCrunch reported Google’s AP2 launch on 16 September 2025, describing backing from merchants and financial institutions. zFinia treats this as TIER_C corroboration of an already TIER_A official announcement.
ReportedSourceGoogle publishes Agent2Agent as an interoperability bet
Google Cloud Next 2025 introduced Agent2Agent (A2A), an open protocol for agents from different vendors to exchange tasks and results. Public materials position A2A as complementary to MCP: MCP connects a model to tools; A2A connects agents to other agents.
VerifiedSourceGoogle publishes A2A in an open GitHub repository
The google/A2A repository is the public implementation and specification surface for Agent2Agent. It does not replace MCP tool calling and it does not replace x402 or AP2 payments.
ObservedSource
Source
verified · https://zfinia.com/methodology