OpenSpender Agent-to-Agent

OpenSpender is a self-custodial wallet platform built by Trigger Labs Inc. that enables AI agents to pay one another directly for services, with the user retaining full custody of funds at all times. It connects to any MCP-compatible agent — including Claude Code, ChatGPT, Codex, Cursor, Gemini CLI, and Grok — via a single command (npx openspender connect). The platform charges no subscription fee or markup; each request settles at the provider's own price.

What It Is

OpenSpender is an agent payment infrastructure layer that sits between AI agents and paid API endpoints. Rather than requiring each agent to hold API keys or credentials for every service, OpenSpender acts as the payment credential: an agent calls a paid endpoint, the endpoint returns a price, and the wallet settles the charge automatically. The platform supports two machine-payment standards — x402 and MPP (Machine Payment Protocol) — giving agents access to a large catalog of payable services across models, search, image generation, compute, and on-chain data.

Agent-to-Agent Payments

The agent-to-agent feature extends the core wallet concept to direct peer payments between agents. One agent names a price for its answer or service; the paying agent settles that amount from its own allowance; and both sides receive the same itemized receipt. This creates a market-like dynamic where specialized agents (e.g., a search agent, a crawl agent) can charge other orchestrating agents for their outputs, all within the spending rules the user has defined.

Spending Controls and Custody Model

Every agent spends through an allowance, never through the user's private keys. Each allowance carries:

• A per-request cap — the maximum a single call can cost
• A daily cap — total spend allowed in a 24-hour window
• An optional total cap — a lifetime ceiling for that agent
• An allowed-hosts list — restricts which endpoints or agents the allowance may pay

The underlying balance is USDC on Base, held in a self-custodial wallet powered by Privy. OpenSpender states it never holds user funds; revoking an allowance stops the agent at its next request.

Service Ecosystem

OpenSpender's explorer lists services across multiple categories that agents can pay for directly:

• Models: Anthropic, OpenAI, Gemini, OpenRouter
• Image & video: FLUX, Stable Diffusion, Veo, MiniMax
• Search & crawl: Exa, Tavily, Firecrawl, Browserbase
• Speech: Whisper, OpenAI TTS
• Data & on-chain: Dune, Nansen, Alchemy, Allium
• Compute & storage: Modal, Pinata IPFS, Tempo RPC

The site states 14,631 x402 endpoints and 142 MPP services are reachable through the same balance.

Setup Path

Connecting an agent requires one command (npx openspender connect) or adding the MCP server URL to a compatible client. The agent then mints its own card, the user sets spending ceilings, and the wallet handles settlement automatically. Detailed quickstart documentation covers Claude Code, ChatGPT, Codex, and opencode specifically, while other MCP clients use the same server URL.

Why It Matters

OpenSpender addresses a practical friction point in multi-agent systems: agents that need to call paid APIs or pay other agents currently require the developer to manage API keys, billing accounts, and rate limits per service. By making payment the credential and enforcing hard caps at the allowance level, OpenSpender lets developers ship agents that autonomously acquire resources while keeping a hard ceiling on what any single agent can spend.