agentic.rayuduramisetti.com

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

Every protocol, drawn →
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.

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.

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.

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.