Pinned Tweet
Mercator makes it easy for your agent to run multi-step agentic workflows by surfacing countless tools that can be paid for autonomously via MPP
Get started in seconds using MACH, a token designed for machine payments, that you can buy now with Apple Pay and give to your agent:
INTRODUCING MERCATOR by @tempo.
Mercator gives agents a new effort level.
By giving an agent a search engine to the world's paid tools it empowers a small model to punch above its weight, while being cheaper than larger models.
$5 Mercator credits w/ your X/Github ⬇️
3
13
3,019
Sessions enable any business that needs streaming payments, like inference, compute, and data, to charge agents as they use their services.
Learn how @stripe uses MPP Sessions to accept streaming payments:
Streaming payments are a super interesting business model now that agents can pay-per-call for tools
Stripe now supports streaming payments using @mpp Sessions, which allows agents to pay subcent transactions for a session, and then settle the final amount when finished.
Could be really useful for streamed compute, LLM interference, data analysis, and more.
Get started: docs.stripe.com/payments/mac…
3
7
1,346
Agents are now shopping online and they've got money to spend.
They can even get discounts!
0 onchain fees for agents when paying with stablecoins on @stripe stores:
Agents are much more likely than humans to make microtransactions which work especially well over stablecoins
Usually that means merchants selling tools to agents would have to manage crypto-specifics, like gas facilitation
Now, @stripe takes care of that for you with your @mpp integration. We deal with the crypto side and pay for gas, and payments just land in your Stripe balance
Get started and one-shot your integration: docs.stripe.com/payments/mac…
MPP was featured in @bytebytego today!
• Why agents need to pay for APIs, data, and compute as they work
• How MPP Sessions enable micropayments by settling payments together
• What this unlocks; from paying per API call to buying a single article
Read the full piece: blog.bytebytego.com/p/ai-age…
Want to learn the history of MPP and why machine payments are making micropayments viable at scale on the internet? This explains it all:
The $0.001 Payment No Human Would Ever Make: Ex-Stripe MPP Co-Author on Agent Payments and Tempo
Shoal Signal Ep. 17 with @brendan_j_ryan, MPP co-author at @tempo, hosted by @zaddycoin
We cover the checkout form agents will never load, why micropayments finally work once a CPU clicks OK, the Lisbon hotel week that produced MPP, why payments will never be unified, and the endgame where users pay over crypto rails without knowing it.
0:00 Checkout without the payment form
2:25 From Kubernetes to payments
4:37 Why payments will never be unified
11:25 No single payment method wins
15:16 Collapsing checkout into a protocol
18:12 Why pay-per-article finally works
20:47 Writing MPP in a Lisbon hotel
24:54 Hunting the killer use case
27:25 Turning rate limits into prices
29:50 Scrape once, serve a million times
35:05 Making 402 an official standard
40:48 Cloudflare and AWS flip the switch
42:32 Users never see the crypto rails
46:14 What finance looks like in five years
48:55 Two books on surfing entropy
Your agent needs data it can actually work with.
Pulse handles that; turning complex documents like financial statements, contracts, and claims into clean markdown and structured data for agents.
With MPP, agents can access and use Pulse via API. No accounts needed:
Agentic payments are now live on @Pulse__AI .
An agent can point at our API with no account, no API key, and no signup, and pay for extraction on its own, one call at a time.
It runs on the Machine Payments Protocol (MPP), settling inline over HTTP in USDC, in the same request that asks for the work. The agent sends an extraction request, Pulse answers 402 Payment Required with the priced terms, the agent pays and retries with proof, and the result comes back. Two round trips, no invoice to reconcile.
The 402 has sat reserved since the early days of HTTP, waiting for a caller that could pay on its own. It’s live on Pulse today, more here:
runpulse.com/blog/welcome-to…
MPP now supports subscriptions, starting with stablecoins on @tempo.
Subscriptions are built for flows including:
• Recurring API access and MCP tools
• Paid plans and memberships
• Usage bundles that renew on a schedule
Live on Tempo, with more payment methods coming soon.
MPP discovery now supports multiple payment offers in a single document.
Services can declare every payment method, currency, and intent type they accept ahead of time. Registries get the full pricing surface in one fetch.
Full blog post below.
MPP now has official SDKs for Go and Ruby.
Both implement the full MPP flow: core types, payment methods, server middleware, and client transports.
Full blog post below.
The MPP Go SDK is maintained by @tempo
GitHub: github.com/tempoxyz/mpp-go
1
8
464
Introducing the Machine Payments Protocol: an open standard for machine payments co-authored by @tempo and @stripe
MPP is designed to be extensible and payment-method agnostic, already supporting stablecoins, cards, and more.







