Install
Thecaw CLI is a standalone binary. The CLI’s environment default is prod.
caw binary to ~/.cobo-agentic-wallet/bin/caw. Add it to your PATH:
Onboard and pair with the wallet owner
Run the interactive onboarding wizard. You will need an invitation code from the wallet owner.status becomes active.
Once the wallet is active, generate an 8-digit pairing token for the wallet owner:
Cobo Agentic Wallet App, then enter the token to complete ownership pairing. Check pairing status with:
Claim testnet tokens
The examples below run on Sepolia testnet and use nativeSETH. Request it from the built-in faucet:
caw wallet balance. Continue once the tokens arrive.
Get credentials
api_url, api_key, and wallet_uuid values from the output.
First hello-world flow
Before executing blockchain actions, submit a pact to request delegated access from the wallet owner. The owner approves the pact in the Cobo Agentic Wallet app.- Submit a pact requesting transfer permissions
- Once active, get the pact ID and check its status:
Required flags are
--intent, --execution-plan, --policies, and --completion-conditions.Explore your wallet
Transfer tokens
code, reason, details, and suggestion.
Check audit logs
Audit logs are accessible via the Python SDK. See Audit and Activity Logs for the full query interface.Go further
Once the CLI path works, move to an SDK if you want to keep the same flow inside application code:- Python SDK — same flow, async client, better for custom logic and long-running runtimes.
- TypeScript SDK — same flow, typed Node.js client for backend services and agent runtimes.
- Custom Skill — good when your runtime already supports skill files and you want the lightest path.
Python SDK
Move the same flow into Python application code.
TypeScript SDK
Move the same flow into Node.js or TypeScript application code.
CLI Reference
Full command surface, options, and error handling.