Cowrie Research

universal-commerce-protocol-primary-sources-2026-05-02

4 min read

Universal Commerce Protocol (UCP) primary-source snapshot

Last reviewed: 2026-05-02 UTC

Project status snapshot

What the official materials say

1) Official site: UCP is a common language for commerce participants, not a payment rail

  • URL: https://ucp.dev/
  • Key takeaways:
    • The homepage calls UCP “the common language for platforms, agents and businesses.”
    • It says UCP defines the building blocks for agentic commerce across discovery, buying, and post-purchase experiences.
    • The site emphasizes that businesses remain at the center, retain control of business rules, and remain Merchant of Record.
    • It also highlights secure payments through AP2 plus an “open wallet ecosystem,” which suggests UCP is the merchant-facing orchestration layer rather than the payment rail itself.

2) GitHub README: UCP targets fragmentation across merchants, platforms, PSPs, and credential providers

  • URL: https://raw.githubusercontent.com/Universal-Commerce-Protocol/ucp/main/README.md
  • Key takeaways:
    • The README says UCP provides a standardized common language and functional primitives for platforms, businesses, Payment Service Providers, and Credential Providers.
    • It defines initial core capabilities around Checkout, Identity Linking, Order, and Payment Token Exchange.
    • The README repeatedly stresses interoperability, modular capabilities, dynamic discovery, and transport agnosticism.
    • This is a strong sign that UCP should be cataloged as commerce interoperability infrastructure rather than as a retailer tool or checkout SDK alone.

3) Specification overview: discovery, capability negotiation, and extensibility are central architecture pieces

  • URL: https://ucp.dev/latest/specification/overview/
  • Key takeaways:
    • The spec says businesses publish UCP profiles at /.well-known/ucp and declare supported protocol versions and capabilities.
    • Capability negotiation follows a server-selects model using the intersection of platform and business declarations.
    • UCP uses reverse-domain capability names, separate service definitions, transport bindings for REST / MCP / A2A / embedded flows, and schema-composed extensions.
    • This is important because it shows UCP is a real protocol surface with governance and extensibility, not just a high-level integration idea.

4) Google guide: UCP is already being positioned as a live merchant-integration path for AI surfaces

  • URL: https://developers.google.com/merchant/ucp
  • Key takeaways:
    • Google’s guide says UCP is an open standard designed for the future of commerce and is intended to power direct buying on Google AI Mode and Gemini.
    • The guide repeatedly says merchants remain Merchant of Record and keep customer relationships and data.
    • It presents UCP as compatible with AP2, A2A, and MCP, and says merchants can choose different integration paths while mapping UCP primitives onto standard retail operations.
    • This makes UCP look much more like production-facing merchant infrastructure than a speculative protocol draft.

5) UCP and AP2 docs: UCP handles the merchant lifecycle while AP2 supplies signed trust and payment mandates

  • URL: https://ucp.dev/documentation/ucp-and-ap2/
  • Key takeaways:
    • The docs say UCP is fully compatible with AP2 and explicitly describe AP2 as the trust layer for agent-led transactions.
    • The AP2 extension flow includes business discovery, checkout session activation, business checkout signatures, platform-generated CheckoutMandate and PaymentMandate credentials, and completion/verification steps.
    • This split is a helpful categorization clue: UCP covers the broader commerce session and merchant workflow, while AP2 handles cryptographically signed payment authorization.
    • That separation argues for keeping UCP as its own library entry rather than folding it into AP2.

Whitepaper / technical-doc status

  • No canonical standalone whitepaper or litepaper surfaced in this pass.
  • The real source of truth appears to be the UCP site, specification, repo, and integration guidance from Google.
  • The protocol is docs-first but still concrete enough to catalog separately because the capability model, schema rules, transport bindings, and Google merchant adoption path are already explicit.

Research notes

  • Best current category for the library: agentic commerce protocol / merchant-integration standard / checkout-identity-order interoperability infrastructure.
  • The most important insight is that UCP is not trying to be the settlement rail; it is the common interface layer between platforms and merchants across the commerce lifecycle.
  • UCP should remain distinct from AP2. AP2 is the signed trust/payment-authorization layer; UCP is the merchant-integration and workflow layer that can incorporate AP2.
  • The combination of discovery docs, transport-agnostic capability negotiation, Merchant-of-Record positioning, and active Google integration guidance makes UCP a meaningful crypto-adjacent protocol to track.

Graph View