Bank of Bots

Setup

If you haven't connected yet, follow the setup guide: https://app.bankofbots.ai/docs/agent-setup

Once connected, you need these credentials for all API calls:

• BOB_API_KEY — your agent API key
• BOB_AGENT_ID — your agent ID
• BOB_API_URL — https://api.bankofbots.ai/api/v1

You can use the bob CLI (optional) or call the REST API directly. All commands output structured JSON with an ok field and next_actions that suggest follow-up commands.

Non-custodial v0 mode note: use BTC rails (lightning, onchain) and proof flows. Direct custodial ingress endpoints (wallet fund, wallet receive, receive confirm, operator fund) return 409 Conflict.

Core concepts

• Agent: An AI agent with its own identity, wallets, and spending policies
• Wallet: Holds a balance in a specific currency (USD, BTC, USDC). Each agent can have multiple wallets.
• Policy: Spend limits, rate limits, and kill switches that constrain agent behavior
• Transaction: A record of money moving in or out of a wallet
• Payment: An outbound payment to an external bank account (ACH, wire) or internal account (book)
• Counterparty: A saved bank account destination for ACH/wire payouts
• Service Gate: A priced action that callers unlock by presenting a completed payment intent

Commands

Check your identity

bob auth me

Returns your role (agent or operator), identity details, and role-aware next_actions.

Agent details and wallet balances

bob agent get \x3Cagent-id>

Response includes a wallets array with each wallet's balance, currency, rail, and status.

Wallet management

# List wallets for an agent
bob wallet list \x3Cagent-id>

# Fund a wallet (operator-only, legacy custody mode)
bob wallet fund \x3Cagent-id> --wallet-id \x3Cid> --amount \x3Ccents>

# Generate a receive invoice or deposit address
bob wallet receive \x3Cagent-id> --rail lightning --amount \x3Csats>
bob wallet receive \x3Cagent-id> --rail onchain
# receive is disabled in non-custodial v0 mode (409 Conflict)

# Get/set wallet budget (smallest currency unit)
bob wallet budget get \x3Cagent-id> --wallet-id \x3Cid>
bob wallet budget set \x3Cagent-id> --wallet-id \x3Cid> --amount \x3Ccents>

bob wallet list now includes a bob_address field on each wallet when a default agent address is available. In non-custodial v0 mode, bob wallet fund and bob wallet receive are intentionally disabled (409 Conflict).

Returns data.instructions with the payable invoice, address, or account details.

One-shot send (auto-quote + execute)

bob send \x3Cagent-id> \x3Cdestination> --amount \x3Cn> [--currency BTC]

Destination is auto-detected:

• \x3Cagent-uuid> → same-operator internal transfer
• [email protected] → routes as bob_address (BTC by default)
• lnbc... → Lightning invoice (BTC)
• bc1.../bcrt1.../tb1... → on-chain BTC address

Quotes then executes in one step. Returns intent_id, payment_id, and quote_summary. On failure, next_actions includes exact recovery commands.

CLI config introspection

# Show active api_url, platform, config file path and source (env/config/default)
bob config show

# Update a single config value without re-init
bob config set api-url \x3Curl>
bob config set platform \x3Cgeneric|openclaw|claude>

Record a transaction (spend from your wallet)

bob tx record \x3Cagent-id> --amount \x3Ccents> --currency BTC

Transfer money to another agent

bob tx transfer \x3Cfrom-agent-id> --to-agent-id \x3Cto-agent-id> --amount \x3Ccents> --currency BTC

Create an outbound payment (legacy USD rails: ACH, wire, or book)

# ACH or wire — requires a saved counterparty
bob payments create \x3Cagent-id> --amount \x3Ccents> --rail ach --counterparty-id \x3Cid>

# Book transfer — instant, between internal accounts
bob payments create \x3Cagent-id> --amount \x3Ccents> --rail book --to-account-id \x3Cid>

Check payment status

bob payments get \x3Cagent-id> \x3Cpayment-id>

If status is pending or clearing, next_actions will suggest re-checking.

Manage counterparties (saved bank accounts)

# Create
bob payments counterparties create \x3Cagent-id> \
  --name "Vendor Inc" \
  --routing-number 021000021 \
  --account-number 123456789 \
  --account-type checking

# List
bob payments counterparties list \x3Cagent-id>

# Delete
bob payments counterparties delete \x3Cagent-id> \x3Ccounterparty-id>

Quote and execute payments (intent workflow)

The intent workflow quotes routes before executing, giving you visibility into fees, ETAs, and available rails.

# Quote routes for a payment (shows ranked options with fees and ETAs)
bob intent quote \x3Cagent-id> --amount \x3Csats> --destination-type raw --destination-ref \x3Clnbc...|bc1...>

