[Protocol Hub](https://aizii.ai/protocol)/External Standard · UCP v1.0

# Google UCP: Universal Commerce Protocol

Breaking Commerce Data Silos with Semantic Graphing and Real-Time Updates.

Abstract

In the legacy web, commerce data is trapped in silos — proprietary databases hidden behind human-centric web pages. Google UCP (Universal Commerce Protocol) is the open standard designed to break these silos. It provides a unified, machine-readable language for product discovery, ensuring that an AI agent can retrieve accurate, real-time commerce data across any merchant platform without the need for custom API integrations.

01 — Technical Deep-Dive

## The Three Pillars of UCP

Google's blueprint for a machine-readable commerce graph.

01

### Semantic Product Graphing

UCP moves beyond keyword matching to represent products as a graph of verified attributes an AI can reason with. A standardized taxonomy turns marketing claims ("long battery life") into structured variables, enabling commerce-aware reasoning with 100% certainty of fit.

02

### The Push Model

The biggest failure in agentic commerce is recommending an out-of-stock item. UCP shifts the web from a Crawl model to a Push model — merchants push price and inventory changes to the global commerce graph the moment they happen. Every recommendation is Transaction-Ready.

03

### The Liquid Catalog

UCP enables Headless Commerce at global scale. Products are no longer confined to a PDP URL. Agents synthesize attributes into custom views for each user query and confirm compatibility in-chat — moving the user closer to settlement with zero page loads.

04 — Dynamic Attribute Discovery

### Outcome-Based Search

UCP allows models to map specific merchant data points to a broader Common Logic graph. Users no longer search for parts — they search for outcomes. UCP ensures your product is found when the agent identifies it as the solution to a complex user problem.

02 — The Protocol War

## UCP vs. ACP

Two rival standards. Two visions for the future of the web. They do not natively talk to each other.

Dimension

Google UCP

OpenAI ACP

Vision

Global Search Index

Private Conversation

Discovery Model

Crawl & query a structured graph

Direct model ↔ merchant API

Data Posture

Push: real-time merchant broadcasts

Pull: model invokes when needed

Settlement Path

Closed-loop via Google AP2

Open via x402 / proprietary rails

Merchant Surface

Liquid catalog, no PDP required

Conversational endpoint

Optimization Goal

Discoverability

Connectivity

The Silo Conflict: a merchant supporting only UCP is optimized for the Google ecosystem but remains functionally invisible to OpenAI-based agents. To succeed, merchants must be protocol-agnostic.

03 — Aizii Implementation

## The Multi-Protocol Adapter

Aizii's DDP acts as the universal translator between UCP, ACP, and every rail that follows.

### Parallel Semantic Broadcast

Aizii takes your single Source of Truth and broadcasts it in the dialect required by each protocol — mapping your data to the UCP Graph for Google while maintaining the ACP Pipe for OpenAI.

### Neutral Infrastructure

Manage your business logic once in Aizii. Aizii absorbs every breaking change from the AI giants so your backend never has to chase a protocol update again.

### Vendor De-Risking

By sitting between your store and the global protocols, Aizii ensures you are never locked in. You retain the power to trade with any agent, on any rail, at any time.

Ecosystem Rail

[Home](https://aizii.ai/) [Protocol Hub](https://aizii.ai/protocol)

[

\[DDP\]

Deterministic Data Protocol

](#)[

\[SVP\]

Semantic Verification Protocol

](#)[

\[FHP\]

Fiduciary Handshake Protocol

](#)[

\[OpenAI ACP\]

Agentic Commerce Protocol

](#)[

\[W3C x402\]

Agentic Settlement Standard

](#)[

\[MCP\]

Model Context Protocol

](#)