> ## Documentation Index
> Fetch the complete documentation index at: https://docs.brickken.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Set up your environment and run your first end-to-end Brickken CLI transaction.

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](/cli/installation) and set up a private key:

```bash theme={null}
npm install -g brickken-cli
export BRICKKEN_PRIVATE_KEY=0x...
```

## 2. Set your environment

```bash theme={null}
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

```bash theme={null}
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`.

```bash theme={null}
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:

```bash theme={null}
export TOKEN_ADDRESS="$(jq -r '.tokenAddress' create-token-output.json)"
echo "$TOKEN_ADDRESS"
```

<Tip>
  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`](/cli/commands/tx) for nested JSON.
</Tip>

## What's next

<CardGroup>
  <Card title="Agent commands" icon="robot" href="/cli/commands/agent">
    Register an ERC-8004 agent and manage its reputation.
  </Card>

  <Card title="Token economics" icon="coins" href="/cli/commands/token-economics">
    Mint, burn, transfer, and approve agentic tokens.
  </Card>

  <Card title="End-to-end guide" icon="diagram-project" href="/cli/guides/agent-and-token-workflow">
    A full agent registration and token lifecycle walkthrough.
  </Card>
</CardGroup>