Verification register Agentic Commerce & Payments
Current reading
The readiness gap, in one scan
AI-assisted assembly · derived results
- Claimed
- 68
- Reported
- 60
- Verified
- 51
- Gap
- +17
Public ambition and stated capability
Observed practitioner reporting
Independently supported evidence
Claimed minus verified
Evidence strength Critical
Decision
What the current evidence supports
Human editorial judgment · 2026-06-28
Proceed with caution
- Why
- UCP is a Tier-3-backed open standard with very-high coalition support (a 10-member Tech Council now including Google, Shopify, Amazon, Meta, Microsoft, Salesforce, Stripe, Etsy, Target, Wayfair) and live checkout with marquee US retailers, directly intersecting our protocol layer. But the unresolved UCP/ACP/Amazon fragmentation and incomplete Lodging/Food specs mean committing engineering to a single stack now still risks rework.
- Next
- Track the ucp.dev Shopping spec (now v2026-04-08) and AP2 payment-handler interface against our UCP Credential Provider (Rule #29 protected); prototype a read-only catalog/checkout adapter behind a feature flag against the /.well-known/ucp discovery mechanism. Do NOT commit to UCP-vs-ACP exclusivity — design the adapter so both protocols can be served.
Constraints
Blockers
No named blocker is present in the current public projection.
Evidence summary
Derived counts
AI-assisted assembly
- Total
- 6
- Tier 1
- 1
- Tier 2
- 2
- Tier 3
- 3
- Supports
- 4
- Contradicts
- 2
- Context
- 0
- Latest observed
- 2026-06-17
Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.
Publication record
Revisions
Initial public reading
This is the initial public reading. No earlier readiness change is recorded.