HTTP 402 has been "reserved for future use" since 1997. Stripe just gave it a job.
The HTTP spec defined 402 Payment Required almost 30 years ago. Nobody knew what to do with it. Some APIs used it for failed card charges. Most developers forgot it existed.
Then Stripe launched the Machine Payments Protocol this week. And suddenly, 402 is doing exactly what it was designed for.
Here's what happened
Stripe and Tempo co-authored MPP as an open standard for machine-to-machine payments. The idea is simple. When an AI agent requests a paid resource, the server returns HTTP 402 with payment details. The agent pays. The server delivers the resource.
No account creation. No pricing page. No checkout flow. Just a status code, a payment, and access.
That might sound boring on paper. But think about what it replaces.
Right now, if your agent needs to call a paid API, someone has to manually sign up, enter a credit card, pick a subscription tier, and paste in the key. MPP skips all of that.
The protocol supports stablecoins directly and fiat through Shared Payment Tokens. Visa already extended it to work with card networks. Lightspark adapted it for Bitcoin via Lightning.
Who's actually using this
→ Browserbase lets agents pay per session for headless browsers
→ PostalForm lets agents pay to print and send physical mail
→ A butcher shop in Melbourne lets agents order food for pickup
Yes, a butcher shop. Your AI agent can now buy you a steak. 🥩
This is infrastructure, not hype. Stripe processes the transactions through its existing PaymentIntents API. Businesses see MPP payments in their dashboard like any other charge. Same reporting, same payouts, same refund flow.
Why developers should care
If you're building anything with agents, this changes your architecture. Before MPP, agent-to-service payments were a hack. You'd hardcode API keys, prepay for credits, or build custom billing integrations for every service.
MPP makes payment a protocol-level concern. Like authentication. Like TLS. Your agent hits an endpoint, gets a 402, pays, and moves on.
That's a big deal for the emerging ecosystem where agents call other agents. Each hop can now include payment natively.
The catch ⚠️
MPP currently runs on Tempo, a blockchain incubated by Stripe and Paradigm. The protocol claims to be rail-agnostic, but the crypto integration might make enterprise adoption slower. Stablecoin payments are US-only for now.
And there's the trust question. Do you want your agent autonomously spending money? The protocol doesn't define spending limits or approval flows. That's left to whoever deploys the agent.
Which means someone will eventually build the "my agent spent $4,000 on API calls while I slept" horror story. 💸
The bigger picture
HTTP 402 sat in the spec for 29 years waiting for a use case. The use case turned out to be machines paying machines without asking humans first.
Whether that excites or terrifies you probably depends on whether you've ever left a recursive function running overnight. 🙂
What's your take — would you let your agent spend money autonomously, or does that need a human in the loop every time? 👇
Top comments (0)