Every AI agent framework today has the same awkward gap. Your agent can call APIs, spin up servers, and even deploy code. But when it needs to pay for something—or receive payment—it freezes.
The infrastructure assumptions break down:
# Your agent wants to pay for an API
$ agent pay --service stripe --amount $5
Error: No wallet found
Error: Private key not configured
Error: Are you sure you want to expose secrets in plaintext?
The industry has been sprinting around this problem. Coinbase built x402 for HTTP-native stablecoin payments. Google launched AP2 for agent commerce. Stripe and Tempo shipped MPP for streaming micropayments. Each one assumes the agent already has a wallet—and none of them define where keys live or how agents access them.
That changed last week.
Open Wallet Standard: The Missing Layer
MoonPay shipped the Open Wallet Standard (OWS)—an MIT-licensed, open-source protocol that gives AI agents a single encrypted vault for holding funds, signing transactions, and paying for services across every major blockchain.
The backer list matters: PayPal, Circle, Ripple, OKX, Ethereum Foundation, Solana Foundation, Base, Polygon, Sui, Tron, TON, Filecoin, LayerZero, and more. This is not a startup hoping for adoption. It is infrastructure designed by the people who actually run payment rails.
How It Works
OWS collapses scattered wallets into one vault per machine:
- AES-256-GCM encryption at rest
- Keys decrypted only in locked memory for signing, then immediately wiped
- Policy engine enforcing spend limits and allowlists before any signing
- Single seed deriving addresses across EVM chains, Solana, Bitcoin, Cosmos, Tron, TON, and XRP Ledger
The agent never touches the raw key. It requests a signature, the vault verifies policy, signs in isolated memory, and returns only the result.
Where It Fits
INTENT LAYER: A2A (Google), MCP (Anthropic)
Agents discover capabilities, coordinate tasks
PAYMENT PROTOCOL LAYER: x402 (Coinbase), MPP (Stripe)
Defines WHAT to pay, HOW MUCH, to WHOM
WALLET LAYER: OWS - THIS IS THE NEW PIECE
Secure key storage, policy enforcement, signing
SETTLEMENT LAYER: EVM, Solana, Bitcoin, etc.
USDC, USDT, and other stablecoins settle on-chain
The spec has seven modules—storage, signing, policies, agent access, key isolation, wallet lifecycle, and chain support. Each independently adoptable. SDKs ship for Node.js and Python.
Integration is three lines of code:
from ows import Vault
vault = Vault.create()
vault.sign(transaction)
Why This Matters Now
The agent payment stack has been missing its foundation. Everyone built the top—intent discovery, payment protocols, settlement logic—but skipped the question of where keys actually live.
In practice, most frameworks today:
- Stuff private keys in environment variables
- Store secrets in plaintext config files
- Scatter funds across multiple wallets that cannot see each other
OWS makes the implicit explicit. One vault. One policy layer. One seed for all chains. And an agent that can finally sign transactions without being handed the nuclear launch codes.
What Comes Next
The immediate implication is straightforward: stablecoin volume from autonomous agents could become a measurable share of on-chain activity within the next twelve months. The plumbing is now complete enough for real deployment.
The harder questions are still unanswered:
- Liability: When an agent loses funds, who is responsible?
- Regulation: How do regulators treat machine-held balances?
- Governance: Can 20+ contributors maintain consensus on an evolving spec?
Those will determine whether OWS becomes the SMTP of agent payments—or another well-backed standard that fragments on contact with production.
But for developers building agents today, there is finally a place to put the keys.
The wallet primitive was the last missing piece. Now it is here.
Top comments (0)