The Agentic Commerce Protocol (ACP) is an open specification for programmatic exchange between a buyer, the buyer's AI agent and a seller to complete a purchase. Its aim is to make checkout a defined integration rather than requiring an agent to imitate every click in a browser. ACP is a commerce protocol; it is not the BeeAI Agent Communication Protocol that has joined A2A.
The checkout boundary
In the documented model, an agent can present checkout choices and collect buyer selections while the seller keeps its existing backend and payment processing. The protocol describes how the parties exchange information for the purchase. It does not make the agent the merchant, remove the seller's responsibilities or turn a language-model response into payment authorization.
Why a structured protocol can help
Browser automation can be fragile when page layouts change or a checkout flow has unexpected steps. A programmatic interface can make item selection, checkout state and buyer updates more explicit. For merchants, the goal is to support agent-originated purchases while retaining control of product data, order handling and fulfillment.
Keep buyer consent and payment security central
A useful implementation should make the order, total, seller and relevant terms clear before the buyer commits. Payment credentials and authentication need to follow the protocol's current security guidance and the merchant's payment-provider requirements. Confirmation should be tied to a specific purchase, not inferred from a broad instruction such as 'find something good'.
What the protocol does not solve by itself
A checkout schema cannot guarantee product suitability, prevent every fraudulent request, resolve disputes or decide who is liable when an agent misunderstands intent. Merchants still need authorization checks, inventory and price validation, idempotent order creation, clear cancellation and refund paths, and auditable records.
Evaluate the living ecosystem
Specifications evolve, and commerce has multiple adjacent initiatives. Before building, check the protocol repository and documentation for current status, versioning, supported payment flows and merchant requirements. Treat a demo as an integration example, not proof that a particular deployment is production-ready.
The broader agentic commerce opportunity
Agent-assisted discovery and checkout could reduce friction for buyers, but the durable product work is in trust: explaining why an item was selected, preserving buyer choice, handling exceptions and making transaction state visible. In agent commerce, a successful purchase is not simply a tool call—it is an explicitly authorized business transaction.