whatisgithub

What is ucp?

universal-commerce-protocol/ucp — explained in plain English

Analysis updated 2026-05-18

2,961PythonAudience · developerComplexity · 3/5LicenseSetup · easy

In one sentence

An open specification defining how businesses, payment providers, and AI shopping agents interoperate for online commerce.

Mindmap

mindmap
  root((UCP))
    What it does
      Commerce interoperability
      Standard checkout spec
      Agent discovery
    Key capabilities
      Checkout
      Identity linking
      Order updates
      Payment token exchange
    Use cases
      AI shopping agents
      Business integrations
      Payment providers
    Related
      Samples repository
      Conformance tests

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Design a business's checkout system so AI shopping agents can automatically discover and use it.

USE CASE 2

Standardize how a platform exchanges payment tokens and credentials with multiple payment providers.

USE CASE 3

Reference the specification when building or reviewing an agentic commerce integration.

What is it built with?

PythonRESTOAuth 2.0

How does it compare?

universal-commerce-protocol/ucpgoogle-agentic-commerce/ap2openmoss/moss-tts-nano
Stars2,9613,0013,032
LanguagePythonPythonPython
Setup difficultyeasymoderatemoderate
Complexity3/54/53/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 30min

This is a specification, not runnable software, implementation requires using the separate SDKs or samples repositories.

Apache 2.0: free to use, modify, and distribute, including commercially, as long as you keep the license and copyright notice.

So what is it?

The Universal Commerce Protocol, or UCP, is an open specification for how different systems in online commerce can talk to each other in a consistent way. Instead of each platform, business, payment provider, and credential provider building custom one off integrations, UCP defines a shared language and a set of building blocks so these systems can discover each other's capabilities and complete transactions reliably. The protocol is built around two ideas: Capabilities and Extensions. Capabilities are core commerce functions a business can implement, such as Checkout or Order, while Extensions add optional enhancements like discounts or fulfillment options without complicating the core definitions. Businesses declare which Capabilities they support in a standardized profile, which lets platforms, including AI shopping agents, automatically discover and configure themselves to work with that business. The initial release focuses on a few essential pieces: Checkout, which handles cart management and tax calculation with or without a human directly present, Identity Linking, which uses OAuth 2.0 to let a platform act on a user's behalf, Order, which delivers webhook based updates as an order is shipped, delivered, or returned, and Payment Token Exchange, which lets payment service providers and credential providers securely swap payment tokens. The protocol is described as transport agnostic, meaning businesses can expose these Capabilities through REST APIs, MCP, or A2A depending on what fits their existing systems. This repository is documentation and specification focused rather than a runnable application. It points to a separate samples repository for implementation examples and a conformance repository for testing whether an implementation follows the spec correctly. The protocol builds on existing open standards where possible, including support for AP2 payment mandates and verifiable credentials, and future plans mentioned in the README include expanding beyond shopping into areas like travel and services, plus adding loyalty program support. UCP is released as an open source project under the Apache 2.0 license.

Copy-paste prompts

Prompt 1
Explain how UCP's Checkout capability differs from its Order capability.
Prompt 2
Walk me through how Identity Linking works using OAuth 2.0 in UCP.
Prompt 3
Help me understand what a business needs to declare to support UCP's Checkout capability.
Prompt 4
How does UCP relate to the AP2 payment protocol mentioned in this README?

Frequently asked questions

What is ucp?

An open specification defining how businesses, payment providers, and AI shopping agents interoperate for online commerce.

What language is ucp written in?

Mainly Python. The stack also includes Python, REST, OAuth 2.0.

What license does ucp use?

Apache 2.0: free to use, modify, and distribute, including commercially, as long as you keep the license and copyright notice.

How hard is ucp to set up?

Setup difficulty is rated easy, with roughly 30min to a first successful run.

Who is ucp for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.