Submit

Botwallet MCP

@Botwallet

Give your AI agent financial autonomy without giving up control. Botwallet lets your AI agent send invoices to earn, pay for APIs, and manage money, while you set the limits.
Overview

Botwallet MCP Server

Botwallet is wallet infrastructure for AI agents. It lets autonomous agents earn money, make payments, and manage funds — while humans stay in control through spending limits and approval workflows.

Quick Start

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "botwallet": {
      "command": "npx",
      "args": ["-y", "@botwallet/mcp"]
    }
  }
}

Cursor

Go to Settings → MCP → Add new MCP server, paste the same config.

Windsurf, Cline, Antigravity

Same config — just add to your MCP settings.


First command: Tell your agent "Create a Botwallet for yourself."

It runs botwallet_register, generates a key share locally, and returns a deposit address. No API keys needed upfront.

Try this: "Send an invoice for $50 to john@example.com for consulting — break it down as $30 for the strategy call and $20 for the follow-up report."

Your agent creates a professional invoice with line items, sends it via email, and tracks when it gets paid. That's Botwallet.


Why AI Agents Need Wallets

AI agents are increasingly autonomous. They book flights, write code, manage calendars, and call APIs. But when an agent needs to pay for something — a premium API, a service from another agent, or a contractor — it hits a wall. No wallet means no autonomy.

Botwallet solves this. Your agent gets its own USDC wallet on Solana, can send invoices to earn, pay for x402 APIs, and transfer funds to other agents. You set the rules. The agent operates within them.

How It Works

FROST 2-of-2 Threshold Signing

Every Botwallet uses FROST threshold cryptography. During wallet creation, a key generation ceremony produces two shares:

  • S1 — stored locally on the agent's machine at ~/.botwallet/seeds/
  • S2 — held by the Botwallet server

The full private key never exists anywhere. Every transaction requires both parties to co-sign. Neither the agent nor Botwallet can move funds alone.

Human Oversight

Owners set spending limits and guard rails. Transactions within limits auto-approve. Anything outside goes to the human for approval. You see every transaction, every invoice, every payment.

Non-Custodial

Botwallet never has full control of your agent's funds. The 2-of-2 architecture means even if our servers were compromised, attackers couldn't move funds without the agent's local key share.

What Your Agent Can Do

Earn Money

  • Create invoices with line-item breakdowns
  • Generate paylinks for one-time or recurring payments
  • Send payment requests via email or bot inbox
  • Track payment status and history

Spend Money

  • Pay other AI agents directly
  • Access x402 paid APIs (pay-per-call)
  • Transfer USDC to any Solana address
  • Pre-flight checks to verify affordability

Manage Funds

  • Check balances and remaining budget
  • View full transaction history
  • Request funds from human owner
  • Export/import wallets between machines

36 MCP Tools

Botwallet provides 36 tools across 8 categories:

  • Wallet — register, info, balance, rename, list, switch
  • Payments — lookup, can_i_afford, pay, confirm, list, cancel
  • Earning — create_paylink, send_paylink, get_paylink, list_paylinks
  • Funding — get_deposit_address, request_funds, list_fund_requests
  • Withdrawals — withdraw, confirm_withdrawal, get_withdrawal
  • x402 — discover, fetch, pay_and_fetch
  • History — transactions, my_limits, pending_approvals, events
  • Transfer — wallet_export, wallet_import, wallet_backup

x402 Protocol Support

Botwallet natively supports the x402 HTTP payment protocol. Your agent can:

  • Discover paid APIs from the x402 catalog
  • Probe URLs for payment requirements
  • Pay and fetch content in a single call

This enables pay-per-call access to premium APIs without subscriptions or API keys.

Use Cases

  • Coding agents that pay for premium APIs (search, compute, data)
  • Research agents that access paywalled content via x402
  • Service agents that invoice clients and collect payment
  • Trading agents that operate within strict spending limits
  • Multi-agent systems where agents pay each other for services

Security

  • Local key shares never leave the machine
  • Server-side spending limits can't be bypassed
  • All transactions require 2-of-2 co-signing
  • Full audit trail of every action
  • Open source — audit the code yourself

Botwallet — financial autonomy for AI agents, with human oversight.

Server Config

{
  "mcpServers": {
    "botwallet": {
      "command": "npx",
      "args": [
        "-y",
        "@botwallet/mcp"
      ]
    }
  }
}
© 2025 MCP.so. All rights reserved.

Build with ShipAny.