What UCP is, and is not
UCP is not a general-purpose API framework. It is a domain-specific protocol for the complete agentic purchase journey: product discovery, inventory check, checkout, payment via AP2, and post-purchase management. It defines not just transport and format (REST + JSON-RPC), but also semantic conventions, what fields are required, what values are valid, what authentication model applies.
A general REST API can theoretically expose all the same capabilities, but without the standardized semantics, each AI agent would need a custom integration with each merchant's API. UCP's value is precisely its standardization: an agent that supports UCP can transact with any UCP-compatible merchant without custom development.
UCP vs custom REST APIs
| Dimension | Custom REST API | UCP |
|---|---|---|
| Standardization | Proprietary per merchant | Universal standard |
| AI agent support | Requires custom integration per agent | Any UCP-compatible agent works natively |
| Authentication | Varies (API keys, OAuth, etc.) | Standardized AP2 + agent certificates |
| Payment handling | Not included (separate payment API) | Integrated via AP2 tokenization |
| Discovery | Manual documentation | UCP registry + llms.txt |
| Time-to-integration | Days to weeks per agent | Minutes for any UCP-compliant agent |
If you already have a REST API, UCP is not a replacement, it's an additional standardized layer that exposes your capabilities to the agentic ecosystem. You keep your REST API for existing integrations; UCP opens a new channel.
UCP vs GraphQL
GraphQL is a query language that gives API consumers flexible control over what data they retrieve. It's excellent for client applications that need different data shapes for different views. UCP, by contrast, defines a fixed schema with specific required and optional fields.
For agentic commerce, GraphQL's flexibility is actually a drawback: AI agents benefit from predictable, consistent data structures they can learn once and apply universally. A GraphQL endpoint requires agents to know your specific schema; a UCP endpoint conforms to a universal schema they already understand.
That said, some merchants implement UCP on top of an internal GraphQL layer, using GraphQL for flexible internal data access and UCP as the standardized external interface. This is a sound architecture.
UCP vs punchout (cXML/OCI) for B2B
Punchout protocols (cXML from Ariba, OCI from SAP) have been the B2B e-procurement standard since the late 1990s. They allow enterprise buyers to "punch out" from their procurement system to a supplier's catalog, fill a cart, and return the order data to the buyer's system.
UCP's B2B mode addresses a similar problem but with significant differences: punchout requires a human to navigate the supplier's website; UCP allows an AI agent to interact with the supplier catalog programmatically. UCP also supports AP2 for payment, while punchout typically uses purchase orders and invoicing.
For suppliers already supporting punchout, UCP is not a replacement in the short term, enterprise procurement systems are slow to change. UCP opens a new channel for emerging AI-driven procurement tools while punchout continues serving legacy ERP workflows.
Migration strategy: adding UCP to existing infrastructure
The recommended approach for merchants with existing APIs:
- Audit existing endpoints: which of your current API endpoints cover catalog, inventory, checkout, and order management? These map to UCP's four core endpoint categories.
- Build a UCP adapter layer: create UCP-compliant endpoints that translate requests to your existing API format and translate responses to UCP's required schema. You don't rewrite your backend; you add a translation layer.
- Add AP2 support: the payment layer is the part most likely to require new implementation. Contact your payment processor (Stripe, Adyen, etc.) for their AP2 integration guide.
- Register in the UCP directory: submit your endpoint base URL to the UCP merchant registry at ucp.dev.
- Test and certify: run the official test suite and pursue UCP certification.
What you don't need to change
UCP does not require you to change your: payment processor (only add AP2 capability), order management system (UCP order data can feed your existing OMS via adapter), product information management (PIM exports become the source for UCP catalog), or customer service tools (UCP orders appear in your standard order management, not separately).