Skip to main content
This quickstart runs a single agentic transaction end-to-end on Sepolia testnet using x402.

​
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="11155111"                 # Sepolia
export WALLET="0xYourWallet"
export BRICKKEN_RPC_URL="https://ethereum-sepolia-rpc.publicnode.com"
Fund WALLET with a small amount of Sepolia USDC so the wallet can pay x402 fees.

​
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

The --execute flag prepares, signs locally, sends, and pays through x402 in one step. The --json flag makes the output machine-readable so you can pipe it into jq. 
brickken create-token \
  --chain "$CHAIN" \
  --signer-address "$WALLET" \
  --name "Quickstart Token" \
  --symbol QST \
  --agent-wallet "$WALLET" \
  --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.

​
What’s next

Agent commands

Register an ERC-8004 agent and manage its reputation.

Token economics

Mint, burn, transfer, and approve agentic tokens.

End-to-end guide

A full agent registration and token lifecycle walkthrough.