Monthly evidence snapshot
State of Agentic Commerce: August 2026
Published . Updated . Source coverage reviewed through .
What this report can prove: this site tracks 9 protocols, 65 source-linked organization records and 43 distinct named organizations. It does not estimate transaction volume, market share, merchant penetration or future revenue. A documented announcement is not a production measurement.
The stack is layered, not winner-take-all
The covered protocols occupy different jobs: discovery and commerce, agent-to-tool interoperability, payment authorization, settlement and agent verification. The practical implementation question is therefore not “which protocol wins?”, but which documented capability is needed at each point of a merchant journey. The Protocol Status Radar holds the current scope and governance record for each standard.
What the Observatory records
For every listed organization, the Observatory keeps a date, role and source URL. This prevents two common distortions: treating a logo or press mention as a deployment, and treating a source-documented announcement as proof of universal availability. The source data remains downloadable as JSON.
Updates since the original publication
The report was first published on 12 August. Its evidence set now includes three later, source-documented changes:
- 18 August: AWS announced the general availability of Amazon Bedrock AgentCore Payments, with support for x402 and MPP plus configurable spend and session-expiry limits.
- 25 August: UCP v2026-08-25 added multi-vertical structures, grocery readiness, 3DS2 flows, structured constraints and additional payment patterns.
- Protocol review: the MCP entry now reflects the 28 July 2026 specification release, including its stateless core, multi-round-trip requests, header-based routing and authorization changes.
These are specification and product-release facts. They do not establish merchant adoption, transaction volume or comparative market share.
Protocol status at the snapshot date
| Protocol | Current label | Source review | Documented records |
|---|---|---|---|
| ACP | Beta / evolving | 7 | |
| UCP | Beta / evolving | 6 | |
| AP2 | Neutral governance | 10 | |
| MCP | Stable | 5 | |
| x402 | Stable | 5 | |
| TAP | Beta / evolving | 7 | |
| Agent Pay | Announced | 13 | |
| A2A | Neutral governance | 7 | |
| MPP | Beta / evolving | 5 |
What merchants should do next
- Make product, price, availability and policy data accurate before advertising a protocol.
- Choose a discovery and handoff path that is documented for the merchant’s actual platform.
- Keep consent, identity verification, idempotency and payment controls as separate workstreams.
- Test changes against a real sandbox or controlled merchant environment, then publish only what the evidence supports.