Ripple Eyes AI Payments in XRP and RLUSD as USDC Dominates
Ripple wants AI agents to pay in XRP and RLUSD. The market is still mostly USDC
Ripple is positioning its payments network around a new use case: enabling AI agents to send and receive value using XRP and RLUSD. The push reflects a broader effort in crypto to build “machine-to-machine” payment rails, where software agents can settle costs automatically without relying on traditional card networks or bank transfers.
At the same time, Ripple is entering a market where stablecoin activity is already heavily concentrated. Despite new entrants and alternative rails, most on-chain stablecoin usage still runs through USD Coin (USDC), which remains a dominant settlement asset for digital payments and exchange liquidity.
The contrast matters because AI-agent payments are often framed as a natural fit for stablecoins: they are dollar-denominated, relatively predictable compared with volatile tokens, and widely integrated across wallets, exchanges, and decentralized finance applications. Ripple’s plan implies that it wants both a volatile asset (XRP) and a dollar-pegged asset (RLUSD) to be viable settlement options for these automated transactions.
In practice, the stablecoin market’s current structure creates an adoption challenge. Payment systems tend to benefit from network effects: the most useful asset is often the one already accepted and integrated across the most venues. With USDC still serving as the primary stablecoin for many on-chain payment flows, new payment initiatives tied to RLUSD must compete on distribution, integrations, and trust.
Ripple’s move also underscores a larger industry trend: crypto firms are increasingly aligning their products with AI infrastructure narratives, especially around microtransactions, automated billing, and programmable payments. Whether AI agents ultimately adopt specific crypto assets will depend less on messaging and more on concrete factors such as settlement reliability, compliance readiness, liquidity, and how easily developers can integrate them into existing stacks.
