Before you start

Check that you have the latest CLI and skill file. Stale versions cause command errors.

CODEBLOCK0

If bob is not installed or bob update fails, reinstall:
CODEBLOCK1

If this skill file looks like HTML or is missing content, reinstall it:
CODEBLOCK2

Setup checklist

Your agent is fully connected when ALL of these pass:

CODEBLOCK3

If any step fails, run bob init --code <claim-code> --name <name> to complete setup. Do NOT call the REST API directly unless you cannot run the CLI binary — the API path skips wallet and passport creation.

If the agent will spend autonomously, add this treasury check before treating setup as complete:

CODEBLOCK4

For spending-enabled agents, treasury is the default path. The agent keeps its own EVM wallet, and BOB provisions a separate 2-of-2 Safe treasury account plus policy for governed spending.

Core concepts

BOB (beta) is a non-custodial payment proof and trust layer. Agents submit cryptographic proofs of on-chain payments they made externally. Each proof builds credit history and raises their BOB Score, a 0–1000 reputation score for long-term financial trustworthiness.

BOB also supports a non-custodial 2-of-2 treasury flow on Base for agents using a Safe controlled by:

• - the agent's EVM wallet
• the BOB treasury signer

In this model, the agent prepares and signs a Safe transaction locally, then submits it for operator review and BOB co-signing. BOB never takes custody of the agent's funds.

Treat this as the standard setup for any agent that can move money in production:

• - agent EVM wallet = identity and first signer
• treasury Safe = governed spending account
• treasury policy = spending controls and review rules

• - Agent: An AI agent with its own identity and BOB Score
• Payment Proof: Cryptographic evidence of an on-chain transaction (BTC, ETH, Base, or SOL txid/hash)
• BOB Score: 0–1000 reputation score derived from proof history, wallet binding, and social signals
• Credit Event: A scored action that changed the agent's BOB Score
• Wallet Binding: Proof of ownership over an external EVM wallet

First connection

When connecting via claim code, introduce yourself — use the name your operator gave you:

CODEBLOCK5

Your name seeds your public handle (e.g. "Alice" → @alice). If the handle is taken, a short number is appended automatically (e.g. @alice-42). The response includes your agent_id, api_key, and bob_handle.

Already initialized without a name? Update it anytime:

CODEBLOCK6

Quick start

CODEBLOCK7

INLINECODE8 attempts to create a passport, generate multi-chain wallet keys (EVM, BTC, SOL), and bind them to the agent's identity. Verify with bob wallet list and bob agent passport-get $BOB_AGENT_ID if needed.

For agents that will spend, bob init handles Safe deployment automatically when the operator selected a spending custody tier (operatorapproved or policycontrolled) during claim code creation. After init:

1. 1. Confirm the agent has a bound EVM wallet.
2. Verify treasury is provisioned: bob treasury status (the Safe and a default policy are created during init for spending tiers).
3. Only fund the treasury Safe after those checks pass.
4. The operator can adjust policies from the dashboard at any time.

The production API URL is https://api.bankofbots.ai/api/v1. Use bob config set api-url <url> to change it if needed.

After Init Checklist

1. 1. Passport created (automatic)
2. Wallets generated and bound (automatic)
3. Treasury Safe deployed (automatic for operatorapproved and policycontrolled tiers)
4. Default policy activated (automatic — operator can customize from dashboard)
5. Import payment proofs to build score
6. Check your score: INLINECODE15
7. Request a loan once eligible

If the operator chose view_only custody, no Safe is deployed. The agent can still build credit via proofs.

Check your score

CODEBLOCK8

Check your identity

CODEBLOCK9

Agent management

CODEBLOCK10

Wallet binding

INLINECODE16 attempts to generate and bind EVM, BTC, and SOL wallets. Verify with bob wallet list. If wallets need rebinding, use the one-shot auto-bind:

CODEBLOCK11

Agent wallets

CODEBLOCK12

INLINECODE18 reads the recent on-chain balance snapshot from the BOB API. This is the best way to inspect current registered wallet balances from the CLI because the server keeps those snapshots warm in the background.

Treasury (2-of-2 Safe)

Use treasury commands for any spending-enabled agent. Treasury is the default governed spending path once a Base Safe treasury account and active policy are provisioned.

If the agent was initialized with a spending custody tier, the Safe is deployed automatically during bob init. For agents that initialized without treasury, deploy it manually:

CODEBLOCK13

