Universal Commerce Protocol (UCP) Integration
Make your store buyable inside AI agents. Any UCP-compatible agent can discover products, build a cart, and check out without custom integration per agent, and you stay the merchant of record.
Virto Commerce ships a native adapter for the Universal Commerce Protocol (UCP)—an open, Google-led standard for agentic commerce. Any UCP-compatible AI agent can discover your products, build a cart, and complete checkout, and your store stays the merchant of record.
Instead of building a bespoke integration for every AI surface, your store speaks one standard that agents already understand, covering discovery, cart, and checkout in a single adapter.
One adapter, unlimited agents: Claude, Gemini, and any future UCP-compatible shopping agent connect through the same adapter, with no per-agent custom work.
How UCP Integration Works in Virto Commerce
Building and maintaining a custom integration for every AI shopping surface doesn’t scale. Each new agent means new adapter code, tested and maintained indefinitely.
Virto’s UCP adapter delegates every request to Virto’s own commerce APIs, so pricing, catalog rules, and checkout logic stay authoritative. It forwards requests to your existing systems instead of reimplementing their logic.
- REST surface: Standard discovery and transaction endpoints any UCP-compatible agent can call.
- Native MCP endpoint: Agents like Claude connect directly via Model Context Protocol.
- Vendor-neutral: Any UCP-compatible agent works—no Virto-specific coding.
- Flow: AI Agent → UCP Endpoint → Virto Adapter → Catalog/Cart/Checkout APIs.
What UCP Integration Delivers for Your Business
- Reach AI shopping surfaces without a rebuild: Expose the catalog, cart, and checkout you already run to any UCP-compatible agent.
- Stay the merchant of record: You keep checkout, data, pricing, and the customer relationship, and the adapter delegates without taking over.
- One standard, not per-agent integrations: No bespoke adapter to build and maintain for every new AI surface.
- Built to outlast one agent: An adapter for an open standard, not a proprietary interface—new agent surfaces plug in without new adapter code on your side.
UCP Use Case Examples
- Consumer AI shopping: A buyer asks their AI assistant to find and purchase a product—the agent completes checkout directly against your store.
- B2B procurement agents: A customer’s procurement agent reorders against contract pricing without a human placing the order manually.
- Multi-agent catalog exposure: A brand exposes its catalog to several AI assistants at once through the same adapter, instead of building a connector per assistant.
- Distributor discoverability: A distributor’s catalog becomes agent-discoverable without adding new middleware.
Watch Our Video for More Information
Make your catalog buyable everywhere AI agents shop, without building and maintaining a connector for each one. Discover more in Virto’s user guide.
Your Questions, Answered
Yes. The UCP adapter delegates every request to Virto’s own commerce APIs, so your pricing, catalog rules, checkout, and customer data stay exactly where they are. Agents transact through you; you don’t hand off the relationship.
Any UCP-compatible agent. The native MCP endpoint supports clients like Claude Desktop directly, and the adapter’s REST surface works with any agent built to the UCP standard.
No. The adapter delegates to your existing commerce APIs rather than replacing them. Your checkout, pricing rules, and catalog logic keep working exactly as they do today, for both human shoppers and AI agents.
UCP is the buy-side standard, meaning agents use it to discover products, build a cart, and complete checkout. onX is the order-operations standard, so it connects your platform to OMS, WMS, 3PLs, and agents for order, inventory, and fulfillment events after the sale. Together they cover both ends of agentic commerce.
No. UCP is an open, vendor-neutral standard co-developed by Google with a coalition of retailers and payment networks. Virto ships a native adapter for it—the standard itself belongs to no single vendor.
