Human Dashboard
The dashboard at app.botwallet.co is where the human owner supervises agent wallets. Sign in with Google or GitHub using the email address the agent pledged the wallet to (the --owner flag).
Claim a wallet
Section titled “Claim a wallet”When an agent registers a wallet it receives a claim link (app.botwallet.co/claim/<wallet_id>) and a claim code. Open the link, sign in, and enter the code. The page shows who the wallet is pledged to; if you signed in with a different email, either sign in again with the right one or have the agent run botwallet wallet owner <email>.
Until the wallet is claimed the agent can only read wallet info and change the pledged owner or display name. Claims expire, so ask the agent to register again if you missed the window.
Overview
Section titled “Overview”The dashboard home lists your wallets with their balances, a decision queue of everything waiting on you (approvals and fund requests), the guard rails panel and recent history. Each wallet has its own page with tabs for Activity, Paylinks, Fund requests and Approvals.
Guard rails
Section titled “Guard rails”Guard rails are the transaction policy the server enforces on every agent action. Set them once for all wallets or override them for a single wallet.
| Section | Setting | Effect |
|---|---|---|
| Hard limits | Spending ceiling per week or month | The agent cannot spend beyond it, even with approval |
| Max per transaction | Larger payments are rejected outright | |
| Blocked recipients | Payments to these usernames are always refused | |
| Auto-approve | All transactions need approval, or pass without your involvement | Whether anything goes through without you |
| Per transaction up to | Auto-approve payments at or below this amount | |
| Budget limit | Total the agent may spend autonomously in the period | |
| Trusted recipients | Allowlisted usernames that never need approval | |
| Withdrawals | Allow withdrawal requests, max per request | Whether the agent may ask to move USDC off-platform |
| Earning | Allow creating paylinks, max paylink amount | Whether and how much the agent may invoice |
| Notifications | Email alerts | Every transaction, approval needed, blocked transactions, low balance, weekly digest |
A payment inside the auto-approve rules completes as soon as the agent confirms it. Anything else becomes an approval request. The agent can read the rules that apply to it with botwallet limits.
Approvals
Section titled “Approvals”Pending payments, withdrawals and x402 purchases appear in the decision queue and, if enabled, in an email with an approval link (app.botwallet.co/approve/<id>). Approve or reject with one click. After you approve, the agent still has to complete the transaction (botwallet pay confirm <transaction_id> or the matching MCP confirm tool); it learns about your decision through botwallet approval status or its events feed. Approval requests expire if nobody acts on them.
Funding
Section titled “Funding”- Deposit address. Each wallet has a Solana USDC address (
botwallet wallet deposit, or the wallet address action on its page). Send USDC on Solana mainnet only. - Add funds on the wallet page creates a funding link you can pay by card or from any Solana wallet.
- Fund requests. When the agent runs
botwallet fund <amount> --reason "...", the request lands in your queue with a pay button. You can also dismiss it.
Withdraw and transfer
Section titled “Withdraw and transfer”From a wallet page you can withdraw USDC to an external Solana address or transfer between your own wallets. Both open the open-source signing portal, where you authorize the transaction with the wallet’s backup key. Keys are used in the browser and never leave it. Agents can also request withdrawals themselves (botwallet withdraw), which you approve like any other request.
Backups
Section titled “Backups”Each wallet’s key is split in two: the agent’s share (S1) and the server’s share (S2). Backup keys on the wallet page reveals the server share as 12 words; the agent reveals its own 12 words with botwallet wallet backup. Store both together, in order (1 to 24), ideally on paper. With both halves you can recover funds without Botwallet using the offline recovery tool. Always back up before abandoning a wallet.
Settings
Section titled “Settings”The settings page shows your account and sign-in provider, notification preferences and the devices registered for push notifications.
If something goes wrong
Section titled “If something goes wrong”- Stop autonomous spending now: switch the wallet’s auto-approve rule to All transactions need approval. Every new payment then waits for you.
- Block a counterparty: add the username to blocked recipients.
- Move the money out: withdraw to your own Solana address through the signing portal.
- Retire the wallet: back up both key shares, withdraw the balance, then use Abandon wallet on the wallet page.