{
 "acronym": "ACP",
 "adoption": {
  "by": "OpenAI and Stripe (project README)",
  "level": "claimed",
  "probe_run": null
 },
 "aliases": [
  "ACP",
  "Agentic Commerce Protocol"
 ],
 "analog": "Checkout API",
 "collisions": [
  "Agent Client Protocol (Zed)",
  "Agent Communication Protocol (IBM)",
  "ERC-8183 (also informally called Agentic Commerce Protocol)",
  "Agent Connect Protocol (AGNTCY)"
 ],
 "discovery": {
  "mechanism": "Bilateral capability negotiation (per RFC: capability_negotiation) between agent platform and merchant; no fixed well-known path published",
  "path": null
 },
 "dispute": null,
 "evidence": [
  {
   "claim": "ACP is an interaction model and open standard maintained by OpenAI and Stripe, currently in beta, using date-based versioning; the 2026-04-17 release added Cart, Feed, Orders, authentication and MCP support.",
   "date": "2026-04-17",
   "label": "VERIFIED",
   "url": "https://github.com/agentic-commerce-protocol/agentic-commerce-protocol"
  },
  {
   "claim": "Governance: a Technical Steering Committee of up to 7 org seats; OpenAI and Stripe are Founding Maintainers with veto power exercised only against violations of five named principles (mission, neutrality, security, protocol integrity, considered decision-making).",
   "date": null,
   "label": "VERIFIED",
   "url": "https://github.com/agentic-commerce-protocol/agentic-commerce-protocol/blob/main/docs/governance.md"
  },
  {
   "claim": "Meta has joined OpenAI and Stripe as a lead maintainer of the project.",
   "date": null,
   "label": "VERIFIED",
   "url": "https://github.com/agentic-commerce-protocol/agentic-commerce-protocol/blob/main/MAINTAINERS.md"
  },
  {
   "claim": "OpenAI publishes ACP-based Commerce documentation for building checkout flows in ChatGPT.",
   "date": null,
   "label": "REPORTED",
   "url": "https://developers.openai.com/commerce/"
  },
  {
   "claim": "Stripe publishes Agentic Commerce documentation implementing ACP for merchants.",
   "date": null,
   "label": "REPORTED",
   "url": "https://docs.stripe.com/agentic-commerce"
  }
 ],
 "form": "endpoint",
 "governance": "Technical Steering Committee (up to 7 org seats); OpenAI, Stripe, and Meta are lead maintainers, with OpenAI and Stripe as Founding Maintainers holding last-resort veto over mission, neutrality, security, and fork-integrity decisions",
 "group": "Protocols called ACP",
 "history": [
  {
   "date": "2026-09-05",
   "note": "seeded from Exa Agent research run"
  },
  {
   "date": "2026-09-06",
   "note": "verified against agentic-commerce-protocol GitHub repo (README, docs/governance.md, MAINTAINERS.md, spec/2026-04-17), developers.openai.com/commerce, docs.stripe.com/agentic-commerce"
  },
  {
   "date": "2026-09-06",
   "note": "collisions updated to add Agent Connect Protocol (Cisco/AGNTCY), verified against github.com/agntcy/acp-spec, spec.acp.agntcy.org"
  }
 ],
 "id": "agentic-commerce-protocol",
 "implementation": "multi-implementation",
 "last_verified": "2026-09-06",
 "name": "Agentic Commerce Protocol",
 "native_status": "Beta open standard, interaction model for connecting buyers, agents, and businesses",
 "origin": {
  "date": "2025-09-29",
  "org": "OpenAI and Stripe"
 },
 "part_of": null,
 "parties": [
  "agent-site"
 ],
 "phase": "living",
 "probe": {
  "method": "POST",
  "on_absent": "Absence proves nothing generalizable: ACP endpoints and auth are negotiated per integration and not advertised at a fixed public path, so a failed probe only shows this origin/path pair is not configured, not that ACP is unsupported.",
  "parse": "Response includes an API-Version response/negotiation and a CheckoutSession object per the 2026-04-17 OpenAPI schema",
  "path": "{origin}/checkout_sessions"
 },
 "question": "How do a buyer's agent and a merchant complete a deterministic, programmatic checkout without the agent becoming the merchant of record?",
 "scope": "commerce",
 "spec_url": "https://github.com/agentic-commerce-protocol/agentic-commerce-protocol",
 "step": "pay",
 "summary_md": "The Agentic Commerce Protocol (ACP) is an open, REST-based interaction model that lets a buyer's AI agent (a \"platform\" such as ChatGPT) complete a checkout with a merchant's existing commerce stack, while the merchant remains the system of record for orders, payments, tax, and compliance [1]. It solves the discovery-to-checkout hand-off for conversational and agentic shopping: a client negotiates capabilities, creates and updates a `CheckoutSession`, and completes or cancels it, with optional delegated-payment tokens (`/agentic_commerce/delegate_payment`) so an agent platform can pass a payment method to a merchant without becoming a payment processor [1].\n\nIt does not define blockchain settlement, on-chain escrow, or a payment rail of its own — payments continue to run over the merchant's existing PSP relationship, and ACP is scoped explicitly to checkout session lifecycle, feed ingestion, and payment-handler negotiation, not returns, tax computation, or fraud modeling [1]. It is also not a discovery protocol: there is no published well-known path for finding ACP support at an origin; capability negotiation is bilateral and appears to be arranged per integration (RFC: capability_negotiation), so it cannot be probed generically the way UCP's `/.well-known/ucp` can.\n\nAs of the current state (2026-09), the specification uses date-based versioning with a complete snapshot per release; the latest stable release is 2026-04-17, adding a push-model Feed API, multi-item checkout examples, and 3-D Secure authentication flows, with active development continuing in an `unreleased/` branch [1]. Governance sits with a Technical Steering Committee of up to seven organization seats, appointed by Founding Maintainers OpenAI and Stripe, who retain veto power scoped narrowly to five stated principles (mission, neutrality, security, protocol integrity, and considered decision-making) [2]. Meta has since joined as a third lead maintainer alongside OpenAI and Stripe [3].\n\nReference implementations exist from both founding maintainers: OpenAI's ChatGPT commerce surface and Stripe's Agentic Commerce integration, both documented on their respective developer sites [4][5]. Because the only adoption figures available come from the maintaining organizations' own materials, adoption here is recorded as claimed rather than independently measured. What remains unresolved: how \"beta\" status maps to production risk for merchants going live today, and whether the TSC's veto mechanism has ever been invoked in a real dispute.",
 "track": "vendor-consortium",
 "version": {
  "date": "2026-04-17",
  "label": "2026-04-17 (date-versioned spec; unreleased/ tracks current development)"
 },
 "url": "https://agenticweb.wiki/protocols/agentic-commerce-protocol/",
 "category": "pay",
 "type": "protocol"
}