Skip to content
Universal Commerce Protocol Brand hub · en
ConceptFrameworkUse CasesMethodologyManifesto
Why NowFor WhomFAQResourcesContact
FR Get in touch →

Concept

The framework for a world where agents are a third consumer.

Universal Commerce Protocol (UCP) describes the coherent set of conventions, semantic, operational, transactional and governance, that enable an AI agent to read, negotiate and complete a purchase on behalf of a human buyer.

A short definition

Universal Commerce Protocol (UCP): a conceptual framework describing the emerging infrastructure layer that makes commercial offerings readable, negotiable and actionable by autonomous software agents.

UCP is not a piece of software, nor a formal specification published by a standards body. It is a reading framework that aggregates, classifies and operationalizes the standards, protocols and rails emerging independently (schema.org, GS1, MCP, A2A, Stripe ACP, Visa Intelligent Commerce, OpenAI Apps SDK...) and gives them a shared grid.

Important distinctions

  • It is not a registered IETF/W3C standard. It is a reading framework, not an RFC.
  • It is not a product. Neither a SaaS nor a technical framework.
  • It is not a platform brand. The framework is platform-neutral by design.

Why a framework, not a stream of articles?

The technical developments making commerce accessible to agents, context protocols, payment tokens, enriched feeds, typed schemas, are currently covered piecemeal by product blogs, scattered specs and the generalist tech press. Everyone covers one piece. No one offers a grid usable in a board meeting.

UCP provides that grid: a stable vocabulary, four layers, a scoring method, and a corpus of use cases. That is what an institutional site should carry, not an editorial feed.

The four layers, in brief

  1. Semantic, make catalog data machine-addressable: Product, Offer, Policy, Availability, Brand, Review, inventory, eligibility.
  2. Agent, expose surfaces where an agent can query, propose, confirm: typed endpoints, MCP tools, A2A interactions.
  3. Transaction, make payment compatible with a delegated buyer: agentic intents, limits, agent identity, fiscal traceability.
  4. Governance, give the operator readable, versioned control over rules, eligibility, disputes and retention.

Each layer is detailed on the Framework page, with associated standards, maturity signals and audit checkpoints.

Five structural claims

  1. Commerce is becoming agent-addressable. Discovery, offers and payments are being exposed to machine clients alongside humans.
  2. SEO remains necessary but is no longer sufficient. Being rankable is a prerequisite; being retrievable and citable is the new goal.
  3. Platforms deliver the plumbing, not the data. Shopify, Stripe, Google, Amazon standardize the rails. Catalog quality remains the merchant's responsibility.
  4. Governance is the merchant's anchor point. Policy, pricing, eligibility, disputes: where the merchant retains control.
  5. The advantage is asymmetric and cumulative. A quality catalog exposed early to agents earns citations and delegated intents; the gap widens.

What the framework does not claim

  • That "AI will change everything tomorrow." The framework is maturity-aware: some layers are established, others emerging, others still prospective.
  • That a single standard will prevail. The framework describes an assembly, not a monolith.
  • That everything must be rebuilt. The framework shows where to invest marginally to gain addressability.

Who should read this framework

  • An executive who must allocate a data / catalog / AI budget for 2026-2027.
  • A commerce SaaS PM positioning their roadmap in response to agent adoption.
  • An analyst or VC evaluating an investment thesis in agentic infrastructure.
  • An innovation team preparing the organization for a reshaping of discovery.

Next steps: read Why Now for the timing analysis, or go directly to the Framework.