Agents Can Spend Money Now
Four commerce protocols shipped in one week, turning agents into economic actors with real payment rails.
Agents learned to spend money last week. Not in a demo. In production, with real payment rails, budget controls, and settlement infrastructure from Stripe, Cloudflare, Shopify, and Google - all landing within days of each other.
What Shipped
Stripe's Machine Payments Protocol (MPP), announced at Sessions 2026 on April 29, is an open standard co-authored with Tempo and proposed to the IETF. Agents pay for services in the same HTTP request that calls them. Supports stablecoins and fiat. Over 100 services adopted at launch - Anthropic, OpenAI, Shopify, Alchemy, Dune Analytics.
Cloudflare's agent provisioning protocol, built on Stripe, went live April 30. An agent can now create a Cloudflare account, buy a domain, start a paid subscription, and deploy code to production. Zero human clicks. Three phases: Discovery (query the service catalog), Authorization (Stripe vouches for the user, Cloudflare issues credentials), Payment (tokenized - the agent never sees card numbers). Default spend cap: $100 per month per provider.
Shopify and Google's Universal Commerce Protocol (UCP) defines how agents discover merchants, negotiate capabilities, and complete checkout. Backed by Target, Walmart, Etsy, Wayfair. It handles discounts, loyalty programs, subscriptions - the messy reality of commerce that clean demos ignore.
Why This Is Different
MCP solved the integration problem - agents can call any tool through one protocol. These commerce protocols solve the transaction problem. Calling an API is free. Buying a domain costs money. That gap required an entirely new trust layer: identity, authorization, budget controls, and settlement.
The architectural pattern is consistent across all of them. The agent never touches raw credentials. A platform attests to user identity and provides tokenized payment handles. The agent operates within a budget envelope set by the human. Spend rails, not guardrails.
What Changes for Builders
If you build agent systems, your trust model just expanded. It is no longer enough to ask "can this agent call the right tools?" You now ask "how much can this agent spend, on what, and who approved it?"
The agents I build will need spend policies the way they currently need tool permissions. Budget-per-task, not just budget-per-month. Approval flows for purchases above a threshold. Audit trails for every transaction. This is a new category of agent governance that did not exist two weeks ago.
Where This Heads
Commerce was the last major capability gap between agents and human operators. Agents could already read, write, search, and deploy. Now they can pay. The economic surface area of an agent just expanded from zero to the entire internet.
The teams that figure out spend governance first will be the ones comfortable deploying agents that actually do things.