This deploys a 2-of-2 Gnosis Safe on Base (agent as owner #1, BOB as owner #2) and creates a default policy based on the agent's custody tier.

CODEBLOCK14

Recommended flow:

1. 1. bob treasury status to confirm there is an active treasury account and policy.
2. INLINECODE21 for the standard one-shot path.
3. Use prepare + sign + submit separately when another tool needs the intermediate Safe hash or signature.
4. INLINECODE25 to track whether the request is pending operator review, confirmed, or failed.

Treasury commands assume:

• - Base chain only (0x2105)
• USDC transfer flow only
• the local CLI keyring contains the agent's EVM private key from INLINECODE27
• operator approval may still be required before execution

Important:

• - The agent still keeps its own wallet.
• Treasury adds a separate governed Safe for controlled funds.
• If an agent is allowed to spend autonomously, funding should go to the treasury Safe, not the raw agent wallet.

LLM Spend Tracking

Track LLM costs, set budgets, and sync usage from the OpenClaw gateway.

CODEBLOCK15

• - track converts --cost-usd to micro-dollars (multiply by 1e6) before posting.
• INLINECODE30 defaults to the last 30 days when --since is omitted.
• INLINECODE32 requires --window (daily/weekly/monthly) and --limit-usd.
• INLINECODE35 calls the OpenClaw gateway sessions.usage RPC, transforms usage into cost events, and posts them to BOB. It tracks the last sync time locally to avoid duplicates.

Import payment proofs

Wallet binding is required before importing proofs. bob init attempts to bind auto-generated wallets. Verify with bob wallet list. If wallets need rebinding, run bob binding auto.

Import historical on-chain proofs

For outbound proofs, pass --sender-address (required for EVM proofs) so BOB can verify the on-chain sender matches your bound wallet. For inbound proofs, pass --recipient-address instead. When both the sender and recipient submit the same tx, confidence is boosted from Medium to Strong (see "Dual-sided proof submission" below).

CODEBLOCK16

Dual-sided proof submission

Both the sender and recipient of a transaction can independently submit a proof for the same on-chain tx. Each side earns credit:

• - Outbound (--direction outbound, default): You sent the payment. Pass --sender-address for EVM proofs so the on-chain sender can be verified against your bound wallet.
• Inbound (--direction inbound): You received the payment. Pass --recipient-address for EVM proofs.

When both counterparties submit the same transaction, confidence is automatically upgraded from medium to strong.

Import x402 payment receipts

CODEBLOCK17

Import MPP receipt (Tempo, Lightning, Stripe, Card)

CODEBLOCK18

Supported methods: tempo (stablecoin on Base), lightning, stripe, card.

Messaging and inbox

Operator command queue

Operators send commands to agents via the dashboard. Use bob inbox check to process pending commands.

CODEBLOCK19

Currently supported command types: wallet.provision. Future: transfer.request, loan.accept, kill_switch, key.rotate.

Heartbeat

When running during a heartbeat or periodic check-in, execute bob inbox check to process any pending operator commands. This covers wallet provisioning, fund transfers, and future command types.

• - If commands are pending, process them and report what was done.
• If no commands are pending, continue with other tasks or reply HEARTBEAT_OK.

For lower-latency command processing, operators can create an OpenClaw cron job:
CODEBLOCK20

Webhooks and inbox

CODEBLOCK21

Loans

Agents can borrow USDC from Bank of Bots based on their BOB Score. All loan operations are in-platform API calls — they are normal agent actions.

How to borrow

Units: USDC amounts are in atomic units (6 decimals). 1 USDC = 1000000. For example, $5.00 = 5000000.

CODEBLOCK22

Current lending policy constraints (control plane):

• - Maximum 5 active loans per agent.
• New borrowing is blocked for 90 days after a default.
• Operator facility status/cap can block new requests (facility suspended/terminated or amount above cap).
• Kill switch freeze blocks loan write actions until lifted.

Repayment flow: bob loan repay --amount <usdc> automatically signs and broadcasts a USDC transfer from your wallet to the lender's Safe on Base (chain ID 8453), then records the repayment. The CLI checks loan status first, so pending_funding and other non-active states fail fast with guidance instead of suggesting unnecessary gas work. You need ETH on Base in the borrower wallet for gas. If this agent wallet is new but another local BOB wallet still has Base ETH, inspect bob wallet gas-candidates, then rerun with --fund-gas-from-local --gas-funder-agent-id <agent-id> and the CLI will top up the borrower wallet from that explicitly selected local wallet before retrying. Check bob loan status for the current total owed. If you already sent USDC manually, pass --tx <hash> instead to just record it without sending again.

Loan management

CODEBLOCK23

Loan lifecycle:

1. 1. Agent requests loan (bob loan request) → status: INLINECODE69
2. Admin funds request → status: INLINECODE70
3. Agent signs terms (bob loan accept-terms) → status: INLINECODE72
4. Borrower repays (bob loan repay) → status: INLINECODE74

Diagnostics

CODEBLOCK24

Runs connectivity and configuration checks (API reachability, valid API key, agent existence). Use this when troubleshooting auth or network issues.

Error recovery

Passport (W3C Verifiable Credential)

CODEBLOCK25

API keys

CODEBLOCK26

Output format

CODEBLOCK27

Important rules

1. 1. Amounts are native atomic units: satoshis for BTC, wei for ETH/Base, lamports for SOL.
2. Proofs are non-custodial. BOB never holds your funds.
3. Historical on-chain proof imports and x402 receipt imports are the current public proof rails.
4. For outbound EVM proofs, --sender-address is required and must match the on-chain sender -- mismatches fail with sender_address_mismatch.