Stripe's Machine Payments Protocol Is the Payments Layer for the Agent Web
Stop selling "AI agents are coming." They're here, they're spending money, and as of March 2026 they have a standardized way to do it. Stripe and Tempo co-released the Machine Payments Protocol, an open standard that lets an AI agent pay for a service in a single HTTP request. Built on HTTP 402, integrated with PaymentIntents in "a few lines of code," not Stripe-proprietary. That's the payment rail for the agent economy, and it's already live.
What MPP actually is
The Machine Payments Protocol is an open specification for agent-to-service payments over the web. The mechanics are simpler than the framing suggests. An AI agent makes a request to a service endpoint. If that endpoint wants payment, it responds with HTTP 402 — the long-dormant "Payment Required" status code — along with structured payment instructions. The agent (or the wallet attached to it) settles the payment and re-requests with proof. The service delivers. Total round trip: one conversation, no human in the loop.
The standard was co-authored by Stripe and Tempo, but it's not owned by either of them. MPP is intentionally open so any payments provider can implement it on either side of the wire. On Stripe's side, the integration uses the existing PaymentIntents API; in their own words, you can add MPP support "in a few lines of code." The protocol assumes nothing about the underlying network. Card rails, stablecoins, account-to-account — the layer that handles the actual money is decoupled from the layer that handles the agent conversation.
If you've been following the web for a while, you've probably noticed that HTTP 402 has been sitting in the spec for thirty-plus years with no real implementation. It was reserved for "Payment Required" in the original HTTP/1.1 draft and never standardized into a usable shape, because there was never a credible client to be paying. That's what changed. Agents are the credible client. MPP is what 402 was always waiting on.
A concrete walkthrough makes the protocol easier to hold in your head. An agent is asked, by a person or another agent, to find current pricing for a specific commercial product. It hits the obvious endpoint. The endpoint returns a 402 with a machine-readable payment instruction — amount, currency, settlement endpoint, what the response will contain. The agent's wallet evaluates the instruction against its budget and policy, settles the payment, and re-issues the request with proof. The endpoint validates the proof and returns the data. Total wall-clock time is roughly the same as any other API call. No account creation, no API key, no subscription, no human approval. That's the unit of work MPP standardizes, and it's the unit of work that human-built payment plumbing has never been able to support at machine speed.
The Forbes coverage of the launch frames it as the start of the machine-to-machine commerce era and points at Twilio as an early beneficiary — a programmable services company whose entire surface area is exactly the kind of API agents want to call. Twilio is the leading indicator, not the whole story.
Why this matters now
Two protocols are starting to define the shape of the agent web, and they pair cleanly. Anthropic's Model Context Protocol (MCP) is how agents read — a standardized way to expose tools, data, and context so any agent can consume them. MPP is how agents pay. MCP plus MPP is the two-rail foundation for a web where agents discover, retrieve, and transact without a human keyboard in the middle.
That changes several long-standing business questions at once. Pay-per-call APIs become trivial — no API key issuance, no subscription plan, no Stripe Customer object to manage; the agent settles per request and the service responds. Agent-to-agent micropayments become possible at price points that didn't work under credit-card economics. Content can be monetized to agent traffic without ad-tech, because the agent will simply pay for the page rather than rendering an ad. Machine-readable paywalls — the kind that an agent can understand, evaluate, and decide to satisfy in milliseconds — become a real product surface instead of a thought experiment.
None of this requires the underlying web to change. The same servers that serve human visitors today can return 402 to agent visitors tomorrow. That's the part most people aren't seeing yet: MPP doesn't ask you to build a new product. It asks you to make the product you already have visible to a customer you've been ignoring.
It's worth being precise about what kind of value this unlocks. Microtransactions on the web have been attempted, and failed, every five years for two decades. Each attempt assumed the bottleneck was the technology — a smarter wallet, a smaller fee, a different currency. The actual bottleneck was always the same: humans hate clicking a $0.04 confirmation. Agents do not. Removing the human from the buyer's seat is what makes the whole category viable. MPP doesn't invent micropayments; it just removes the only customer who was ever going to refuse to use them.
What it means for your business
Three concrete scenarios are worth thinking through now, before the agent traffic mix gets large enough to force the question.
Your docs, content, and API become monetizable to agent traffic without ad-tech. If your business publishes pricing data, market research, technical documentation, or anything else that an agent might be sent to retrieve, you can charge for that retrieval without changing your audience-facing model. Humans still read your blog for free. Agents pay per call. You don't need an ad network, a paywall vendor, or a subscription tier — you need a 402 response and a payment endpoint. That math gets interesting fast when a single agent might hit the same source thousands of times in a research session.
Your internal automations can transact without human approval loops. Most internal AI tooling today stops at "draft a thing for a human to send" because the moment money moves, you need a signoff workflow. MPP changes the floor on that. An internal agent with a budget can buy a one-off lookup, a per-call enrichment, a paid subscription on behalf of the org, and settle in seconds. The bottleneck on internal automation has rarely been the AI's reasoning; it's been the legal and operational drag on "let the system spend money." MPP doesn't fix the governance question, but it removes the technical excuse.
Services priced per-call, billed to the agent's owner, settled in seconds, become a new product shape. This is the one that's hardest to picture today and most consequential later. Almost every SaaS company priced their product around what a human team would tolerate doing manually — seats, monthly tiers, usage bundles. Agent customers don't have any of those constraints. They want to pay for what they use, exactly, and they want to walk away when they're done. The first product category to actually price for that customer ends up with a sales motion the incumbents can't match without restructuring their entire ARR.
A short, practical version: if you sell something an agent might want to buy on behalf of a human, the next 12 months are when you decide whether to expose that surface natively or wait for someone else to do it and undercut you on response time.
The Commonwealth Creative angle
We build agent-ready websites and knowledge bases for small businesses, and we've been thinking out loud about what an "agent-readable" version of a site even looks like. Up to now, that conversation has mostly been about structured content, MCP-style exposure, and making sure a site survives summarization. MPP adds the missing layer. We can now help clients design surfaces that don't just answer agent traffic — they can be paid for it.
We are not a Stripe partner. We're an agency that runs on the agent economy, builds for clients who increasingly will, and reads the primary sources so you don't have to. If you're trying to figure out where MPP fits into your roadmap — what parts of your site or product to expose to agent traffic, how to price for it, whether to wait — that's a conversation we're happy to have. Contact us here.
Close
For thirty years, every business on the internet has been building for one customer: a human with eyeballs. The next billion website visitors won't have either, and Stripe just handed them a wallet.
