MoonPay has open-sourced what it calls the wallet layer for the emerging agent economy, launching the Open Wallet Standard as a new framework for how AI agents hold funds, sign transactions, and pay for services across blockchains. The company said the standard is designed to give agents a universal wallet interface without exposing private keys to the agent itself, the model, or the parent application.
The release matters because it targets a gap MoonPay says still exists in agent infrastructure. Payment rails for AI agents are starting to emerge, but wallet access, key storage, and cross-framework portability remain fragmented. MoonPay is trying to make that wallet layer open, reusable, and multi-chain from day one.
What MoonPay announced
MoonPay said it has launched the Open Wallet Standard, an MIT-licensed open-source standard for AI-agent wallets. The company said the software is available now on GitHub, npm, and PyPI, and that more than 15 organizations contributed to the launch.
According to the release, the standard grew out of MoonPay’s own internal work on MoonPay Agents, a non-custodial software layer it launched in February 2026. MoonPay said it took that wallet infrastructure, generalized it across runtimes and chains, and released it as a broader standard rather than keeping it proprietary.
What problem it is trying to solve
MoonPay’s core argument is that agent payments are developing faster than agent wallet standards. In the release, the company points to recent progress in areas like machine payments, agent commerce, and on-chain identity, but says those systems still assume the agent already has a usable wallet.
That creates fragmentation. MoonPay said different agent frameworks currently implement their own signing logic, key management, and wallet formats, which makes wallets hard to reuse across tools and increases the risk of insecure setups like plaintext configuration files or exposed environment variables.
In MoonPay’s framing, the Open Wallet Standard is meant to be the shared wallet layer underneath those payment and agent protocols. In plain English, it is trying to make one wallet usable across multiple agent tools and blockchain environments instead of forcing every agent stack to reinvent the same security model.
Key details on how the standard works
The release says the standard is modular and launches with seven sub-specifications covering storage, signing, policies, agent access, key isolation, wallet lifecycle, and supported chains. MoonPay said each module can be adopted independently, which suggests teams will not need to take the whole stack at once.
Security is the central selling point. MoonPay said private keys stay inside an encrypted local vault and are never exposed directly to the agent or model context. The company also said a pre-signing policy engine can enforce spending limits, allowlists, chain restrictions, and time-bound permissions before a transaction is signed.
MoonPay also described the system as local-first. The wallet vault lives on the user’s own machine, while signing happens without relying on remote cloud key management. The release says the main network dependency is broadcasting the already signed transaction.
What developers and agents get
MoonPay said the standard includes native SDK bindings for Node.js and Python, along with a CLI and an MCP server interface. It also said agents built on Claude, ChatGPT, LangChain, and other MCP-compatible frameworks can access wallets through their native tool systems.
The company added that the standard supports wallet portability and broad chain access. Its pitch is that developers can treat networks as first-class citizens within the same wallet framework, rather than building chain-specific wallet logic for each separate agent deployment.
Why this matters now
This launch shows where crypto and AI infrastructure are starting to overlap more seriously. Over the last year, the market has spent a lot of time on how agents make payments or prove identity. MoonPay is making the case that the next important layer is the wallet itself: where value sits, how keys stay protected, and how different agents use the same funds safely.
It also suggests that the early agent economy may be heading toward shared standards faster than many earlier crypto infrastructure categories did. MoonPay is not presenting this as a closed product advantage. It is presenting it as common infrastructure that should make adjacent protocols more usable. That does not guarantee adoption, but it does make the release more important than a narrow product update.
Why it matters for crypto
- It pushes wallet infrastructure into the center of the AI-agent stack, not just payments or identity.
- It gives developers a multi-chain, open-source framework for agent wallets with local key control and policy-based signing.
- It suggests crypto wallet design may increasingly be shaped by machine users, not only human users.
- It strengthens the case for open standards in agent payments, especially as more protocols and frameworks try to work together.
What to watch next
- Whether outside developers and agent frameworks adopt the Open Wallet Standard in meaningful numbers. MoonPay announced contributors, but not usage metrics.
- Whether other wallet providers and infrastructure firms decide to support the same standard instead of pushing their own formats. This is an inference based on the interoperability problem MoonPay describes.
- Whether the standard becomes a default wallet layer for machine payments tied to protocols like x402 or MPP. MoonPay clearly wants that outcome, but it is not yet proven.
- Whether policy-based signing and local vault design become baseline expectations for agent wallets across the industry.