Universal Commerce Protocol Proposes Open Rails for Agentic Commerce

Anurag Sinha, identified on the Open Source Summit North America 2026 schedule as a Senior Staff Software Engineer and Manager at Google and attributed on the Google Open Source Blog to Universal Commerce Protocol (UCP), delivered a keynote at Open Source Summit North America 2026 (Minneapolis, May 18-20) and published a June 16, 2026 architecture walkthrough post. The keynote and post describe UCP's design and explain why agentic commerce needs open infrastructure. UCP itself launched in January 2026 at NRF Retail's Big Show, co-developed by Google and Shopify, with endorsed partners including Walmart, Target, Etsy, Adyen, Mastercard, Stripe, and Visa (Google Developers Blog).

Per the Google Open Source Blog post, UCP uses a four-layer model to create a shared language for commerce:

• •Services organise domains such as shopping and common
• •Capabilities define core actions including checkout, catalog, cart, orders, and shared functions such as identity linking
• •Extensions keep capabilities configurable so features like fulfillment logic, loyalty, and post-purchase flows can be modelled once and reused across multiple flows rather than hardwired per merchant
• •Transport layer stays protocol-agnostic, supporting REST, Model Context Protocol (MCP), and Agent2Agent (A2A) bindings

The post frames these layers as enabling consumer platforms, agents, and businesses to advertise what they support, compose new behaviours, and communicate over the transport that works best for them (Google Open Source Blog).

The post cites an industry forecast from Bain estimating agentic shopping could account for roughly 10% to 25% of U.S. e-commerce by 2030 (Bain, cited in Google Open Source Blog). Commerce fragmentation - each merchant operating its own checkout, fulfillment, loyalty, and policy logic - is presented as the core integration problem UCP addresses, similar in intent to how identity (OpenID) and payment tokenisation standards reduced per-integration overhead in prior eras.

The post explicitly frames openness as a design principle: merchants, developers, and community contributors are invited to propose capabilities and extensions so the protocol reflects more than the needs of the largest players. The public GitHub repository is at github.com/Universal-Commerce-Protocol/ucp, and the project has published a Tech Council and reference consumer experiences built on the protocol (Google Developers Blog). The project home is ucp.dev.

• •Reference implementations and conformance tooling published to the public repository, which would confirm that agent behaviour can be validated against the schema across payment providers and fulfillment models.
• •Integration depth beyond the founding retail partners: smaller-merchant and platform SDKs would indicate ecosystem breadth rather than a large-partner-only standard.
• •Protocol-level security controls, since agentic completion of purchases raises authentication and liability questions distinct from browser-driven checkout flows.
• •MCP and A2A transport adoption in production, given those are the agent-native bindings most relevant to teams building on current agent frameworks.