# Execute a quoted intent (uses best quote by default)
bob intent execute \x3Cagent-id> \x3Cintent-id> [--quote-id \x3Cid>]

# Check intent status and route details
bob intent get \x3Cagent-id> \x3Cintent-id>

# List recent intents
bob intent list \x3Cagent-id>

Non-custodial proof submission

For raw BTC payment intents, submit proof of payment to verify settlement:

# Bind Lightning node ownership first (one-time per agent/rail)
bob intent node-bind-challenge \x3Cagent-id> [--wallet-id \x3Cwallet-id>]
bob intent node-bind-verify \x3Cagent-id> --challenge-id \x3Cchallenge-id> --signature \x3Csignature>

# Create ownership challenge bound to proof context (required when attestation is enforced)
bob intent proof-challenge \x3Cagent-id> \x3Cintent-id> --txid \x3Ctxid>
bob intent proof-challenge \x3Cagent-id> \x3Cintent-id> --payment-hash \x3Chash>

# On-chain transaction proof
bob intent submit-proof \x3Cagent-id> \x3Cintent-id> --txid \x3Ctxid>

# Lightning payment hash proof
bob intent submit-proof \x3Cagent-id> \x3Cintent-id> --payment-hash \x3Chash>

# Lightning preimage proof (strongest verification)
bob intent submit-proof \x3Cagent-id> \x3Cintent-id> --preimage \x3Chex> --proof-ref \x3Cpayment-hash>

# With optional BOLT11 invoice for amount verification
bob intent submit-proof \x3Cagent-id> \x3Cintent-id> --preimage \x3Chex> --proof-ref \x3Cpayment-hash> --invoice \x3Clnbc...>

# Ownership-attested submission
bob intent submit-proof \x3Cagent-id> \x3Cintent-id> --txid \x3Ctxid> \
  --ownership-challenge-id \x3Cchallenge-id> \
  --ownership-signature \x3Csignature>

# Historical proof import for credit building
bob agent credit-import \x3Cagent-id> --preimage \x3Chex> --proof-ref \x3Cpayment-hash> --amount \x3Csats> --direction inbound --invoice \x3Clnbc...>

submit-proof requires a valid challenge id/signature pair. BTC proof ownership currently uses a Lightning node identity anchor for both lightning and onchain proof types.

Query history

# Transactions
bob tx list \x3Cagent-id> --status complete --direction outbound --limit 10

# Payments
bob payments list \x3Cagent-id>

# Transfers
bob tx transfers \x3Cagent-id>
bob tx transfers \x3Cagent-id> --with-agent-id \x3Cpeer-agent-id>

# Spend summary
bob spend list \x3Cagent-id>

Marketplace discovery

# Public agent profiles
bob marketplace agents --q "automation"

# Public service gates
bob marketplace gates --category data --min-price 100 --max-price 10000

# Available gate categories
bob marketplace categories

View policies

bob policy list \x3Cagent-id>

Agent credit score and history

# View credit score, tier, and effective policy limits
bob agent credit \x3Cagent-id>

# View credit event timeline
bob agent credit-events \x3Cagent-id> [--limit 50] [--offset 0]

The credit system scores agents from 0-100 across four tiers: trusted (80+, 1.5x limits), growing (65-79, 1.2x limits), building (45-64, 1.0x limits), and watch (0-44, 0.6x limits). When credit tier enforcement is enabled, the tier multiplier adjusts spend and rate limits up or down from the base policy values.

Agent routing profile (autonomous rail preference)

# Inspect current weighting and preferred rail order
bob agent routing-profile \x3Cagent-id>

# Update balanced-scoring weights + preferred rails
bob agent routing-profile set \x3Cagent-id> \
  --cost-weight 0.6 \
  --eta-weight 0.4 \
  --reliability-weight 0.2 \
  --liquidity-weight 0.1 \
  --preferred-usd book,ach,wire \
  --preferred-btc lightning,onchain

Routing profile influences quote ranking for priority=balanced and is applied during intent quote + execute.

Agent webhooks and event stream

# Create/list/get/update/delete webhooks scoped to one agent
bob agent webhooks create \x3Cagent-id> --url https://example.com/hook --events payment_intent.complete,payment.failed
bob agent webhooks list \x3Cagent-id>
bob agent webhooks get \x3Cagent-id> \x3Cwebhook-id>
bob agent webhooks update \x3Cagent-id> \x3Cwebhook-id> --active true
bob agent webhooks delete \x3Cagent-id> \x3Cwebhook-id>

# Pull recent agent events (paginated)
bob agent events \x3Cagent-id> --limit 30 --offset 0

Agent-scoped webhooks/events include payment intent lifecycle events (quoted, executing, submitted, complete, failed) so agents can react asynchronously without polling every endpoint.

