UCP Universal Commerce Protocol
Treat UCP as an evolving agent-commerce interoperability signal. Validate against primary specs before implementation.
SourceAgentic Commerce Protocol Timeline
Track UCP, ACP, AI shopping, and payment-provider signals as source-backed timeline entries.
Protocol map
What teams are tracking
ACP Agentic Commerce Protocol
Use ACP language carefully until implementation details and stewards are verified for a given merchant stack.
Source AI agents AI Shopping Agent Readiness
Focus on discoverability, structured product data, policy clarity, and monitoring before claiming protocol support.
Source Recent signals
Protocol and payment timeline
- Stripe leadership discusses AI shopping and agentic commerce
Merchants should track checkout-provider guidance before making heavy protocol claims.
- Google explains UCP under the hood
Teams should map protocol requirements to catalog, policy, checkout, and monitoring owners.
- UCP spec site gives implementation teams a reference point
Engineering owners should use spec pages as the source of truth when planning implementation.
- Mastercard brings AI checkout into agentic commerce conversation
Payment and ecommerce product owners should participate in readiness planning.
- Google and Shopify push a shared AI shopping standard
Merchants should audit product data, policy data, crawlability, and the ownership path for AI-shopping readiness.
- Shopify Engineering details UCP mechanics
Technical teams should monitor version changes and decide who owns UCP implementation details.