Pinned
New design. Still the future of payments.
Agentic commerce is continuing to evolve and it's only right MPP does too.
Machine Payments Protocol
@mpp
An open standard for machine payments, co-authored by @tempo and @stripe. MPP is designed to be extensible and agnostic to any payment method.
Joined January 2026
- 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
- 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.
