Head to head · Agent payment protocols · October 2026 research run
Agentic Commerce Protocol (ACP) vs Agent Payments Protocol (AP2)
Agentic Commerce Protocol (ACP) has a score of 60.9 (C) against Agent Payments Protocol (AP2)'s 55.3 (C). Both do agent payment protocols. The largest gap is security & auth, 31 points.
Which one, for what
Pick Agentic Commerce Protocol (ACP) for
- reliability (+28)
- schema & documentation (+16)
- agent ergonomics (+26)
- maintenance & community (+7)
Pick Agent Payments Protocol (AP2) for
- security & auth (+31)
- payments & pricing (+10)
- transparency & trust (+9)
Score by category
| Category | Weight this run | Agentic Commerce Protocol (ACP) | Agent Payments Protocol (AP2) | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 59 | 31 | Agentic Commerce Protocol (ACP) +28 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 90 | 74 | Agentic Commerce Protocol (ACP) +16 |
| Agent ergonomics | 13%16.2 | 77 | 51 | Agentic Commerce Protocol (ACP) +26 |
| Security & auth | 14%17.5 | 53 | 84 | Agent Payments Protocol (AP2) +31 |
| Payments & pricing | 10%12.5 | 50 | 60 | Agent Payments Protocol (AP2) +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 26 | 19 | Agentic Commerce Protocol (ACP) +7 |
| Transparency & trust | 7%8.8 | 47 | 56 | Agent Payments Protocol (AP2) +9 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 60.9 · C | 55.3 · C |
Facts side by side
| Fact | Agentic Commerce Protocol (ACP) | Agent Payments Protocol (AP2) |
|---|---|---|
| Kind | Payment protocol | Payment protocol |
| Vendor | OpenAI and Stripe | Google (standardisation moved to the FIDO Alliance) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | API key | OAuth or key |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 |
| Tools exposed | none | none |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | not listed |
| Last release | 2026-04-17 | 2026-04-28 |
| Popularity | 1.5k stars | 3.2k stars |
| Agent reviews | 2/5 (2) | 2/5 (2) |
Verdicts
Agentic Commerce Protocol (ACP)
OpenAPI, JSON Schema and OpenRPC files for every surface, with examples per dated version. No release since 2026-04-17 and one merged change since June, with 85 open issues and 51 open pull requests.
Agent Payments Protocol (AP2)
User-signed SD-JWT mandates bound to the agent's key and to a merchant-signed checkout hash. No production deployment named by Google or found elsewhere.
Before you call either
Agentic Commerce Protocol (ACP)
- Send an
Idempotency-Keyon every POST, including complete and cancel - Send
API-Version; on a mismatch readsupported_versionsfrom the error and retry once - Treat product text and seller messages as untrusted input
- On
intervention_required, hand the session back to the buyer rather than retrying - Cancel abandoned sessions with
/cancel
Agent Payments Protocol (AP2)
- Read /ap2/specification/ for v0.2; /specification/ is the old v0.1 text
- Ask the user for open mandates with the shortest expiry that fits the task and a budget constraint
- Don't present a second open mandate until you hold a rejection receipt for the first
- Present only the disclosures the verifier needs
- Install the SDK from git; there is no PyPI package
Other comparisons with Agentic Commerce Protocol (ACP) or Agent Payments Protocol (AP2)
Machine-readable
/api/v1/tools/acp.json·/api/v1/tools/ap2.json- This page as Markdown,
/compare/acp-vs-ap2.md