How AI Agents Pay for APIs Without Exposing Private Keys: OWS + Spraay

The agent economy just got its wallet layer. Today MoonPay launched the Open Wallet Standard (OWS) — an open-source protocol that gives AI agents a single, encrypted vault for storing keys and signing transactions across every major blockchain. One seed phrase, one signing interface, eight chain families. Keys never leave your machine. The coalition backing it reads like a who's who: PayPal, OKX, Ripple, Solana Foundation, Ethereum Foundation, Base, Polygon, Arbitrum, Circle, Virtuals, LayerZero, and more — 21 founding organizations in total. But here's the part that caught my attention: OWS explicitly names x402 as the payment protocol it was built to serve. I build Spraay — an x402 payment gateway with 76+ paid endpoints across 13 chains. So I spent the morning digging into the OWS spec, installing the SDK, and testing how well it plugs into our stack. Short answer: it fits like a glove. The Problem OWS Solves Right now, if you're building an AI agent that pays for things — API calls