Quickstart

This quickstart runs a single agentic transaction end-to-end on Base Sepolia using x402, in the recommended brickken-relayed mode (Brickken signs and broadcasts).

1. Install and authenticate

If you have not already, install the CLI and set up a private key:

npm install -g brickken-cli
export BRICKKEN_PRIVATE_KEY=0x...

2. Set your environment

export BRICKKEN_ENV="sandbox"
export CHAIN="84532"                 # Base Sepolia
export BRICKKEN_RPC_URL="https://sepolia.base.org"

Fund the wallet behind BRICKKEN_PRIVATE_KEY with a small amount of Base Sepolia Circle USDC (0x036CbD53842c5426634e7929541eC2318f3dCF7e) so it can pay the x402 send fee. In brickken-relayed mode Brickken’s relayer covers native gas.

3. Sanity checks

brickken --version
test -n "$BRICKKEN_PRIVATE_KEY" && echo "private key ok" || echo "private key missing"
test -n "$BRICKKEN_RPC_URL"     && echo "rpc ok"          || echo "rpc missing"
command -v jq

4. Deploy a token end-to-end

Preparing is free; the --execute flag also sends and pays the x402 charge in one step. With --execution-mode brickken-relayed you omit --signer-address and --agent-wallet — Brickken’s relayer signs, pays gas, and becomes the token owner. The --json flag makes the output machine-readable so you can pipe it into jq.

brickken create-token \
  --chain "$CHAIN" \
  --execution-mode brickken-relayed \
  --name "Quickstart Token" \
  --symbol QST \
  --premint 1000 \
  --decimals 18 \
  --execute \
  --json | tee create-token-output.json

When create-token --execute succeeds, the CLI waits for the deployment receipt and adds tokenAddress to the JSON output. Capture it for follow-up commands:

export TOKEN_ADDRESS="$(jq -r '.tokenAddress' create-token-output.json)"
echo "$TOKEN_ADDRESS"

Echo critical variables such as TOKEN_ADDRESS and AGENT_UUID before reusing them. If a command seems to “drop” fields, the usual cause is shell expansion or quoting — not --json. Quote every value that can contain spaces, and prefer --file for nested JSON.

Getting Started

Commands

Guides

1. Install and authenticate

2. Set your environment

3. Sanity checks

4. Deploy a token end-to-end

What’s next

Agent commands

Token economics

End-to-end guide

​1. Install and authenticate

​2. Set your environment

​3. Sanity checks

​4. Deploy a token end-to-end

​What’s next

Agent commands

Token economics

End-to-end guide

1. Install and authenticate

2. Set your environment

3. Sanity checks

4. Deploy a token end-to-end

What’s next