An open standard for platforms, agents, and businesses. Here is what it actually specifies, and what Pixerr does and does not support today.
UCP is an open commerce language. Pixerr is not a certified UCP integration. We are preparing the product model so we can speak that language later.
The Universal Commerce Protocol is an open standard for interoperability between consumer platforms (including AI agents and apps), businesses, payment service providers, and credential providers. The specification is published on ucp.dev and in the public GitHub repository.
Google documents how UCP is used on its surfaces in the Merchant Center UCP guide and in Under the Hood: Universal Commerce Protocol. Google’s reference implementation is aimed at direct buying in experiences such as AI Mode in Search and Gemini. That is Google’s product. It is not a Pixerr partnership, certification, or endorsement.
UCP is co-developed across the industry. Naming those companies as UCP participants is not a claim that Pixerr is one of them.
Agentic shopping breaks if every assistant has to scrape HTML and every merchant has to build a custom integration for every surface. UCP’s bet is a shared set of primitives: discovery, capability negotiation, checkout, identity linking, and order management, with the business remaining merchant of record.
Discovery of a business’s UCP profile happens at
/.well-known/ucp.
That profile declares protocol version, services, capabilities, and payment handlers.
Capability names use reverse-domain identifiers such as
dev.ucp.shopping.checkout.
Negotiation is server-selects: the business chooses the intersection of what both parties declared.
UCP’s shopping service is broader than “show a product card.” The public overview lists catalog search and lookup, cart building, identity linking (OAuth 2.0), checkout sessions, and order management with webhooks for status, tracking, and returns. Transports include REST (OpenAPI), MCP (OpenRPC), A2A, and an embedded checkout path. Payments are designed to interoperate with Agent Payments Protocol (AP2) rather than inventing a new wallet from scratch.
Google currently describes two integration styles on its surfaces: native checkout against the seller’s checkout API, and an optional embedded checkout for approved merchants with more complex UI. Roadmap items such as richer multi-item carts and post-purchase support are documented by Google as upcoming, not as something Pixerr should claim.
If “sell everywhere” depends on Pixerr rebuilding checkout for every assistant, we will fail. An open protocol is how a small platform participates without pretending it can out-integrate the entire internet. Our bet is: keep one honest product record, then adapt it.
Creators should not have to implement UCP. That is the point of the platform.
Start creating
