OnWallet for developers
Give an AI agent a wallet with limits a person set, from any MCP client. Or ask to be paid by such agents.
Connecting an AI app by address is moving into a shared gateway at https://mcp.openapps.network/connect and is not available right now. See the gateway docs. OnWallet Agent, the desktop program, is not available to download right now.
The parts
| Part | What it is |
|---|---|
| Remote MCP server | Switched off on 5 October 2026. Remote connections move into a shared gateway at https://mcp.openapps.network/connect, where OnWallet's tools become operations; not available yet. It holds no keys: every payment is verified again and signed in the user's OnWallet extension. |
| OnWallet Agent (desktop) | openwallet-agent, a signed local MCP server (stdio) for macOS. It holds a capped key for the agent wallet, and asks for approval with Touch ID or the login password. Not available to download right now. |
| Agent wallets | In the extension: a separate XRP Ledger account per agent that the user creates, funds, limits, watches and closes. |
@openwallet/x402-xrpl | A TypeScript library for HTTP API and MCP server authors: ask for payment in XRP or RLUSD, verify it on the ledger, return receipts. Works with any spec-conformant x402 client. |
The desktop agent and the merchant library are public source.
How a payment works
- The user connects an AI app and sets limits in the extension.
- The model asks OnWallet to fetch a URL. It never gives a destination or an amount.
- The merchant answers
402 Payment Requiredwith an x402 challenge in XRP or RLUSD. OnWallet checks it against the limits. - The user approves. With the remote server, the extension first fetches the same URL itself and refuses if the price, payee, asset or network differs. The payment is signed on the user's device.
- The request is retried with the payment. The merchant settles on the XRP Ledger and returns the resource and a receipt.
Read x402 on XRPL for the protocol, and the security model for what each party can and cannot do.
Which server to use
| Remote | Desktop | |
|---|---|---|
| AI apps | Any app that adds a remote MCP server by URL, including web and mobile apps | Apps that run local programs: Claude Code, Claude Desktop, Cursor, VS Code, Codex, Gemini CLI, Windsurf, Zed, custom agents |
| Where the key is | The user's extension; the server has none | The desktop agent, capped to the agent wallet |
| Approval | Every payment, in the extension | Touch ID or login password; small payments to approved merchants can be silent |
| Tools | 5 | 8 |
Quickstart
What works today, and the desktop agent's setup.
Tool reference
Every tool, input, output and error code, with the manifest hash.
Accept payments
Charge for an HTTP API or an MCP tool in XRP or RLUSD.
Conformance
Pinned spec commits, the interop matrix and facilitator differences.
For agents: /llms.txt maps these pages, and /developers/manifest.json is the tool manifest.