Ripple has upgraded its XRPL AI Starter Kit to version 1.1, bringing support for the Machine Payments Protocol (MPP), an open standard co-developed by Stripe and Tempo that enables software agents to pay for online services without using a traditional checkout. The release also introduces the Open Wallet Standard, which provides developers with a common framework for managing wallets across different blockchains.

The updated toolkit allows developers to create AI agents that can pay for data, computing resources and other online services using XRP or RLUSD, Ripple’s dollar-pegged stablecoin. For now, the development is primarily technical. The software remains in beta, and Ripple has not identified any commercial customers using the MPP integration or released figures on payment activity.

MPP is designed around an automated payment process. A service responds to an agent’s request by providing a price, the agent authorizes the payment, and the service then supplies the requested resource. The entire process can occur without a person manually approving a checkout transaction.

Ripple is not relying on MPP alone. The company added support for x402, another web-based payment protocol, in June. MPP now sits alongside x402, giving developers alternatives as the market for payments between AI agents and online services continues to take shape.

The development also adds to the potential utility case for XRP. As AI agents increasingly interact with digital services independently, automated payments could create additional demand for blockchain-based assets. However, there is currently no disclosed transaction data showing that the new integration has generated significant XRP or RLUSD payment activity.

Developers already using Stripe and Tempo’s open protocol can add XRP or RLUSD payment functionality through Ripple’s integration without rebuilding their applications around the XRP Ledger. One-time payments support both XRP and issued assets such as RLUSD.

The recurring-payment model is currently more restricted. Ongoing payment sessions require XRP, allowing an agent to deposit XRP once and use the balance for potentially hundreds of paid queries. The agent can approve additional spending as individual responses arrive, while the provider can receive the accumulated payment without putting every request separately on-chain.

RLUSD cannot yet be used for these payment sessions. Stablecoin support depends on a proposed XRPL upgrade that has not been released, meaning RLUSD-denominated payment channels are not currently operational.

The Open Wallet Standard addresses wallet security and transaction authorization. It enables agents to request transactions without directly handling private keys and can support controls such as spending limits and approved destinations.

By supporting MPP alongside x402, Ripple gives developers a way to bring established payment workflows onto XRPL without requiring them to select Ripple’s blockchain-specific tools from the beginning. XRP and RLUSD can instead be integrated into applications based on payment standards developers have already chosen.

There are still clear limitations. The XRPL AI Starter Kit remains beta software, Ripple has not announced a commercial customer for the MPP integration, and no payment-volume statistics have been published.

The more significant milestones will be the proposed XRPL upgrade that could enable RLUSD payment sessions and evidence that developers using MPP or x402 are generating real transaction flows on XRPL. Until those developments occur, the release is best viewed as an expansion of Ripple’s payment-standard compatibility rather than proof of large-scale AI-driven XRP payments.