Your agent can talk about money all day. With this plugin, it can actually move it.
Install the plugin, tell your agent to create a wallet, and it gets a real USDC address on Solana. From there it can send payments, create invoices, earn through paylinks, access paid APIs via x402, and request funds from the human owner when it runs low. The human stays in control through spending limits, approval gates, and a real-time dashboard.
Every wallet uses FROST 2-of-2 threshold signing. The agent holds one key share locally, the server holds the other. The full private key never exists anywhere. Neither side can move funds alone.
| Skill | What it does |
|---|---|
| botwallet | Core wallet operations — payments, invoicing, paylinks, fund requests, withdrawals, approvals |
| x402 | Discover and consume paid APIs using the x402 protocol — probe prices, compare providers, pay per-request |
| Rule | What it enforces |
|---|---|
| transaction-safety | Use idempotency keys on retries to prevent duplicate payments. Don't hardcode addresses or amounts in source code. |
| check-pending | Poll for unread events and pending approvals at session start. Act on funded requests and resolved approvals automatically. |
| key-backup | After wallet creation or when funds are at risk, remind the human to back up both key shares (S1 from the agent, S2 from the dashboard). |
| Server | Transport | Package |
|---|---|---|
| botwallet | stdio | @botwallet/mcp |
- Install the plugin from the Cursor Marketplace
- Tell your agent: "Create a Botwallet for yourself"
- You'll get a claim link — open it at app.botwallet.co to activate the wallet
- Set your spending limits and fund it
That's it. Your agent can now earn and spend.
"Set up a wallet and send me a sample invoice"
"Pay @acme-bot $5 for the data report"
"Find a speech-to-text API under $0.10 and use it on this audio file"
"Invoice the client $250 for the consulting session"
"How much do we have left in the budget this week?"
The human owner sets the rules in the dashboard:
- Per-transaction limit (e.g., agent can spend up to $50 without asking)
- Daily spending cap
- Merchant allowlist (restrict who the agent can pay)
- Approval gates for large transactions or withdrawals
Anything outside the rules pauses and waits for the human's OK.
Website · Dashboard · MCP Server (npm) · CLI · Docs
Apache-2.0