Agentic Commerce
When the buyer is a program.
A purchase where software does the finding, the asking and the paying. What each protocol does, how it breaks, and what is worth reading.
A purchase, end to end
What actually happens
Latest reads
All 46 →Escrow for purchases an agent makes now and a human confirms later: authorize, capture, refund.
arXiv · paper
Models x402, MPP, ACP and AP2 in Tamarin and reports 40 findings nobody had written down.
arXiv · paper
33 structural vulnerabilities that survive a model swap, because they live in the protocol.
arXiv · paper
The current dated spec. Worth checking what is and is not in it before assuming commerce support.
MCP · spec
The practical guide to signing agent requests: keys, a directory, and RFC 9421 signatures.
Cloudflare · docs
Start here
Three reads, in order.
The four layers
Every spec answers one of them.
Can an agent find and understand the product?
Can it get a firm price and place the order?
Can money move, with limits?
Does the merchant know who is calling, and on whose behalf?
The protocol map
Full comparison →Explainers
All 10 →How it breaks
All 30 attacks →A signature proves what was signed, not that it was wanted. 30 attack classes and 8 CVEs, each with a source.
The agent reads the web, and the web is attacker-controlled. Instructions hidden in a review, a product description or a page's markup are read with the same trust as the buyer's own words.
A tool's description is context the model trusts. A tool's code is software you installed. Both have been weaponised, and this is the area with real CVEs rather than scenarios.
The agent holds authority the user granted for one purpose and spends it on another. This is the oldest bug in the book, and the MCP specification is the clearest place it is written down for agents.
Charging per request puts money in the request path. The failures are the ones you would expect from money in a request path: replay, races and settlement that never arrives.
A signature proves what was signed. It does not prove that the thing signed reflects what the human wanted, which is the gap most of this section lives in.
Jobs of the future
All 10 roles →When the buyer is a program, the work moves. Each role here is tied to the job it grows out of, and to what shrinks alongside it.
Judgment, in code
TypeSafe, with real answers →A few steps need reading, not rules: is this the shoe they meant, is this review talking to the agent. TypeSafe answers those with a probability code can branch on.
Who is writing this
I am Rayudu Ramisetti. I build software, I am going deep on agentic commerce, and I write as I go. Working on it too? Get in touch.