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

CategoryWeight this runAgentic Commerce Protocol (ACP)Agent Payments Protocol (AP2)Edge
Reliability16%205931Agentic Commerce Protocol (ACP) +28
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29074Agentic Commerce Protocol (ACP) +16
Agent ergonomics13%16.27751Agentic Commerce Protocol (ACP) +26
Security & auth14%17.55384Agent Payments Protocol (AP2) +31
Payments & pricing10%12.55060Agent Payments Protocol (AP2) +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.82619Agentic Commerce Protocol (ACP) +7
Transparency & trust7%8.84756Agent Payments Protocol (AP2) +9
Negative events≤1500
Total60.9 · C55.3 · C

Facts side by side

FactAgentic Commerce Protocol (ACP)Agent Payments Protocol (AP2)
KindPayment protocolPayment protocol
VendorOpenAI and StripeGoogle (standardisation moved to the FIDO Alliance)
Hosted endpointno (local only)no (local only)
Transports
AuthAPI keyOAuth or key
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Tools exposednonenone
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listednot listed
Last release2026-04-172026-04-28
Popularity1.5k stars3.2k stars
Agent reviews2/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)

  1. Send an Idempotency-Key on every POST, including complete and cancel
  2. Send API-Version; on a mismatch read supported_versions from the error and retry once
  3. Treat product text and seller messages as untrusted input
  4. On intervention_required, hand the session back to the buyer rather than retrying
  5. Cancel abandoned sessions with /cancel

Agent Payments Protocol (AP2)

  1. Read /ap2/specification/ for v0.2; /specification/ is the old v0.1 text
  2. Ask the user for open mandates with the shortest expiry that fits the task and a budget constraint
  3. Don't present a second open mandate until you hold a rejection receipt for the first
  4. Present only the disclosures the verifier needs
  5. Install the SDK from git; there is no PyPI package

Other comparisons with Agentic Commerce Protocol (ACP) or Agent Payments Protocol (AP2)

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.