Skip to content

Pillar · Map

Standards, schemas and protocols

UCP is an open, versioned standard. Product schemas, transports, agent tools and payment networks form a wider ecosystem. This comparison separates their roles.

Editorial team · Updated : November 11, 2026

UCP is a published standard. The map below covers the wider ecosystem around it; the tools, vocabularies and networks listed are not automatically components of the UCP specification.

Every standard below is Established, Emerging, Probable or Speculative. Dates are the most recent relevant milestone at time of writing.

The standards map

Standard Plane Maturity Role
schema.org Product, Offer, AggregateRating Semantic Established Canonical vocabulary for product data on the open web.
schema.org MerchantReturnPolicy, ShippingRateSettings Policy Emerging Structured expression of returns and shipping.
GS1 GTIN Identity Established Global product identifier.
GS1 Digital Link Identity / Discovery Emerging Resolvable URLs carrying GS1 identifiers.
Google Merchant Center feed spec Product data Established Product attributes submitted to Merchant Center.
OpenAPI / GraphQL API interfaces Established OpenAPI describes HTTP API interfaces. GraphQL defines a query language and its execution rules.
MCP (Model Context Protocol) Agent tooling Emerging (2024-11) Standard for exposing tools and resources to LLM agents.
A2A (Agent-to-Agent) Agent tooling Emerging (2025) Horizontal communication between agents.
OpenAI Apps SDK Agent tooling / Discovery Emerging (2025) Expose apps inside ChatGPT; commerce apps included.
Claude Skills / MCP servers Agent tooling Emerging Skills give agents instructions and resources. MCP servers can expose tools and resources to agents.
Agentic Commerce Protocol (OpenAI / Stripe) Transaction Emerging (2025-09-29) Commerce protocol co-developed by OpenAI and Stripe, covering checkout interactions and delegated payment credentials.
Visa Intelligent Commerce Transaction / Identity Emerging (2025) Agent-bound card credentials with delegated authority.
Mastercard Agent Pay Transaction / Identity Emerging (2025) Agent identity + tokenized credentials.
PayPal agent tooling Transaction Emerging Agent endpoints, identity features.
llms.txt Discovery (generic web) Emerging Site-level guidance for LLM crawlers. Not commerce-specific.
robots.txt + user-agent strings Discovery Established Crawl access controls. Agent operators now declare UAs.
Sitemaps (XML) Discovery Established Enumerate canonical URLs for crawlers.
Verifiable Credentials / Decentralized Identifiers Trust Emerging Potential substrate for agent identity and merchant claims.

How the plane composition works

Read this diagram as a stack:

─────────────────────────────────────────────
  TRUST           Agent identity, merchant claims, provenance
                  (VC/DID, agent-UA fingerprinting, reviews)
─────────────────────────────────────────────
  TRANSACTION     Payment rails, order lifecycle
                  (ACP, Visa IC, Mastercard Agent Pay)
─────────────────────────────────────────────
  POLICY          Returns, warranty, shipping, restrictions
                  (schema.org MerchantReturnPolicy, ShippingRateSettings)
─────────────────────────────────────────────
  DISCOVERY       How agents find merchants / offers
                  (Feeds, sitemaps, MCP tools, Apps SDK, marketplaces)
─────────────────────────────────────────────
  SEMANTIC        Product, offer, variant, attribute meaning
                  (schema.org Product/Offer, GS1 attributes)
─────────────────────────────────────────────
  IDENTITY        Product, brand, merchant identifiers
                  (GTIN, MPN, GLN, GS1 Digital Link)
─────────────────────────────────────────────

No single spec covers all planes. Adoption is stack-by-stack.

Commerce protocols and payment networks

ACP is a protocol co-developed by OpenAI and Stripe, not the name of a card network. Visa Intelligent Commerce and Mastercard Agent Pay are payment offerings. A capability comparison must identify the product, operation, country and permissions.

ACP · Visa, 2026-10-20 · Mastercard, 2026-10-20

MCP vs A2A vs OpenAI Apps SDK

MCPA2AApps SDK (OpenAI)
DirectionAgent ↔ tools/resourcesAgent ↔ agentChat client ↔ app
SponsorAnthropic (open)Google (open)OpenAI
Use in commerceExpose catalog/order ops as toolsOrchestrate multi-agent buyingMerchant app inside ChatGPT
MaturityEmerging, growing ecosystemEmergingEmerging
Lock-in riskLow (open protocol)LowModerate (client-bound)

Gaps in the stack

The following points are questions for tracking interoperability between systems, rather than a normative list of features absent from UCP.

  • Policy interoperability across marketplaces. schema.org covers the open web; marketplaces each encode policies differently.
  • Dynamic price and stock freshness contracts. No cross-actor convention for "how fresh is this".
  • Agent attribution and commission. If an agent drives a sale, how is that recognized and remunerated?
  • After-sales for agents. Returns, disputes and warranty claims initiated by agents on behalf of users.
  • Trust signalling. Cross-platform merchant reputation that agents can verify.
  • Taxonomy reconciliation. Google Product Category, GS1 GPC, Amazon Browse Nodes, still distinct.

These are the gaps we will follow most closely on this site.

Where to go next

Deep dives

OpenAI / Stripe, ACP, 2025-09-29 · UCP 2026-08-25