Ripple’s MPP AI Kit Arrives as XRP Payment Use Expands

Ripple has updated its XRPL AI Starter Kit to version 1.1, adding the Machine Payments Protocol (MPP), an open standard developed by Stripe and Tempo that allows software agents to pay for digital services without going through a conventional checkout. The release also adds Open Wallet Standard support, creating a unified interface for wallet management across multiple blockchains.

The update gives developers the ability to create AI agents that can pay for data, computing resources and other online services using XRP or RLUSD, Ripple’s dollar-pegged stablecoin. The announcement is primarily a technical development for now, as the toolkit remains in beta. Ripple has not disclosed any commercial customers using the MPP integration or provided payment-volume figures.

MPP operates through an automated sequence. A service quotes a price after receiving an agent’s request, the agent approves the payment, and the requested service or resource is delivered. This allows payments to take place within an agent’s workflow without requiring a user to complete a checkout.

Ripple is also taking a multi-standard approach to AI payments. It introduced support for x402, another web-payment protocol, in June, and MPP has now been added alongside it. The approach gives developers flexibility while the market continues to develop and no single payment standard has emerged as dominant.

The integration could add another potential utility case for XRP as AI agents become more capable of interacting with online services and making payments independently. However, Ripple has not released data showing meaningful payment activity through the new MPP functionality.

Developers already using Stripe and Tempo’s protocol can integrate XRP or RLUSD payments without rebuilding their applications around a different blockchain. Both XRP and issued assets such as RLUSD are available for one-time payments.

Recurring payment sessions currently support XRP only. The model allows an AI agent to deposit XRP and use the balance for numerous paid requests, approving additional spending as each response is received. Instead of placing every query on-chain separately, the service provider can collect the resulting accumulated payment.

RLUSD support for these sessions has not yet gone live. It depends on a proposed XRPL upgrade that remains undeployed, so stablecoin-based payment channels are not currently available.

The Open Wallet Standard addresses transaction authorization and wallet security. It allows AI agents to initiate transaction requests without directly accessing private keys, while controls such as spending limits and approved destinations can be incorporated.

Supporting both MPP and x402 gives developers a path to connect existing payment workflows with the XRP Ledger. Ripple can therefore introduce XRP and RLUSD to applications whose developers may have selected their payment standards before deciding which blockchain to use.

Commercial adoption remains unconfirmed. The toolkit is still in beta, Ripple has not named a customer using the MPP integration, and no payment-volume data has been published.

The next developments to monitor are the proposed XRPL upgrade that could enable RLUSD payment sessions and whether applications using MPP or x402 begin producing measurable transaction activity on XRPL. Until then, the release expands Ripple’s technical reach across emerging agent-payment standards without demonstrating large-scale XRP payment adoption.