brickken-relayed mode, Brickken’s relayer signs and broadcasts the operation; in client-signed mode the CLI signs locally with your private key.
npm package
Install
brickken-cli from npm.GitHub repository
View the public source repository.
Install
Authentication
The CLI is x402-only. It ignoresBRICKKEN_API_KEY and BKN_API_KEY.
BKN_PRIVATE_KEY is accepted as an alias. The private key signs the x402 payment, and — in client-signed mode only — the blockchain transaction. In brickken-relayed mode it signs the x402 payment only.
Environments
| Environment | Base URL |
|---|---|
sandbox (default) | https://api.sandbox.brickken.com |
production | https://api.brickken.com |
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 (legacy) | 11155111 | 0xaa36a7 |
create-token --execute, wait for a deployment receipt to recover tokenAddress. Set an RPC URL for that lookup:
BKN_RPC_URL is accepted as an alias, or pass --rpc-url.
Command Model
High-level commands are prepare-only by default, and preparing is free. Add--execute to also send and pay the x402 charge 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.
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 tx prepare --method <method> | any supported method | Prepare a raw backend method. |
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. |
AI Agent Skill
The npm package includes a Brickken skill atskills/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):
--path to target your agent’s skills directory (for example ~/.claude/skills for Claude Code, ~/.gemini/skills for Gemini CLI, ~/.cursor/skills for Cursor):
Agent Example
File Input
Use--file for nested JSON/YAML payloads, long metadata, or automation:
Preparing is free; only the send is x402-priced. 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.