Skip to Content
CLI Reference

CLI Reference

Command reference for @human.tech/waap-cli. For browser dApps, see the SDK Reference.

Run waap-cli commands --json for the authoritative schema of your installed version.

Authentication

# Sign up (creates account + logs in)
waap-cli signup --email you@example.com --password 'S3cur3Pass!'
 
# Log in to existing account
waap-cli login --email you@example.com --password 'S3cur3Pass!'
 
# Log out
waap-cli logout

Get Wallet Address

whoami is chain-independent. It reports every address on the account in one call, whichever chain you are working on.

waap-cli whoami --json
# → evmWalletAddress:    0x...
# → suiWalletAddress:    0x...
# → solanaWalletAddress: ...

The EIP-1193 route returns the EVM address only:

waap-cli request eth_accounts

Sign a Message

waap-cli sign-message --message "Hello WaaP"

Sign Typed Data (EIP-712)

waap-cli sign-typed-data --data '{
  "types": { "EIP712Domain": [...], "Mail": [...] },
  "domain": { "name": "Ether Mail", "chainId": 1 },
  "primaryType": "Mail",
  "message": { "contents": "Hello!" }
}'

Send a Transaction

waap-cli send-tx \
  --to 0xRecipient \
  --value 0.01 \
  --chain-id 1 \
  --rpc https://eth.llamarpc.com

Select a Chain

There is no chain to switch. Every signing command takes --chain and requires it, so the chain is a property of the call rather than of the session.

waap-cli send-tx --to 0xRecipient --value 0.01 --chain evm:137

chain set is deprecated and stores nothing. It warns and returns without saving, so a script that relies on it will send on whatever the command’s own --chain says. --chain-id is also deprecated; use --chain.

Policy & 2FA

Agent safety controls. These have no SDK equivalent. A dApp cannot change a user’s policy.

# View policy settings
waap-cli policy get
 
# Set daily spend limit
waap-cli policy set --daily-spend-limit 500
 
# Enable 2FA
waap-cli 2fa enable --email agent@example.com
 
# Check 2FA status
waap-cli 2fa status

Deep Dives

Last updated on
SDK ReferenceEVM Networks