Notes on agentic payments.
Short essays on x402, stablecoins, governance, and how AI agents should pay for things on the open internet.
- 10 min read
x402 now has a formal attack surface. Four flaw classes, and what they mean for anyone letting agents spend.
The first systematic security analysis of x402 identifies four flaw classes — cross-resource substitution, duplicate-settlement races, allowance overdraft, and denial of settlement — reaching 100% resource leakage against official SDKs. Here is what each one actually does, and why a payment protocol was never going to be the place where spending gets controlled.
x402securityagentic-payments - 9 min read
Cloudflare gave agents a wallet. A spending cap is not governance.
Cloudflare Wallets and cloudflare.pay give AI agents an identity and a virtual wallet with allowances, allowlists, and per-transaction caps. That closes the buyer side of x402 — but per-wallet limits are not the same as company-wide spend policy, approvals, and auditable receipts.
x402cloudflareagent-wallets - 9 min read
200 million x402 transactions, $15 million moved. What the numbers actually say.
The x402 Foundation is live under the Linux Foundation with 40 members including Visa, Mastercard, Amex and Stripe. Transaction counts are enormous and dollar volume is tiny — roughly 14 cents a payment. That ratio is not a failure. It is the whole point, and it changes what the control layer has to look like.
x402x402-foundationagentic-payments - 8 min read
Cloudflare will let anyone charge agents. Someone still has to let agents pay.
Cloudflare's Monetization Gateway turns any API, page, dataset, or MCP tool into a paid resource over x402. That solves the merchant side. The buyer side — how an AI agent actually decides to pay, under whose rules — is the other half of the problem.
x402cloudflareagentic-payments - 8 min read
MCP meets x402: how tool-calling agents actually pay for tools
MCP gave agents a standard way to call tools. x402 gives those tools a standard way to charge. Here is how the two fit together, and what a paid MCP tool call actually looks like end to end.
mcpx402agent infrastructure - 7 min read
Wallet providers vs. governance layers: why AI agents need both
Coinbase, Privy, Turnkey, and Fireblocks solve custody and signing. That is not the same problem as deciding whether an AI agent should be allowed to pay. Here is how the two layers fit together.
walletsgovernanceagent infrastructure - 9 min read
Stablecoins, agentic payments, and the end of the human checkout
A plain-English explainer of what stablecoins are, why they fit agentic payments better than cards, the ones worth knowing in 2026 (USDC, EURC, USDT, PYUSD, SEKAU), and what changes when shopping is agent-driven.
stablecoinsagentic-paymentsx402 - 8 min read
What are agentic payments?
Agentic payments are transactions initiated by AI agents on behalf of a human or company. Here is what they are, why they are different, and how they work.
agentic-paymentsx402stablecoins - 6 min read
AI agents do not need a wallet. They need governance.
Giving an autonomous agent its own wallet is the wrong abstraction. Here is why scoped, policy-bound access to a wallet someone else custodies is the right one.
governancewalletsx402 - 7 min read
x402, explained for builders
x402 is a small open protocol that lets any HTTP resource quote a price and any client pay inline. Here is what it does, what it does not, and how to think about it.
x402protocolsdevelopers