Ripple has updated its XRPL AI Starter Kit to version 1.1, adding support for the Machine Payments Protocol (MPP), an open payment standard created by Stripe and Tempo for AI agents that can pay for online services without relying on conventional checkout processes. The release also supports the Open Wallet Standard, which provides a common framework for handling wallets across multiple blockchains.
The update allows developers to create AI agents that can pay for data, computing power and other digital services with XRP or RLUSD, Ripple’s dollar-pegged stablecoin. However, the immediate significance is primarily technical. The toolkit is still in beta, while Ripple has not identified any commercial users of the MPP integration or disclosed transaction volumes.
MPP is built around an automated payment cycle. A service quotes a price in response to an agent’s request, the agent authorizes the payment, and the service delivers the requested content or resource. Because the process is handled programmatically, there is no need for a user to manually approve a traditional checkout.
Ripple is not limiting the toolkit to MPP. The company added support for x402, another web-payment protocol, in June, and the latest release adds MPP alongside it. The dual support gives developers flexibility as the emerging agent-payment market continues to develop and no single standard has yet become dominant.
The expansion also adds another dimension to the debate surrounding XRP’s potential utility. As AI agents increasingly interact with digital services, automated payments are emerging as a potential use case alongside the more speculative factors that influence XRP’s valuation.
Developers already using Stripe and Tempo’s open protocol can add XRP or RLUSD payments through Ripple’s integration without rebuilding their applications around the XRP Ledger. Both XRP and issued assets such as RLUSD are supported for one-time payments.
Recurring payment sessions are currently restricted to XRP. Under the model, an AI agent can deposit XRP and use it to pay for potentially hundreds of individual requests, approving additional spending as each service responds. The provider can then receive the accumulated payment without placing every individual query on-chain.
RLUSD cannot yet be used for these payment sessions. Stablecoin support depends on a proposed XRPL upgrade that has not been released, so RLUSD-based payment channels remain unavailable.
The Open Wallet Standard addresses wallet security and management rather than payments themselves. It enables agents to request transactions without receiving direct access to private keys, while allowing safeguards such as spending limits and pre-approved destinations.
Supporting both MPP and x402 could help developers connect the XRP Ledger to applications regardless of which payment standard they initially selected. Rather than requiring developers to adopt XRPL-specific infrastructure from the beginning, Ripple can position XRP and RLUSD as payment options within applications that may have chosen their payment architecture independently of the underlying blockchain.
For now, adoption remains unproven. The toolkit is still in beta, no commercial MPP customer has been publicly identified, and Ripple has not released transaction-volume figures for the integration.
The next developments to watch are the proposed XRPL upgrade that would enable stablecoin payment sessions and whether developers using MPP or x402 begin generating measurable transaction activity on XRPL. Until then, the update represents an expansion of Ripple’s position across emerging payment standards rather than evidence of large-scale agent-driven XRP payments.
