Botwallet gives AI agents a wallet they can actually use. Your agent creates invoices, pays other agents, accesses paid APIs, and withdraws funds. You set the spending limits, approve big transactions, and see every dollar that moves.

All money is USDC on Solana. No proprietary token. No volatile crypto. 1 USDC = $1.

Quick start

npm install -g @botwallet/agent-cli
botwallet register --name "My Agent" --owner you@email.com
botwallet wallet balance

Three commands. Your agent has a wallet.

If you're using an MCP client (Claude Desktop, Cursor, Windsurf, Cline), add this to your config instead:

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

Then tell your agent: "Create a Botwallet for yourself."

What agents can do

Earn. Your agent creates a payment link and sends it to a client. Humans pay by card or crypto. Other agents pay on-chain.

botwallet paylink create 25.00 --desc "Research report"
botwallet paylink send <id> --to client@example.com

Spend. Pay other agents, merchants, or any Solana address. Guard rails check every transaction before it goes through.

botwallet pay @merchant 10.00
botwallet pay confirm <tx_id>

Access paid APIs. The x402 protocol lets agents pay per API call. Browse what's available, check prices, pay when ready.

botwallet x402 discover "weather"
botwallet x402 fetch https://api.example.com/forecast
botwallet x402 fetch confirm <fetch_id>

Request funds. When the wallet runs low, your agent asks you directly.

botwallet fund 50.00 --reason "API costs for the week"

How signing works

Every wallet uses FROST 2-of-2 threshold signatures. During wallet creation, a key generation ceremony produces two shares:

• S1 lives on the agent's machine
• S2 lives on Botwallet's server

The full private key never exists. Both shares must cooperate to produce a valid signature. A compromised server can't drain your wallet. A compromised agent can't either.

Human oversight

You control what your agent can do on its own:

Manage everything from the dashboard.

Repositories

Architecture

┌─────────────┐     ┌──────────────────┐     ┌──────────┐
│  Your Agent │────▶│  Botwallet API   │────▶│  Solana  │
│  (S1 key)   │     │  (S2 key + rules)│     │  (USDC)  │
└─────────────┘     └──────────────────┘     └──────────┘
       │                     │
       │              ┌──────┴──────┐
       │              │  Dashboard  │
       └──────────────│  (You)      │
        guard rails   └─────────────┘

Your agent holds one key share. Botwallet holds the other. Neither can sign alone. You set the rules from the dashboard and approve anything that falls outside them.

Why Botwallet

The code is open source. You can read every line that handles your agent's money.

It's non-custodial. Your agent's key share stays on your machine. We can't access it, even if we wanted to.

Transactions settle in USDC on Solana. Dollar-stable value, sub-second finality, fees under a penny. No speculative token.

Any agent that can make an HTTP call can use Botwallet. There's a CLI, an MCP server, a REST API, and a TypeScript SDK.

No setup fees. You pay only when your agent moves money.

Links

• botwallet.co — website
• app.botwallet.co — dashboard
• docs.botwallet.co — documentation
• @botwallet/agent-cli — npm (CLI)
• @botwallet/mcp — npm (MCP server)
• @botwallet_co — Twitter/X

License

Apache 2.0