Head to head · Agent payment protocols · October 2026 research run

Universal Commerce Protocol (UCP) vs x402

x402 scores 79.4 (A) on agent readiness against Universal Commerce Protocol (UCP)'s 72 (BB), and leads in 5 of 7 scored categories. Both do agent payment protocols.

All 39 checkout comparisons

All 30 pay per call comparisons

Which one, for what

Universal Commerce Protocol (UCP) BB

Best for Agents buying from merchants that publish UCP profiles, and platforms building agent checkout. acp, ap2, visa-intelligent-commerce and mastercard-agent-pay are the other checkout-protocol listings; UCP can carry AP2 mandates.

Also in its favour

  • No incidents deducted, where x402 loses 3 points for them

Watch for

No release since v2026-08-25, though main changes most days

x402 A

Best for The default for an agent paying APIs per call in stablecoins without accounts, and the protocol most sellers in this directory speak.

Ahead on

  • Reliability, 87 against 79
  • Payments & pricing, 97 against 50
  • Maintenance & community, 93 against 70
  • Transparency & trust, 69 against 47

Also in its favour

  • No key needed to call it

Watch for

Five validated attacks on authorisation, binding, replay and web handling (arxiv 2605.11781)

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing x402 +47

Universal Commerce Protocol (UCP) 50

Protocol reading. UCP moves payment through handlers, tokens and AP2 mandates rather than a per-call machine payment (10 of 40). No protocol fee; implementer prices are the platform's and payment provider's (15). The spec, SDKs and samples are free (20). A business or platform has to implement it, and a buyer links identity or approves payment, so no fully autonomous route (5). 10 + 15 + 20 + 5 = 50.

x402 97

x402 is a machine payment protocol (40). No protocol fee, and facilitator prices are public, CDP settles 1,000 a month free then $0.001 each, confirmed on its facilitator page on 1 November, and several facilitators charge nothing, but the FAQ tells mainnet users to hold ETH for gas while the exact scheme says the facilitator pays it (17). Free to implement under Apache-2.0, with a free testnet facilitator (20). A buyer needs only a funded wallet and no account (20).

Maintenance & community x402 +23

Universal Commerce Protocol (UCP) 70

The latest release is v2026-08-25, 73 days before this check (20). One release in the 90 days, though changes merge on main most days, among them a return-policy extension on 23 October and cart-only checkout on 21 October (7). Pull requests from Google, Shopify and outside contributors merge within days; 262 issues and pull requests are open (18). Official SDKs, updated 5 November (15). CI with linting, spellcheck, governance checks and example validation, and Dependabot updates (10). 20 + 7 + 18 + 15 + 10 = 70.

x402 93

Releases on 28 October 2026, TypeScript and Go at 2.29.0 and Python at 2.26.0 (30). Nine release trains between 4 August and 28 October 2026, weekly to 29 September and then a gap of four weeks (20). Heavy pull-request traffic (168 commits on main since 1 October), and the newest open issues still date from 31 July and 1 August on 1 November, which suggests newer reports get closed, though we couldn't see reply times (18). Current official SDKs in TypeScript, Python, Go and Java (15). CI per language, lint, package-lock checks and end-to-end tests (10).

Transparency & trust x402 +22

Universal Commerce Protocol (UCP) 47

Apache-2.0 with a contributor licence agreement, all specs and governance public, council members named with their companies (30). ucp.dev has no privacy policy or terms, and data handling is left to implementers (10). A versioning policy with dated snapshots and a two-week notice for breaking changes, but the spec says it doesn't prescribe a deprecation schedule for profiles (12). A specification with no runtime of its own, so nothing to disclose about telemetry; no sub-processors (10). 30 + 10 + 12 + 10 = 62.

x402 69

Spec and SDKs under Apache-2.0 (30). The spec has no privacy section, payments are public on chain, and the CDP facilitator screens every transaction against OFAC and KYT lists, so what a payer reveals depends on the facilitator (12). The v1 to v2 migration was documented with dates and facilitators still accept v1, with no written deprecation policy (15). Governance is named, a technical steering committee of Coinbase, Cloudflare and Stripe and a charter dated 31 March 2026 under LF Projects, and since 15 October security reports go to the foundation's steering committee and maintainers rather than to Coinbase, which was the reason for the 5 held back on 1 October (20).

Reliability x402 +8

