agentic.rayuduramisetti.com

7 specs

Protocols

Not competitors. One purchase can use a checkout spec, a payment spec and a transport at once, so read the layer first. Each flow is drawn below.

SpecLayerStandardisesLeaves alone
ACPStripe · OpenAI · MetaCheckoutProduct feed, checkout session, delegated payment, orders and webhooks.Move money itself, or decide whether the agent is allowed to spend.
UCPGoogle · ShopifyCheckoutCatalogue, cart, checkout, order lifecycle, and what a merchant supports.Prescribe a payment rail; it carries whichever one the merchant accepts.
AP2GooglePaymentSigned intent, cart and payment mandates, for human-present and autonomous flows.Define the storefront or the catalogue; it assumes a checkout already exists.
x402x402 FoundationPaymentA 402 response carrying payment terms, and the retry that proves payment.Handle carts, tax, shipping or returns. It is one request, one price.
MCPAnthropic · communityTransportTool discovery and invocation between a client and a server.Define anything about commerce; there is no official payments extension.
A2ALinux FoundationTransportAgent cards, tasks and messages between independent agents.Carry payment on its own; the x402 extension adds that.
RESTeveryone, alreadyCheckoutNothing new, which is the point. An OpenAPI document makes it discoverable.Give you mandates, scoped tokens or a shared vocabulary between merchants.

01 · Checkout

ACP (Agentic Commerce Protocol)

Stripe · OpenAI · Meta

Let an agent complete a purchase against a merchant that it does not have an account with.

Sequence diagram1. Buyer to Agent: buy this. 2. Agent to Merchant: read product feed. 3. Agent to Merchant: create checkout session. 4. Merchant to Agent: line items, tax, total. 5. Agent to PSP: request delegated token. 6. PSP to Agent: token scoped to this cart. 7. Agent to Merchant: complete session with token. 8. Merchant to PSP: charge. 9. Merchant to Agent: order + webhooksBuyerAgentMerchantPSPbuy this1read product feed2create checkout session3line items, tax, total4request delegated token5token scoped to this cart6complete session with token7charge8order + webhooks9
The merchant stays the seller of record; the agent never holds a reusable card number.
Standardises
Product feed, checkout session, delegated payment, orders and webhooks.
Leaves alone
Move money itself, or decide whether the agent is allowed to spend.
Shape
REST + JSON, dated spec versions, OpenAPI and JSON Schema published.

02 · Checkout

UCP (Universal Commerce Protocol)

Google · Shopify

The same job as ACP, with capability discovery first and more than one transport.

How to read ucp.dev

Sequence diagram1. Agent to Merchant: discover capabilities. 2. Merchant to Agent: what this merchant supports. 3. Agent to Merchant: search catalogue. 4. Agent to Merchant: create / update cart. 5. Agent to Merchant: start checkout. 6. Merchant to Payment: take payment. 7. Merchant to Agent: order lifecycle eventsAgentMerchantPaymentdiscover capabilities1what this merchant supports2search catalogue3create / update cart4start checkout5take payment6order lifecycle events7
Capability discovery comes first, so an agent learns what is supported before it tries it. The same calls travel over REST or MCP.
Standardises
Catalogue, cart, checkout, order lifecycle, and what a merchant supports.
Leaves alone
Prescribe a payment rail; it carries whichever one the merchant accepts.
Shape
REST and MCP bindings, with SDKs and a conformance suite.

03 · Payment

AP2 (Agent Payments Protocol)

Google

Prove that a human authorised what the agent is about to buy.

Sequence diagram1. User to Agent: intent mandate (signed). 2. Agent to Merchant: assemble cart. 3. Merchant to Agent: cart mandate (signed). 4. Agent to Credentials: payment mandate. 5. Credentials to Merchant: authorised payment. 6. Merchant to Agent: receiptUserAgentMerchantCredentialsintent mandate (signed)1assemble cart2cart mandate (signed)3payment mandate4authorised payment5receipt6
Three signed artefacts, so months later everyone can show what the human actually authorised.
Standardises
Signed intent, cart and payment mandates, for human-present and autonomous flows.
Leaves alone
Define the storefront or the catalogue; it assumes a checkout already exists.
Shape
Signed credentials carried over A2A, with an x402 variant for on-chain settlement.

04 · Payment

x402 (x402 payments)

x402 Foundation

Charge for a single HTTP request, with no account and no checkout page.

Sequence diagram1. Agent to Server: GET /resource. 2. Server to Agent: 402 + accepted terms. 3. Agent to Settlement: pay. 4. Agent to Server: GET with payment header. 5. Server to Settlement: verify and settle. 6. Server to Agent: 200 + the resourceAgentServerSettlementGET /resource1402 + accepted terms2pay3GET with payment header4verify and settle5200 + the resource6
No account, no checkout page: the price travels in the refusal, and the retry carries the proof.
Standardises
A 402 response carrying payment terms, and the retry that proves payment.
Leaves alone
Handle carts, tax, shipping or returns. It is one request, one price.
Shape
HTTP status 402 plus headers; settlement usually on-chain stablecoins.

05 · Transport

MCP (Model Context Protocol)

Anthropic · community

Give a model tools and data, including a merchant's catalogue and cart.

Sequence diagram1. Model to MCP server: initialise. 2. Model to MCP server: list tools. 3. MCP server to Model: tools + schemas. 4. Model to MCP server: call tool(args). 5. MCP server to Backend: do the work. 6. MCP server to Model: resultModelMCP serverBackendinitialise1list tools2tools + schemas3call tool(args)4do the work5result6
A merchant's catalogue or cart can sit behind one of these tools; MCP itself knows nothing about commerce.
Standardises
Tool discovery and invocation between a client and a server.
Leaves alone
Define anything about commerce; there is no official payments extension.
Shape
JSON-RPC over stdio or HTTP, with a dated spec.

06 · Transport

A2A (Agent2Agent)

Linux Foundation

Let two agents talk, a shopper's agent and a merchant's for example.

Sequence diagram1. Agent A to Agent B: fetch agent card. 2. Agent B to Agent A: skills it offers. 3. Agent A to Agent B: create task. 4. Agent B to Agent A: 402 payment required (x402). 5. Agent A to Agent B: task + payment proof. 6. Agent B to Agent A: artifacts, status updatesAgent AAgent Bfetch agent card1skills it offers2create task3402 payment required (x402)4task + payment proof5artifacts, status updates6
Two independent agents, neither inside the other. The x402 extension is what turns a task into a paid one.
Standardises
Agent cards, tasks and messages between independent agents.
Leaves alone
Carry payment on its own; the x402 extension adds that.
Shape
JSON over HTTP, with agent cards for discovery.

07 · Checkout

REST (Plain REST + OpenAPI)

everyone, already

The baseline. Most agents will meet an ordinary JSON API long before a named protocol.

Sequence diagram1. Agent to Your API: GET /openapi.json. 2. Your API to Agent: what exists, and the shapes. 3. Agent to Your API: GET /products. 4. Agent to Your API: POST /orders. 5. Your API to Agent: 201 + orderAgentYour APIGET /openapi.json1what exists, and the shapes2GET /products3POST /orders4201 + order5
No new vocabulary. An OpenAPI document and integer prices get you most of the way.
Standardises
Nothing new, which is the point. An OpenAPI document makes it discoverable.
Leaves alone
Give you mandates, scoped tokens or a shared vocabulary between merchants.
Shape
Your endpoints, described so a model can call them without guessing.