Skip to main content

​
Overview

The Brickken Skill is an AI-agent skill built on the open Agent Skills format (SKILL.md). It works with any agent that supports the standard — including Claude Code, OpenAI Codex, Gemini CLI, Cursor, and GitHub Copilot — and helps agents choose and use the right Brickken surface:
  • Dapp API when you have a Brickken API key.
  • Agentic API when you do not have an API key and want to use private-key based x402 flows.
  • MCP when your agent can connect to the hosted Brickken MCP server.
  • CLI when local signing and terminal execution are the best fit.
Use the skill when an agent needs to inspect Brickken endpoints, prepare request bodies, understand expected responses, or decide whether a task should go through the API, CLI, or MCP.

Download Skill

Download the standalone Brickken skill archive.

CLI package

Install the public brickken-cli package from npm.

GitHub repository

View the public CLI and bundled skill source.

MCP

Open the official Brickken MCP page.

​
Install Only the Skill

Use this path when you want the Brickken Skill without installing the CLI globally. Download the archive and unzip it into your agent’s skills directory:
Verify the installation:
Most agents also discover project-level skills from a directory inside the repository (for example .claude/skills, .cursor/skills, .gemini/skills, or .github/skills). Unzip the archive there instead to share the skill with your team through version control. Start a new agent session after installing the skill so the agent reloads its available skills.

​
Install with the CLI

If you already use the Brickken CLI, install the bundled skill with:
By default the installer targets ~/.codex/skills. Pass --path to install into any other agent’s skills directory:
To install without a global CLI install, run the installer through npx:
Inspect where the npm package bundles the skill:

​
Configure Credentials

​
Dapp API

Use the Dapp API when you have a Brickken API key.
The skill guides the agent toward API-key authenticated endpoints, request bodies, response examples, and transaction preparation or send flows.

​
Agentic API

Use the Agentic API when you want x402-paid flows without a Brickken API key. It runs on Base mainnet (8453) and Base Sepolia (84532).
Preparing an operation is free; the x402 USDC payment is charged only on send. In the recommended brickken-relayed mode the private key signs only the x402 payment, and Brickken’s relayer signs, pays native gas, and broadcasts the operation — so you do not need to sign the blockchain transaction or hold native gas. In client-signed mode the key also signs the prepared transaction locally. Never send a private key to the Brickken API.
Do not paste production API keys or private keys into shared chats, tickets, terminals, or logs. Use your agent client’s secret store or local environment variables.

​
Example Prompts