CLI

The Brickken CLI is the public terminal client for the Dapp API, KYC onboarding, the Sandbox/Forge BKN faucet, and the Agentic API. It supports Dapp API transaction methods through brickken tx, Dapp API JSON endpoints through brickken dapp, ERC-8004 on Base, and ERC-8226 RAMS mandates on Ethereum Sepolia. Client-controlled requests use an API key when configured and otherwise use x402 where supported; relayed sends always use x402.

npm package

Install brickken-cli from npm.

GitHub repository

View the public source repository.

Install

npm install -g brickken-cli
brickken --version
brickken --help

You can also run it without a global install:

npx brickken-cli --help

Authentication

Dapp API requests and KYC require an API key. Client-controlled Agentic API and RAMS requests use the key when configured and otherwise fall back to x402. Agent getters and the BKN faucet use an API key when configured and support x402 where documented.

export BRICKKEN_API_KEY=...
export BRICKKEN_PRIVATE_KEY=0x...

BKN_API_KEY and BKN_PRIVATE_KEY are accepted aliases. The private key signs the x402 payment, client-signed transactions, and requested RAMS typed data locally.

With BRICKKEN_API_KEY configured, the CLI can prepare and send Dapp API transaction methods and call Dapp API JSON endpoints. Multipart file uploads such as /patch-token-docs remain REST-only.

Never paste production private keys into shared terminals, tickets, or chat logs. Prefer environment variables or an .env file that is not committed.

Environments

Environment	Base URL
`sandbox` (default)	`https://api.sandbox.brickken.com`
`production`	`https://api.brickken.com`

brickken --env sandbox --help
brickken --env production --help

An internal forge environment exists for Brickken pre-release QA — contact tech@brickken.com for its base URL. Override the API base URL directly when needed:

brickken --base-url https://api.sandbox.brickken.com --help

Network and RPC

Pass the target operation chain with --chain. Decimal and hex values are accepted. The Agentic API runs on Base, with Base Sepolia for tests.

Network	Decimal	Hex
Base mainnet	`8453`	`0x2105`
Base Sepolia	`84532`	`0x14a34`
Ethereum Sepolia (RAMS)	`11155111`	`0xaa36a7`

Some commands, especially create-token --execute, wait for a deployment receipt to recover tokenAddress. Set an RPC URL for that lookup:

export BRICKKEN_RPC_URL="https://sepolia.base.org"   # Base Sepolia

BKN_RPC_URL is accepted as an alias, or pass --rpc-url.

Command Model

High-level commands are prepare-only by default. With an API key, client-controlled requests use API-key authentication; without one, eligible Agentic API and RAMS requests use x402. Relayed preparation is free and relayed sends use x402. Add --execute to also send in one step. Add --json for machine-readable output. The recommended path is brickken-relayed mode: pass --execution-mode brickken-relayed and omit --signer-address — Brickken’s relayer signs and broadcasts. The default is client-signed, where you provide --signer-address and the CLI signs the prepared transaction locally.

# Prepare only (free in relayed mode), relayed execution
brickken create-token \
  --chain 84532 \
  --execution-mode brickken-relayed \
  --name "Research Agent Token" \
  --symbol RAGT

# Prepare + pay the send via x402, relayed mode
brickken create-token \
  --chain 84532 \
  --execution-mode brickken-relayed \
  --name "Research Agent Token" \
  --symbol RAGT \
  --execute \
  --json

Commands

