Stripe Just Launched a Protocol for AI Agents to Pay You Directly. Here's How to Build a Business Around It.

Today might be the most important day for AI business models since GPT-4 launched. And almost nobody is talking about it the right way.

Stripe and Tempo just launched the Machine Payments Protocol (MPP) — an open standard that lets AI agents pay for services autonomously. Not through a human clicking "buy." Not through a pre-authorized credit card. The agent itself discovers a service, negotiates the price, authorizes payment, and receives the resource. Programmatically. In seconds.

This is not a whitepaper or a concept. It went live today. Real businesses are already getting paid by machines.

What Just Happened

Stripe — the company that processes hundreds of billions of dollars in payments annually — co-authored an open protocol with Tempo (a blockchain backed by Paradigm at a $5 billion valuation) specifically designed for machines to pay other machines.

The protocol supports both fiat (cards, buy-now-pay-later) and stablecoins. Visa contributed the credit card payment specs. Payments appear in your normal Stripe dashboard alongside human transactions. Same settlement schedule. Same fraud protection. Same tax calculation.

Matt Huang, co-founder of Tempo and managing partner at Paradigm, described the design philosophy: "Our team came up with what we thought was the most elegant, minimal, efficient protocol that anyone can extend without our permission."

Why This Changes Everything

Until today, AI agents could do work but couldn't buy things. An agent could research flights but couldn't book one. It could find the best API for a task but couldn't pay for access. The payment step required a human in the loop.

MPP removes that bottleneck. When an agent requests a resource, the service responds with a payment request. The agent authorizes it. The resource is delivered. No human clicks, no account creation, no checkout page navigation.

This means every API, every micro-service, every digital resource can now have agent-native billing. The agent discovers you, evaluates your offering, pays, and moves on. At machine speed.

The Opportunity Map

Think about what agents need to do their jobs but can't currently access without human help:

Digital services agents will pay for:

• Web scraping and browser sessions (Browserbase is first)
• Data enrichment and verification
• Image/video generation and editing
• Document formatting and PDF creation
• Translation and localization
• Code review and security scanning
• SEO analysis and keyword research

Physical-world bridges agents will pay for:

• Printing and mailing (PostalForm is first)
• Food ordering (Prospect Butcher Co is first)
• Flower delivery, gift sending
• Office supply ordering
• Shipping and logistics

Infrastructure agents will pay for:

• Compute on demand
• Storage per gigabyte
• API access per call
• Database queries per request

Each of these is a business waiting to be built with MPP.

How to Build an MPP-Enabled Service This Week

The technical integration is surprisingly simple. Stripe designed MPP to work with their existing PaymentIntents API. If you already have a Stripe account, adding MPP support takes a few lines of code.

Step 1: Pick your service. What's the smallest, most useful thing you can offer to an AI agent? Think in terms of single API calls, not complex workflows. "Convert this HTML to PDF" is better than "build me a website."

Step 2: Build the API endpoint. Your service needs to accept a request and return a result. Standard REST or any HTTP endpoint works.

Step 3: Add MPP payment flow. When an agent requests your service, respond with a payment request specifying the amount. The agent authorizes, Stripe processes, and you deliver the result. The MPP docs walk through the exact implementation.

Step 4: Register with MCP directories. Agents discover services through MCP servers and tool directories. List your service on SkillsMP, ClawHub, and OpenTools so agents can find you.

Step 5: Price for machines. Agents don't care about monthly subscriptions or pricing tiers. They want per-request pricing. $0.01 per PDF conversion. $0.05 per web scrape. $0.10 per data enrichment. Think micro-transactions.

The Business Models That Will Win

Model 1: Per-request micro-services ($0.01-$1.00 per call)

Build one small, reliable service. Price it per use. Volume is everything — if 10,000 agents each make 100 requests per month at $0.05 each, that's $50K/mo.

Model 2: Physical-world agent gateway ($5-50 per transaction)

Agents are digital. The real world is not. Every service that bridges this gap commands premium pricing. Sending physical mail, ordering food, booking venues, purchasing supplies. Agents will pay more for these because the alternative is stopping and waiting for a human.

Model 3: MPP integration consulting ($2-5K per client)

Hundreds of existing API businesses need to add MPP support. The protocol just launched, docs are sparse, and most developers haven't heard of it yet. If you understand MPP today, you can charge premium rates to help businesses become agent-accessible.

Model 4: Agent billing analytics dashboard ($49-299/mo SaaS)

As businesses start accepting agent payments, they'll need tools to understand the patterns. Which agents are paying? What services are most requested? What's the revenue per agent? Build the analytics layer.

The Competition Landscape

Stripe and Tempo's MPP isn't the only agent payment protocol. Coinbase launched x402 (an HTTP-native payment protocol). Google released its own agent payment scheme with stablecoin support. Visa contributed to MPP's credit card specs.

But MPP has a structural advantage: Stripe's existing merchant base. Millions of businesses already use Stripe. Adding MPP support to their existing integration is trivial. That distribution advantage means MPP is likely to become the default standard — just as Stripe became the default for human payments.

What This Means for the Next 12 Months

We're about to see an explosion of agent-native businesses. Services built from the ground up for machines as the primary customer. No landing pages. No onboarding flows. No customer support chat. Just an API endpoint, a price, and an MPP payment flow.

The businesses that move fastest here will own their categories before most people realize the categories exist.

"Agentic payments is very early, and we still are figuring out the best way to structure these." — Matt Huang, Paradigm. That "very early" is the whole opportunity. Early means cheap competition, fast iteration, and outsized returns for first movers.

Build one micro-service this week. Wire it up with MPP. List it in agent directories. Start getting paid by machines while everyone else is still reading about it.