---
language: en
title: "Universal Commerce Protocol"
description: "UCP organizes commerce capabilities between platforms and sellers. Discovery, checkout, and payment authorization have distinct roles and checks."
canonical: "https://tropk.ai/en/resources/glossary/universal-commerce-protocol"
last_modified: "2026-10-12T16:10:35.087Z"
---

# Universal Commerce Protocol

Reviewed on 2026-10-07.

## What it means

Universal Commerce Protocol, or UCP, is an open protocol for commerce interactions between platforms, agents, and businesses. It organizes services, capabilities, and extensions for operations such as catalog queries, carts, checkout, and orders. The documentation consulted in October 2026 presents the 2026-08-25 release, with profiles that declare versions and features available for negotiation between parties.

## Why it matters for marketing

For commerce marketing, UCP helps define the scope of an integration beyond the promise of being available to agents. A store can offer catalog queries without offering every checkout option. The team needs to know which capabilities have been implemented and accepted by the platform before advertising a complete purchase journey.

## Example in practice

Imagine a store offering checkout and a discount on a lamp purchase. The platform profile accepts checkout, but not the discount extension in the same version. By examining the negotiated capabilities, the team would realize that the lamp promotion requires another purchase path, without promising the discount in that incompatible flow.

## How to apply or verify

Check the profile published at /.well-known/ucp, the selected version, and the schemas for the advertised capabilities. Then compare these declarations with the negotiation response and a corresponding checkout session. Development and commerce operations should verify totals and active extensions together. The specification requires compatibility by exact version, not just by date order.

## Important distinctions

Discovering capabilities does not authorize a purchase or confirm payment. UCP can use different transports and negotiate the optional [AP2](/en/resources/glossary/agent-payments-protocol) mandates extension for proofs of consent and integrity. This extension should not be assumed in every session. The name Universal does not guarantee support on every platform, in every country, or with every payment method; each integration needs to demonstrate its scope.

## Sources and references

- [Universal Commerce Protocol](<https://ucp.dev/>) — Universal Commerce Protocol
- [Core Concepts — Universal Commerce Protocol](<https://ucp.dev/documentation/core-concepts/>) — Universal Commerce Protocol
- [Universal Commerce Protocol — Official Specification](<https://ucp.dev/latest/specification/overview/>) — Universal Commerce Protocol

## Continue a leitura

- [Agent Payments Protocol](</en/resources/glossary/agent-payments-protocol>)
- [Agentic Commerce Protocol](</en/resources/glossary/agentic-commerce-protocol>)
- [Model Context Protocol](</en/resources/glossary/model-context-protocol>)

## About the author

[Vinicius Pacheco](</en/team/vinicius-pacheco>)

Responsible for Tropk’s technical content, focusing on crawling, indexing, structured data, and agent access to content.

---

[All pages in Markdown](<https://tropk.ai/sitemap.md>)