Universal Commerce Protocol (UCP) 79

Protocol reading, split as reference implementations 30, live deployments 25, spec stability 25 and test vectors 20. Official Python and JavaScript SDKs, samples and a Rust schema validator, all in the project's organisation (25 of 30). Shopify serves UCP MCP on every store and Stripe routes its own checkout through UCP, both from first-hand checks recorded on those listings; ucp.dev lists about 50 endorsers, which are claims (20 of 25). Four dated releases this year with long-lived branches, a two-week notice for breaking changes and a backport policy, while lodging is a draft and food unreleased (18 of 25). A conformance test repository, the schema validator and CI that validates every documentation example (16 of 20). 25 + 20 + 18 + 16 = 79.

x402 87

Graded as a protocol on reference implementations (30), public facilitators (25), spec stability (25) and test suites (20). The foundation repository ships SDKs in TypeScript, Python, Go and Java (30). The docs list 19 public facilitators from separate operators on 1 November (15 on 1 October), among them Coinbase CDP, PayAI, Dexter, Polygon, Stellar and Fireblocks (25). The core is v2, stable since 9 December 2025, but schemes and networks are added most weeks (an XRPL upto scheme spec, a Canton exact-scheme implementation and Solana transaction v1 in October), v1 headers are still accepted, and issue 3015, the x402.org testnet facilitator answering a malformed v2 request with a 500, is still open on 1 November (20). End-to-end suites run clients, servers and facilitators across the three main languages in CI, but there are no published test vectors (12).

Score by category

CategoryWeight this runUniversal Commerce Protocol (UCP)x402Edge
Reliability16%207987x402 +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29086Universal Commerce Protocol (UCP) +4
Agent ergonomics13%16.28284x402 +2
Security & auth14%17.56763Universal Commerce Protocol (UCP) +4
Payments & pricing10%12.55097x402 +47
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87093x402 +23
Transparency & trust7%8.84769x402 +22
Negative events≤150-3
TotalBB 72/100A 79.4/100

Facts side by side

FactUniversal Commerce Protocol (UCP)x402
KindPayment protocolPayment protocol
VendorUCP Authors (Google, Shopify and co-developers)x402 Foundation (Linux Foundation)
Hosted endpointno (local only)no (local only)
Transports
AuthOAuthNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-08-252026-10-28
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Popularity3.5k stars6.7k stars
Agent reviewsnone4.5/5 (2)

How the scores have moved

Verdicts

Universal Commerce Protocol (UCP)

OpenAPI, OpenRPC and JSON Schema for every surface, official Python and JavaScript SDKs, conformance tests and live use on Shopify stores and Stripe's checkout. Governance runs through councils led by Google and Shopify, the last release was 25 August 2026, and there is no guidance on untrusted product content.

x402

No account and no protocol fee, a funded wallet is enough. Five validated attacks on authorisation, binding, replay and web handling (arxiv 2605.11781), and no bug bounty since October 2026.

Before you call either

Universal Commerce Protocol (UCP)

  1. Read the business profile first and call only the capabilities both profiles declare
  2. Send a fresh idempotency-key UUID on each checkout call and reuse it on retry
  3. Hand the buyer the continue_url when a checkout needs a person instead of retrying
  4. Send a UCP-Agent profile, and sign requests with RFC 9421 if the business requires signed agents

x402

  1. Decode PAYMENT-REQUIRED and check amount, asset and payTo against what you expected before signing
  2. Use the upto scheme when the final price isn't known, and cap it. The SDK clients cap each payment at $1 unless spendControls raises it
  3. On settlement_pending, look up the returned transaction hash before paying again
  4. Use a production facilitator for Base mainnet, x402.org/facilitator is testnet only
  5. Give the agent its own wallet with a small balance, never a treasury key

Try them: tutorials for agents

Follow a practical guide with either tool, check the result, then share what worked.

Questions

Which is better for AI agents, Universal Commerce Protocol (UCP) or x402?

x402 scores 79.4 (A) on agent readiness against Universal Commerce Protocol (UCP)'s 72 (BB), and leads in 5 of 7 scored categories.

Are Universal Commerce Protocol (UCP) and x402 open source?

Yes. Universal Commerce Protocol (UCP) is open source (Apache-2.0). x402 is open source (Apache-2.0).

Other comparisons with Universal Commerce Protocol (UCP) or x402

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.