Command	Backend method	Purpose
`brickken agent register`	`agentRegister`	Register an ERC-8004 agent identity.
`brickken agent set-uri`	`agentSetURI`	Update an agent URI/profile.
`brickken agent set-metadata`	`agentSetMetadata`	Write an agent metadata key/value.
`brickken agent set-wallet`	`agentSetWallet`	Update the agent operational wallet.
`brickken agent transfer-ownership`	`agentTransferOwnership`	Transfer the ERC-8004 identity to a new owner.
`brickken agent feedback give`	`agentGiveFeedback`	Submit reputation feedback.
`brickken agent feedback revoke`	`agentRevokeFeedback`	Revoke feedback.
`brickken agent feedback respond`	`agentAppendFeedbackResponse`	Respond to feedback.
`brickken create-token`	`agentCreateToken`	Deploy an agent-owned ERC-20 token.
`brickken mint`	`agentMintToken`	Mint an agent-owned token.
`brickken burn`	`agentBurnToken`	Burn an agent-owned token.
`brickken transfer`	`agentTransferToken`	Transfer an agent-owned token.
`brickken transfer-from`	`agentTransferFromToken`	Transfer through allowance.
`brickken approve`	`agentApproveToken`	Approve an allowance.
`brickken dapp get`	`GET <path>`	Call a Dapp API read endpoint with an API key.
`brickken dapp request`	`POST/PATCH <path>`	Call a Dapp API JSON endpoint with an API key.
`brickken rams <command>`	`rams` / `GET /rams/`	Manage ERC-8226 mandates, compliance, execution, reads, and signatures.
`brickken tx prepare --method <method>`	any supported method	Prepare a Dapp or Agentic API transaction; sends an API key when configured.
`brickken tx sign`	local only	Sign prepared transaction JSON locally.
`brickken tx send`	`POST /send-transactions`	Submit signed transactions.
`brickken tx status`	`GET /get-transaction-status`	Poll transaction status.
`brickken skill path`	local only	Print the bundled Brickken AI-agent skill path.
`brickken skill install`	local only	Install the bundled skill into an agent skills directory.

See the complete brickken rams command reference and end-to-end mandate workflow. See the Dapp API command reference for authenticated reads and JSON requests, and the raw transaction reference for tokenization and STO methods.

AI Agent Skill

The npm package includes a Brickken skill at skills/brickken, built on the open Agent Skills format and compatible with any agent that supports it — Claude Code, OpenAI Codex, Gemini CLI, Cursor, GitHub Copilot, and more. Use it when an AI agent needs to choose between the Dapp API, Agentic API, CLI, or MCP. For standalone installation without a global CLI install, see the Skill documentation. After installing brickken-cli, install the skill into the default skills directory (~/.codex/skills):

brickken skill install

Or pass --path to target your agent’s skills directory (for example ~/.claude/skills for Claude Code, ~/.gemini/skills for Gemini CLI, ~/.cursor/skills for Cursor):

brickken skill install --path ~/.claude/skills --force

To inspect where the bundled skill lives in the installed package:

brickken skill path

Without a global install:

npx brickken-cli skill install --path ~/.claude/skills --force

Agent Example

export CHAIN="84532"   # Base Sepolia

brickken agent register \
  --chain "$CHAIN" \
  --execution-mode brickken-relayed \
  --name "Research Agent" \
  --description "On-chain AI research agent" \
  --image https://example.com/agent.png \
  --service-name A2A \
  --service-endpoint https://agent.example/.well-known/agent-card.json \
  --ai-model-provider OpenAI \
  --ai-model-name "Research Model" \
  --x402-support true \
  --execute \
  --json

File Input

Use --file for nested JSON/YAML payloads, long metadata, or automation:

brickken tx prepare \
  --method agentSetMetadata \
  --file metadata.json \
  --execute \
  --json

Relayed preparation is free and the full operation is x402-priced at send. Client-controlled modes split the operation charge between prepare and send. Fund the wallet behind BRICKKEN_PRIVATE_KEY with enough USDC on the x402 payment chain (e.g. Circle USDC on Base Sepolia). In brickken-relayed mode Brickken’s relayer pays native gas; in client-signed mode you also need native gas on the operation chain.

Getting Started

Commands

Guides

npm package

GitHub repository

Install

Authentication

Environments

Network and RPC

Command Model

Commands

AI Agent Skill

Agent Example

File Input

npm package

GitHub repository

​Install

​Authentication

​Environments

​Network and RPC

​Command Model

​Commands

​AI Agent Skill

​Agent Example

​File Input

Install

Authentication

Environments

Network and RPC

Command Model

Commands

AI Agent Skill

Agent Example

File Input