Agent wallet setup

Agent wallet setup

Boon agent mode signs through OWS. Use this for agents that propose and execute approved boons.

Prerequisites

You need:

• Boon CLI available as boon
• OWS Node/native binding installed in the environment
• an OWS wallet with an EVM/Base account
• a policy-scoped ows_key_... API token for live sends
• a small amount of Base USDC in the OWS address

Connect the wallet

boon wallet connect ows --wallet boon-agent

Boon resolves the wallet, records the alias and Base address, and prints the address to fund.

Configure the API token

Set one of:

export BOON_OWS_API_KEY=ows_key_...
# or
export BOON_OWS_API_KEY_FILE=/path/to/ows-token.txt

The token must begin with ows_key_... and have attached policies. Boon intentionally rejects owner passphrases for agent sends because they bypass OWS policy enforcement.

Check readiness

boon wallet current --json
boon doctor --json
boon tip --dry-run github:alice 2 "pr:owner/repo#42: review"

Require chainId: "eip155:8453" from wallet current. In the doctor output, both wallet and wallet-policy must pass. A funded wallet with the wrong chain tag or no matching policy token is not ready. Select or create a correctly tagged Base wallet and mint its agent key through the CLI. Never edit OWS wallet or key JSON to force a check to pass.

Recommended caps

Boon’s default local guardrails are intentionally small:

Setting	Default
maxUsdcPerDay	50
maxUsdcPerTip	10
minSecondsBetweenTips	60
per-handle cooldown	30 days

Keep OWS wallet balances near the amount you are comfortable letting an approved agent policy spend.