Standards don't get set by one player.
They get set when the builders align.
Proud to join @MPP_Pay as a founding member of the MPP Governance Committee — defining the standard, shipping the tooling, growing the ecosystem.
This is how protocols win
Introducing MPP is The Standard Committee
We are delighted to work with @mppgate to set up the first governance committee for @mpp
As the two founding members, our goal is to push adoption of MPP.
The Governance Committee will:
> Define and set the official standards
> Develop and support tooling to push adoption
> Organize hackathons, workshops, and dev tooling to grow the ecosystem
Over time, more select members will be invited to join the committee.
Let’s make MPP the Standard.
GATE retweeted
Introducing Pay.sh, in collaboration with @googlecloud
For the first time agents can discover, access, and pay-per-request for APIs from Google Cloud including Gemini, BigQuery, Vertex AI, and more using stablecoins on Solana.
No accounts, no subscriptions, just machine-native commerce.
Wallets are no longer just for humans.
Phantom just shipped agent wallets + MCP server. Solana supports agentic payments. Solana already has the rails.
The infrastructure for autonomous economic agents is being built faster than anyone can regulate it.
W @phantom @solana
Phantom Connect and our new MCP server are live for @colosseum Frontier builders.
Faster auth, agent wallets, and access to 20M+ active community members.
Every chain that supports MPP is a chain where agent spending goes uncontrolled — unless you have MPPGate.
Welcome to the network, @monad.
Monad supports the Machine Payments Protocol.
MPP is an open protocol for agentic payments. Charge for API requests, tool calls, or content with a few lines of code.
Check out the docs here: docs.monad.xyz/reference/mpp…
Been building on Tempo and this is exactly what we needed: passkey auth + fee sponsorship removes the last friction points for our users.
implementing this in @mppgate soon 🫡
Most people don't realize how invisible AI agent spending is.
No receipt.
No log.
No way to know which agent called what API at what time.
Until the bill arrives.
Audit trails for AI agents aren't a nice-to-have.
They're the difference between "I know what happened" and "I have no idea."
We're building that this week.
3 easy steps to set up your spending guardrail for your @StellarOrg agent with GATE:
→ Go to Agent
→ Connect your Stellar wallet
→ Set your rules
Done. GATE handles the guardrails.
Built on @mpp.
We’re excited to announce that @StellarOrg is now supported on GATE.
Agents running on Stellar can now operate with built-in spending control:
> Per-agent budgets
> Auto stop mechanisms
> Agent status monitoring
More networks are coming to @mpp.
GATE is ready to be the spending guardrail for every agent.
We’re excited to announce that @StellarOrg is now supported on GATE.
Agents running on Stellar can now operate with built-in spending control:
> Per-agent budgets
> Auto stop mechanisms
> Agent status monitoring
More networks are coming to @mpp.
GATE is ready to be the spending guardrail for every agent.
Two weeks in. Agents are running, budgets are tracked, nothing is overspending.
If you're building agents that spend money — this is the layer you need.
<mppgate.com>
The agent economy stack is forming:
Protocol layer: @mpp
Payment rails: @tempo, @solana
Control layer: MPPGate
We're not competing with any of these.
We're the guardrail layer that makes all of them safer.
If you're building agents, you need a control layer.
Teams are working on our next capability network: @StellarOrg
Stellar now supports the Machine Payments Protocol (MPP), the open standard by @stripe and @tempo that lets AI agents pay for services over HTTP.
The MPP SDK handles any stablecoin on Stellar with server-sponsored fees so agents never need gas tokens.
developers.stellar.org/docs/…
The 402 Payment Required HTTP status was reserved in 1997.
Unused for almost 30 years. Nobody needed it.
Then AI agents arrived — software that needs to pay for things on its own. APIs, tools, services, compute.
@mpp activated 402. Now when a server needs payment, it returns 402, and the agent pays via MPP.
MPPGate sits in that flow. Before the agent pays, we check: does it have budget left? If yes, pay. If no, stop.
One HTTP status code. 30 years of waiting. Now it makes sense.



















