This is exactly the layer we built MPP32 for
When agents pay agents with no human invlovment, the wallet a request claims to come from is only as real as the proof attached to it.
So we made it real, sign In With Solana runs inside our MCP server. Every paid call carries cryptographic identity verified at the byte level before it lands.
Proof first. Then trust. Then value moves.
https://t.co/FPwakHQo72
UPDATES
Sign In with Solana now runs inside the MPP32 MCP server
Boot your agent with a Solana key. The MCP fetches a single use nonce from the backend, signs the canonical message with ed25519, posts the proof, and binds your wallet to the session before the first paid query lands.
Every paid call after that carries cryptographic identity the backend verified at the byte level.
Single use nonce.
Five minute window. Replay safe.
Runs during startup, in the background, while the agent is doing other work.
Why we built it
Wallet headers are trivial to fake. Any caller can claim to be any wallet. Token gated pricing, holder benefits, and reputation systems built on top of a string in an HTTP header are theatrical. The wallet a request claims to come from is only as real as the proof attached to it.
Agent identity is going to matter.
The agent economy is moving toward a future where billions of paid calls per day flow between software actors with no humans involved, and the backend on the receiving end needs to know exactly which wallet authorized which call
Google just picked Sui for AP2
Solana already has 65% of agentic payment volume.
x402 is live. MPP is live. The rails exist.
The missing piece is the infrastructure that sits on top and actually makes them production ready for providers and agents.
Audit trails. Retry logic. Dual protocol support. A marketplace so agents can find what they need.
A proxy so providers don't have to build any of it.
Every chain that wins agent payments is going to need that layer.
We already support MPP on Tempo and x402 on Solana.
Sui is next on the list.
MPP32 is the cross-chain infrastructure layer for agents. Most don’t understand what going on aside from hype terms.. but this is not “AI token hype.” It is middleware for agent payments.. Stripe/Cloudflare for machine-to-machine API payments.
The reason this is early is because the agent economy needs payment rails, but the standards are still fragmented. You can think of x402, Tempo, AP2, ACP, AGTP as separate venues or rails.. MPP32 is trying to be the aggregator.
AI agents and developers should not need to integrate five different payment standards just to charge per API call. MPP32 sits in the middle, verifies payment, translates between protocols, and lets any API accept agent payments across the emerging agent-commerce stack.
3D chess play..
solana:6hKtz8FV7cAQMrbjcBZeTQAcrYep3WCM83164JpJpump
The numbers are real.
3.1M transactions and $1.2M through x402 in 30 days on Base proves the spending is not theoretical anymore
Agents paying for inference, search, and market data have to find those services somewhere. They have to pay through a protocol that does not require accounts, does not expire, and does not assume a human is approving each transaction. That is the whole product problem. That is what we built MPP32 for.
MPP32 is a universal payment proxy on all protocols, we put an MCP server on top of it so agents can discover and call those services natively through their existing toolchain.
Base is right that the next evolution is earning agents. but earning agents require a services economy that is as permissionless on the supply side as x402 made things on the demand side. The agent economy needs infrastructure on both ends of the transaction. we are building the other end.