MPP Gateway
Stablecoin payment gateway for 43 APIs with per-request access and no client-side API keys.
About
MPP Gateway is a stablecoin payment gateway that lets you access APIs without client-side API keys. It sits behind Machine Payments Protocol and turns each request into a paid call, so the client can pay in stablecoins and receive the upstream response plus a payment receipt. The site highlights 43 APIs, 11 total endpoints, and example routes for market data, GitHub, Stripe, Twilio, Plaid, and carbon removal.
What is MPP Gateway
MPP Gateway is a stablecoin payment gateway built around Machine Payments Protocol. It exposes paid access to upstream services so a caller can request an endpoint, receive a 402 Payment Required response when payment is needed, and then complete the request with Tempo stablecoin payments. The app is presented as a hackathon project built for Tempo and Stripe, and it focuses on agent-friendly API access rather than a consumer dashboard.
The public site says it has 43 APIs behind the protocol, 11 total endpoints, and a live services view. That makes MPP Gateway useful as a concrete example of a stablecoin payment gateway that abstracts API billing into the request flow itself.
Key features
MPP Gateway combines payment handling and API proxying in one flow:
- Stablecoin payment gateway flow: the request is gated, paid for, and then proxied to the upstream API.
- No client-side API keys: the site explicitly says you do not need API keys on the client side.
- 402-based access model: the app uses HTTP 402 Payment Required as part of the interaction.
- Payment receipt delivery: after payment, the gateway returns the upstream response plus a Payment-Receipt.
- Tempo integration: payments are described as being handled via Tempo stablecoin, including an automatic tempo CLI path.
- Multiple real integrations: the examples shown include Massive, Stripe, GitHub, Twilio, Plaid, and Stripe Climate.
- Public route examples: the site documents sample calls such as market status, stock lookup, balance checks, repo listing, SMS sending, and carbon removal.
The app’s examples suggest the gateway is meant for programmatic use. For instance, the same stablecoin payment gateway pattern can be used for a cheap stock lookup, a GitHub repo request, or a more expensive SMS or Plaid call, depending on the upstream service and route.
How to use it
Using MPP Gateway follows a request-pay-proxy pattern:
- Pick an endpoint from the live services list or route examples.
- Send the request to the MPP Gateway URL instead of calling the upstream provider directly.
- If the request requires payment, handle the 402 Payment Required response.
- Pay with Tempo stablecoin using the provided flow or tempo CLI.
- Retry or continue the request path and receive the upstream response plus a Payment-Receipt.
Example routes on the site show the expected style of usage:
GET /massive/v1/marketstatus/nowfor market statusGET /massive/v3/reference/tickers?ticker=AAPLfor stock lookupGET /stripe/v1/balancefor Stripe balance checksGET /github/user/reposfor GitHub reposPOST /twilio/2010-04-01/Accounts/<SID>/Messages.jsonfor SMS sendingPOST /plaid/accounts/balance/getfor bank balance retrievalPOST /stripe/v1/climate/ordersfor carbon removal orders
Because the gateway is designed around an API proxy, the main workflow is closer to a developer tool than a conventional app UI. You are working with routes, status codes, and upstream responses.
Who it is for
MPP Gateway is best suited for developers who want a stablecoin payment gateway that can sit in front of API calls. It is especially relevant for:
- AI agent builders who want per-request payments without managing API keys on the client.
- Hackathon teams experimenting with machine payments and API monetization.
- Backend developers who want to test a pay-per-request proxy model.
- Finance and developer-tool users who need examples involving balances, market data, or payment rails.
- Teams exploring how a stablecoin payment gateway could wrap third-party APIs.
The app is not framed as an end-user finance product or a generic API marketplace. It is more narrowly focused on request-level payments and upstream API access.
What to know before you use it
MPP Gateway is specific in what it does and limited in what the public material confirms.
- It is built for the MPP Hackathon by Tempo and Stripe, so it should be treated as a project-oriented gateway rather than a mature commercial platform.
- The site shows 43 APIs and 11 total endpoints, but the exact full inventory is not fully visible in the scraped material.
- Route prices are shown per request, such as $0.005, $0.01, and $0.10, but pricing may differ by endpoint and should be verified on the live site before use.
- The gateway is meant to proxy upstream APIs; it does not appear to replace those services or remove their own usage limits, auth rules, or data constraints.
- If you need authoritative account data, payment records, or regulated financial information, use the official upstream provider rather than relying only on the gateway layer.
- Because this is an API-first service, success depends on handling HTTP responses correctly and supporting the payment workflow in your client or agent.
In short, MPP Gateway is a stablecoin payment gateway for developers who want to experiment with paid API access, agent billing, and request-level settlement. If your use case depends on exact routing, live balances, or official records, confirm the upstream source before you rely on the stablecoin payment gateway in production.
FAQ
What is the MPP Gateway?
MPP Gateway is a stablecoin-based payment proxy that lets you pay for API requests on a per-call basis without managing API keys. It currently supports 43 live endpoints across categories like finance, messaging, and developer tools, and is designed for AI agents and developers who want simple, usage-based API billing.
Is MPP Gateway free to use?
Some example requests are shown with small per-call prices, but the overall pricing model is endpoint-based and should be checked on the live site. The homepage shows request prices like $0.005, $0.01, and $0.10 for specific routes.
How do I use the gateway?
You make an HTTP request to the gateway’s endpoint; if payment is required, you'll receive a 402 status. Then, you use the Tempo CLI to send the required stablecoin payment, and the gateway will proxy your request to the actual API, returning the result along with a payment receipt.
Do I need API keys on the client side?
No, the site says client-side API keys are not needed. Instead, the request is paid through the gateway using Tempo stablecoin.
Which stablecoin is used for payments?
All payments are made with Tempo stablecoin, a fast and low-cost digital currency. The gateway leverages Tempo’s payment infrastructure to handle microtransactions efficiently.
What platforms does MPP Gateway support?
It is a web-based API gateway with an API-first workflow. The public material only shows Web and API as supported surfaces.
Who is this service for?
It’s ideal for AI agents that need autonomous API access, developers building applications with usage-based pricing, and anyone who wants to avoid API key management. It was originally built for the MPP Hackathon by Tempo and Stripe.
What kinds of endpoints are available?
The examples include market data, stock lookup, Stripe balance checks, GitHub repos, Twilio SMS, Plaid balance retrieval, and Stripe Climate carbon removal. The site also says there are 43 APIs behind the protocol.
Is there a cost to use the gateway itself?
The gateway is free to use; you only pay the per-request fees for the specific APIs you call. These fees are set by the gateway and are typically a few cents or less per request.
Who should use this app?
It is best for developers and AI agent builders who want pay-per-request API access. It is not positioned as a consumer finance app.