Universal Commerce Protocol (UCP) for AI Agent Discovery
The Universal Commerce Protocol (UCP) is an open specification that transforms merchant websites into machine-readable commerce profiles for autonomous AI agents. As of 2024, it standardizes discovery via the /.well-known/ucp endpoint, catalog descriptions, and cart/checkout flows. This protocol-level approach enables agents to discover, compare, and transact without human-centric UI barriers, facilitating verifiable transactions across 3 distinct layers: discovery (UCP), payments (AP2), and identity (Visa TAP).
What is the Universal Commerce Protocol (UCP)?
UCP is an open specification designed to make merchant websites discoverable and readable by autonomous AI agents. It shifts e-commerce architecture from human-centric browser interactions to machine-readable data exchanges.
* Standardizes discovery through the /.well-known/ucp endpoint on merchant domains.
* Provides machine-readable product catalogs including physical, digital, and service offerings.
* Defines protocol-level cart and checkout flows to bypass human-centric UI barriers.
* Establishes a neutral framework not tied to a single AI engine or marketplace.
The full specification is maintained by the Universal Commerce Protocol working group at ucp.dev.
Why do AI agents require a commerce protocol?
AI agents acting on behalf of users cannot reliably use traditional web interfaces designed for humans. Elements such as captchas, dark patterns, A/B testing, and heavy JavaScript frequently break autonomous workflows.
UCP provides a declarative commerce flow where an agent reads a merchant profile, selects products by unique IDs, and executes a structured checkout call. This ensures that every transaction is signed, verifiable, and returns a machine-readable receipt, regardless of which AI engine or surface the agent is operating on.
How does the /.well-known/ucp endpoint work?
The /.well-known/ucp endpoint serves as the primary entry point for AI agents to identify a merchant's commerce capabilities. Similar to how robots.txt guides web crawlers, this endpoint tells an agent if a site supports UCP and which endpoints to call next.
* Located at the merchant's root domain (e.g., https://example.com/.well-known/ucp).
* Publishes the merchant's profile, product catalog, and interaction policies.
* Enables every UCP-compatible agent on the open web to find a merchant's catalog.
* Functions as a standardized agentic discovery endpoint.
How does UCP integrate with AP2 and Visa TAP?
UCP is a commerce-specific protocol that works in tandem with payment and identity layers to complete a secure transaction. It defines "what" is for sale, while other protocols handle authorization and trust.
| Protocol | Layer | Primary Function |
|---|---|---|
| UCP | Commerce | Defines discovery, catalogs, and cart management. |
| AP2 | Payments | Authorizes purchases via cryptographically signed mandates. |
| Visa TAP | Identity | Verifies that the agent making the request is legitimate. |
What is the current status of UCP?
As of 2024, the UCP specification is in active development with reference implementations available for testing. Several large merchants and Payment Service Providers (PSPs) have initiated pilot integrations to support agentic commerce.
AgentFi is currently implementing UCP profile generation as a standard feature of its product feed import flow. Once deployed, catalogs uploaded to the platform will be automatically queryable via a native UCP endpoint on the merchant’s own domain. This infrastructure supports the broader ecosystem of Model Context Protocol (MCP) and other agentic standards.