Show HN: Openspender gives your agents wallets

OpenSpender launched a self-custodial wallet that lets AI agents pay for API calls per request at provider prices, with no per-provider accounts or keys. The wallet supports MCP-compatible agents like Claude Code, ChatGPT, and Codex, and uses x402 and MPP payment standards. OpenSpender charges no subscription or markup, and users retain full control of funds.

One wallet your agents spend from. Fund it once and every model, search, image, and compute call settles per request at the provider's own price — no account and no key per provider. Who holds the money? You do. The wallet is self-custodial and OpenSpender never holds your funds. Top it up, move it out, or empty it from your wallet at any time. How do the caps work? Agents spend through an allowance, never your keys. Each allowance carries a per-request cap, a daily cap, an optional total cap, and the hosts it may pay. Edit or delete it and the change lands on that agent at its next request. Which agents can use it? Anything that speaks MCP. Claude Code and claude.ai, ChatGPT, Codex, and opencode each have a one-line setup in the quickstart; other MCP clients — Cursor and Gemini CLI included — take the same server URL. What are x402 and MPP? The two machine-payment standards OpenSpender speaks. The agent calls a paid endpoint, the endpoint answers with a price, the wallet settles it, and the response comes back — no key exchange in between. Browse x402 and MPP services. What does it cost? No subscription, no markup, and no account with us. Each request settles at the provider's price and that is the whole bill.