{
 "acronym": "UCP",
 "adoption": {
  "by": "UCP project (ucp.dev launch-partner list)",
  "level": "claimed",
  "probe_run": null
 },
 "aliases": [
  "UCP"
 ],
 "analog": "Commerce API plus a machine-readable merchant capability document",
 "collisions": [],
 "discovery": {
  "mechanism": "well-known capability/profile document",
  "path": "/.well-known/ucp"
 },
 "dispute": null,
 "evidence": [
  {
   "claim": "UCP's own site lists co-development partners across Shopping (Google, Shopify, Etsy, Wayfair, Target, Walmart, Amazon, Microsoft, Meta, Salesforce, Stripe), Lodging (Amadeus, Booking.com, Expedia Group, Google, Hilton, Marriott, Trip.com), and Food (DoorDash, Google, Square, Toast, Uber Eats).",
   "date": null,
   "label": "VERIFIED",
   "url": "https://ucp.dev"
  },
  {
   "claim": "The GitHub org's central MAINTAINERS.md names a Shopping Tech Council (Google, Shopify, Etsy, Meta, Amazon, Microsoft, Target, Stripe, Salesforce) and a Food Tech Council (Google, Square, Toast, DoorDash, Uber Eats), governed per GOVERNANCE.md's Domain Tech Council / Governing Council model.",
   "date": null,
   "label": "VERIFIED",
   "url": "https://raw.githubusercontent.com/Universal-Commerce-Protocol/.github/main/MAINTAINERS.md"
  },
  {
   "claim": "UCP core concepts documentation defines discovery via a well-known capability document at /.well-known/ucp (also referencing /.well-known/oauth-authorization-server for identity linking), and states UCP is built on REST and JSON-RPC transports with AP2, A2A, and MCP support built in.",
   "date": null,
   "label": "VERIFIED",
   "url": "https://ucp.dev/documentation/core-concepts/"
  },
  {
   "claim": "The UCP GitHub repository describes UCP as an open standard for interoperability between commerce entities (platforms, businesses, PSPs, Credential Providers), with Capabilities such as Checkout, Identity Linking, Order, and Payment Token Exchange.",
   "date": null,
   "label": "VERIFIED",
   "url": "https://raw.githubusercontent.com/Universal-Commerce-Protocol/ucp/main/README.md"
  }
 ],
 "form": "well-known-file",
 "governance": "Domain Tech Councils (DTC) per vertical — Shopping Tech Council and Food Tech Council seated — under an overall Governing Council (GC); DTC seats held by Google, Shopify, Etsy, Meta, Amazon, Microsoft, Target, Stripe, Salesforce, Wayfair, Square, Toast, DoorDash, Uber Eats",
 "group": null,
 "history": [
  {
   "date": "2026-09-05",
   "note": "seeded from Exa Agent research run"
  },
  {
   "date": "2026-09-06",
   "note": "verified against ucp.dev (home, core-concepts), Universal-Commerce-Protocol/ucp README, and Universal-Commerce-Protocol/.github MAINTAINERS.md / GOVERNANCE.md"
  }
 ],
 "id": "ucp",
 "implementation": "multi-implementation",
 "last_verified": "2026-09-06",
 "name": "Universal Commerce Protocol",
 "native_status": "Open standard; specification expanding beyond Shopping into Lodging and Food",
 "origin": {
  "date": "2026-01",
  "org": "Google"
 },
 "part_of": null,
 "parties": [
  "agent-site"
 ],
 "phase": "living",
 "probe": {
  "method": "GET",
  "on_absent": "A missing or non-JSON response at /.well-known/ucp means the origin does not (yet) declare UCP capabilities; UCP also supports MCP/A2A transports, so a 404 on the well-known path does not rule out a business exposing UCP only via those channels.",
  "parse": "200 response with a UCP profile JSON document declaring supported Capabilities (e.g. Checkout, Identity Linking, Order) and Extensions",
  "path": "{origin}/.well-known/ucp"
 },
 "question": "Can an agent discover a business's commerce capabilities, build a cart, and check out interoperably across shopping, lodging, and food ordering?",
 "scope": "commerce",
 "spec_url": "https://ucp.dev/documentation/core-concepts/",
 "step": "pay",
 "summary_md": "The Universal Commerce Protocol (UCP) is an open standard, initiated by Google, that gives platforms (AI agents, apps, procurement systems) and businesses a common language and set of REST/JSON-RPC \"Capabilities\" — Checkout, Identity Linking, Order, Payment Token Exchange — so agentic commerce can work without bespoke, one-off integrations per merchant [3][4]. Businesses declare what they support in a machine-readable profile discoverable at a well-known path (`/.well-known/ucp`), and platforms use that to autonomously configure themselves for a given origin [3].\n\nUCP solves cross-vertical interoperability for agentic shopping, lodging, and food ordering by defining Capabilities and optional Extensions on top of transport-agnostic REST, MCP, or A2A bindings, and it explicitly builds on the Agent Payments Protocol (AP2) for payment authorization and OAuth 2.0 for identity linking rather than reinventing either [3][4]. It does not itself move money or replace a merchant's payment processor — the merchant remains \"Merchant of Record\" — and its Lodging and Food verticals are still described by the project as pending detailed specifications as of the current documentation snapshot [1].\n\nGovernance runs through per-vertical Domain Tech Councils (DTC) — a seated Shopping Tech Council and Food Tech Council as of this verification — operating under an overall Governing Council, with seats and maintainer nomination rights tied to actual contribution rather than fixed vendor slots [2]. Seated companies span Google, Shopify, Etsy, Meta, Amazon, Microsoft, Target, Stripe, and Salesforce (Shopping) and Google, Square, Toast, DoorDash, and Uber Eats (Food) [2]. UCP's own launch materials additionally name Walmart, Amadeus, Booking.com, Expedia Group, Hilton, Marriott, and Trip.com as co-development partners across Shopping and Lodging verticals, though Lodging has no seated council yet in the maintainers file [1][2].\n\nBecause every adoption figure available — the partner list, the council rosters — comes from UCP's own site and repository, adoption here is recorded as claimed by the UCP project rather than independently measured; nobody outside the project has published a count of live UCP-conformant merchant endpoints. What is unresolved: how many of the named partners have a working `/.well-known/ucp` profile live today versus having only committed to the initiative, and how UCP's scope divides from AP2 in practice given the two are designed to interlock.",
 "track": "vendor-consortium",
 "version": {
  "date": "2026-08-25",
  "label": "documentation site dated 2026-08-25; active/expanding specification (Lodging and Food detailed specs pending)"
 }
}