Machine Payments Protocol - A New Standard for Agentic Payments
How Machines can pay for APIs, Tools, and Content in one flow
The past year has seen an explosion of interest in agent payment protocols allowing AI agents or bots to autonomously pay for services on behalf of their users. Today’s payment rails however still have visually rich checkout flows, browser captchas, and manual account creation.
MPP, or Machine Payments Protocol, is an open standard from Tempo and Stripe that lets software pay for services as part of the same HTTP request. The idea is simple: if an API call, tool use, or piece of content costs money, the payment step should not require a human checkout flow, account setup, or manual billing page.
In this edition, we’ll look into what MPP is, how the payment flow works, and why it matters as more internet activity shifts from people to software agents.
What is MPP
Most online payments are still built for humans. They assume forms, logins, checkout screens, and all the friction that comes with them. MPP is trying to solve that interface problem by giving developers a standard way to charge for APIs and giving agents a standard way to pay for them.
That matters because the protocol is not tied to one payment rail. MPP is designed to support multiple methods, including Tempo stablecoins, Stripe-powered payments, cards, and Bitcoin Lightning. The point is to standardize the payment flow, not force everyone onto one network.
How the Payment Flow Works
The flow is meant to be straightforward. A client requests a paid resource. The server replies with HTTP 402 Payment Required and tells the client how it can pay. The client completes the payment, sends back proof, and then receives the resource. The server can also return a receipt so both sides have a record of what happened.
MPP also supports more than one payment style. A simple one-time payment works for fixed-cost actions like a paid API call or a content download. A session model works better for repeated usage, where software may need to make many small payments without settling every single request onchain.
Machine-to-Machine Commerce
The clearest use case is agentic software. If an AI agent needs to query a model, search the web, generate an image, or access paid data, it needs a way to discover price and pay without a human stepping in each time. MPP is built for that kind of machine-to-machine commerce.
This is also why the project is broader than a crypto payments project. Fortune reported that MPP launched with support for both fiat and crypto, and that it is meant to work across multiple blockchains and payment rails rather than just one. That makes it easier to understand as internet payment infrastructure, not just another crypto checkout tool.
MPP is still early, but the core idea is easy to understand. As more software starts acting on behalf of users, payments need to become more native to the request itself. Stripe brings distribution and existing payments infrastructure. Tempo brings a crypto-native rail designed for fast stablecoin transfers.
The simplest way to think about MPP is this: it is trying to make paying for an API feel as native as calling the endpoint.
Important Links
Become a Premium member and get the full Alea platform.
Join thousands of sharp crypto investors & traders using Alea to evaluate opportunities and deploy with conviction. For just $149/month, Premium unlocks:
Full report suite: Deep Dives, Perspectives, Blueprints, Theses, Benchmarks, Memos & Pulse.
Protocol Data Rooms: Standardized due diligence portals with live analytics, risk matrices, and governance tracking across 24+ protocols.
Podcast Digest & Summit Digest: Key takeaways from the conversations shaping markets, so you don’t have to listen to every pod.
Governance Tracker: Live proposal feeds and voting activity across major protocols.
Full access to the historical research archive.