--execute to also send and pay the x402 charge. The recommended brickken-relayed mode (--execution-mode brickken-relayed) lets Brickken’s relayer sign and broadcast; the default client-signed mode signs locally with --signer-address.
Each high-level command maps to a backend agentic method. Field-level semantics for every method are documented under Agentic Methods with x402.
Shared options
Every command accepts these:create-token
Deploy a new agentic ERC-20 token.The examples below use
--signer-address / --agent-wallet for client-signed mode. In brickken-relayed mode you omit both — Brickken’s relayer becomes the token owner. When create-token --execute succeeds, the CLI waits for the deployment receipt and adds tokenAddress to the JSON output; set --rpc-url, BRICKKEN_RPC_URL, or BKN_RPC_URL for the target chain. Do not continue into mint or burn unless tokenAddress is present.mint
Mint additional tokens.--signer-address must be the configured agentWallet.
burn
Burn tokens.--signer-address must be the configured agentWallet.
transfer
Transfer tokens from the signer’s wallet.transfer-from
Transfer tokens through an allowance.--signer-address is the approved spender.