Is UCP a competitor to x402?

Not directly. UCP standardises agent shopping, checkout, and order management, while x402 standardises payment for individual HTTP requests. UCP does not settle payments itself, and builders have combined UCP for commerce logic with x402 for settlement. They address different layers of agentic commerce.

Google announced the Universal Commerce Protocol on January 11, 2026, co-developed with retailers and commerce platforms including Shopify, Etsy, Wayfair, Target, and Walmart, with payment companies among endorsing partners. It is open source and compatible with Google's Agent Payments Protocol.

Should an API provider use UCP or x402?

An API provider charging per request should use x402 or a similar HTTP 402 payment protocol, since UCP targets retail shopping journeys rather than metered resource access. Providers of physical or retail goods selling through shopping agents are the main audience for UCP.

x402 vs UCP: Payment Layer vs Commerce Layer

x402 and UCP work at different layers. x402 is a payment protocol that uses HTTP 402 to request and verify payment for a resource, usually in stablecoins like USDC. UCP, Google's Universal Commerce Protocol announced in January 2026, standardises the shopping journey for agents: checkout, identity linking, and order management. UCP does not settle payments itself.

What x402 contributes here

x402 lets a server respond to a request with HTTP 402 Payment Required and machine-readable payment terms. The client pays, typically USDC on a network such as Base, and retries with proof. A facilitator can verify and settle the payment. It suits APIs, data, and digital resources priced per request.

What UCP does

Google announced the Universal Commerce Protocol on January 11, 2026, co-developed with major retailers and commerce platforms and endorsed by payment networks and processors. UCP defines capabilities for agent shopping such as checkout, identity linking, and order management, and runs over REST, MCP, or A2A.

Different layers

UCP answers what is being bought, from whom, and how the order is managed. x402 answers how a specific request is paid for and proven. A shopping agent buying a physical product through a retailer fits UCP; an agent paying a few cents for a data lookup fits x402.

Payment handling in UCP

UCP separates payment instruments, such as a card or wallet, from payment handlers that process them. That design lets merchants support various payment methods without the protocol settling funds itself. It is compatible with Google's Agent Payments Protocol for proving user authorisation.

Combining them

Third-party builders have described stacks that use UCP for cart and commerce logic and x402 for stablecoin settlement. This is an implementation choice rather than an official Google integration, but it shows the protocols are complementary rather than competing.

Which to adopt

Retailers and commerce platforms selling goods to shopping agents should look at UCP. API and data providers charging per request, and agent builders paying for resources, should look at x402. Platforms serving both can support both.

Who governs x402 vs UCP

UCP is open source on GitHub, led by Google with retail partners. x402 is governed through the x402 Foundation under the Linux Foundation, with members spanning payment networks, cloud providers, and crypto companies.

A combined example

A procurement agent for a business orders office supplies through a retailer that supports UCP, using the retailer's checkout and order management. While researching options, the same agent pays a product data API per lookup using x402. UCP governs the order; x402 governs the metered data purchases. The agent's wallet and policy limits apply to both.

Developer effort

Implementing UCP means exposing commerce capabilities such as checkout and order status in the protocol's format, often through a commerce platform that supports it. Implementing x402 means adding middleware to endpoints that returns 402 terms and verifies payment, often with a facilitator handling settlement. The x402 path is typically lighter for API providers.

Security considerations

UCP's identity linking and AP2 compatibility help merchants confirm that an agent acts for a real customer. x402 relies on payment verification before serving a response, which protects the provider. In both cases, the paying agent's own limits protect the payer.

Where the ecosystem may go

As agent commerce matures, expect commerce protocols such as UCP and ACP to reference payment protocols for settlement, and payment protocols such as x402 and MPP to interoperate. Building on open, layered protocols keeps options open as these connections form.

Aspect	x402	UCP
Layer	Payment per request	Commerce journey and checkout
Typical use	APIs, data, digital resources	Retail shopping by agents
Settlement	Stablecoins, verified per request	Delegated to payment handlers
Transport	HTTP 402	REST, MCP, or A2A
Origin	Coinbase, now x402 Foundation	Google with retail partners

Frequently asked questions

Is UCP a competitor to x402?: Not directly. UCP standardises agent shopping, checkout, and order management, while x402 standardises payment for individual HTTP requests. UCP does not settle payments itself, and builders have combined UCP for commerce logic with x402 for settlement. They address different layers of agentic commerce.
Who created UCP?: Google announced the Universal Commerce Protocol on January 11, 2026, co-developed with retailers and commerce platforms including Shopify, Etsy, Wayfair, Target, and Walmart, with payment companies among endorsing partners. It is open source and compatible with Google's Agent Payments Protocol.
Should an API provider use UCP or x402?: An API provider charging per request should use x402 or a similar HTTP 402 payment protocol, since UCP targets retail shopping journeys rather than metered resource access. Providers of physical or retail goods selling through shopping agents are the main audience for UCP.