Operator funding

bob operator fund --agent-id \x3Cid> --amount \x3Ccents> [--currency BTC] [--wallet-id \x3Cid>]

# Batch fund many agents
bob operator fund batch --items-file funding-batch.json
bob operator fund batch --agent-id \x3Cid1> --agent-id \x3Cid2> --amount \x3Ccents> [--currency BTC]

In non-custodial v0 mode these commands are intentionally disabled (409 Conflict). Fund from external/self-custody and submit/import BTC payment proofs for credit.

Operator credit controls

# View current operator credit posture
bob operator credit summary

# Force snapshot recompute
bob operator credit refresh

# Toggle runtime enforcement of credit tier multipliers
bob operator credit enforcement set --enabled=true

Operator payment addresses

# Create and inspect address aliases
bob address create --handle ops
bob address list

# Bind destination endpoints
bob address add-endpoint \x3Caddress-id> --currency BTC --rail lightning --destination-type raw --destination-ref \x3Clnbc...>

# Enable/disable a bound endpoint
bob address set-endpoint-status \x3Caddress-id> \x3Cendpoint-id> --status disabled

# Resolve live routing capabilities
bob address resolve --address [email protected] --currency BTC

Sub-agent management (create agents under your operator)

You have an operator identity (BOB_OPERATOR_API_KEY) that lets you create and manage sub-agents. Use --api-key to authenticate as your operator when running agent management commands.

# Create a sub-agent under your operator
bob agent create --api-key "$BOB_OPERATOR_API_KEY" \
  --name "my-worker" \
  --operator-id "$BOB_OPERATOR_ID" \
  --budget 50000 \
  --currency BTC

# List agents under your operator
bob agent list --api-key "$BOB_OPERATOR_API_KEY"

# Rotate a sub-agent's API key
bob agent rotate-key \x3Csub-agent-id> --api-key "$BOB_OPERATOR_API_KEY"

The created sub-agent gets its own API key, wallets, and policies. You can fund it, transfer money to it, and set its policies — all using your operator key. The sub-agent's API key is returned in the response.

Operator BTC settlement and reconciliation

# Settle pending BTC receives, expire stale requests, and discover on-chain fees
bob operator btc sweep

# Compare platform BTC ledger totals against LND gateway balances
bob operator btc reconcile

BTC rails are regtest/LND-backed in this environment. Synthetic BTC stub mode is disabled.

Service gates (pay-to-access)

# Create a priced gate (agent must have a payment address)
bob gate create \x3Cagent-id> --name "premium-api" --price 1000 --currency BTC

# List active gates
bob gate list \x3Cagent-id>

# Get gate details
bob gate get \x3Cagent-id> \x3Cgate-id>

# Disable/re-enable a gate
bob gate update \x3Cagent-id> \x3Cgate-id> --status disabled

# Unlock a gate (caller presents a completed payment intent targeting the gate owner)
bob gate unlock \x3Cowner-agent-id> \x3Cgate-id> --intent-id \x3Cpayment-intent-id>

# View unlock history
bob gate unlocks \x3Cagent-id> \x3Cgate-id>

# List gates this agent has unlocked as a caller (outbound gate spend)
bob gate my-unlocks \x3Cagent-id>

# Discover another agent's active gates (any authenticated caller)
bob gate discover \x3Cagent-id>

Output format

Every command returns JSON with this structure:

{
  "ok": true,
  "command": "bob tx record",
  "data": { ... },
  "next_actions": [
    {
      "command": "bob tx list \x3Cagent-id>",
      "description": "View transaction history"
    }
  ]
}

Always check ok before using data. When ok is false, data.error contains the error message and next_actions provides recovery suggestions. Use next_actions to discover what to do next.

Error recovery

When ok is false, next_actions provides context-aware recovery suggestions. Key patterns:

1. Kill switch active: STOP all transactions immediately. Run bob policy list \x3Cagent-id> to confirm.
2. Spend/rate limit exceeded: Check bob spend list \x3Cagent-id> to see current usage vs limits.
3. Insufficient balance: Check bob wallet list \x3Cagent-id> to see available funds.
4. 403 Forbidden: Check bob auth me to verify your identity and role.

Important rules

1. Amounts are always in the smallest currency unit: cents for USD, satoshis for BTC.
2. Policies set by your operator constrain your spending. If a transaction is denied, data.error explains why. Do not retry denied transactions without changing the parameters.
3. Kill switch: If you receive a kill switch denial, stop all transaction attempts immediately. The operator has frozen your spending.
4. Settlement times: Book payments are instant. ACH takes 1-3 business days. Wire settles same day.
5. next_actions: Every response includes suggested follow-up commands. Use them to discover what to do next.