> ## 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.

# Skill

> Brickken AI-agent skill for the Dapp API, Agentic API, CLI, and MCP.

## Overview

The **Brickken Skill** is an AI-agent skill built on the open [Agent Skills](https://agentskills.io) 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.

<CardGroup cols={2}>
  <Card title="Download Skill" icon="download" href="https://raw.githubusercontent.com/fbrickken/docs/main/downloads/brickken-skill.zip">
    Download the standalone Brickken skill archive.
  </Card>

  <Card title="CLI package" icon="box" href="https://www.npmjs.com/package/brickken-cli">
    Install the public `brickken-cli` package from npm.
  </Card>

  <Card title="GitHub repository" icon="github" href="https://github.com/Brickken/brickken-api-cli">
    View the public CLI and bundled skill source.
  </Card>

  <Card title="MCP" icon="plug" href="https://mcp.brickken.com/">
    Open the official Brickken MCP page.
  </Card>
</CardGroup>

## 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:

| Agent                    | Personal skills directory                               |
| ------------------------ | ------------------------------------------------------- |
| Claude Code              | `~/.claude/skills`                                      |
| OpenAI Codex             | `~/.codex/skills`                                       |
| Gemini CLI               | `~/.gemini/skills`                                      |
| Cursor                   | `~/.cursor/skills`                                      |
| GitHub Copilot / VS Code | `~/.copilot/skills`                                     |
| Other agents             | See your agent's documentation for its skills directory |

```bash theme={null}
export SKILLS_DIR=~/.claude/skills   # set to your agent's skills directory

mkdir -p "$SKILLS_DIR"
curl -L https://raw.githubusercontent.com/fbrickken/docs/main/downloads/brickken-skill.zip -o /tmp/brickken-skill.zip
rm -rf "$SKILLS_DIR/brickken"
unzip -o /tmp/brickken-skill.zip -d "$SKILLS_DIR"
```

Verify the installation:

```bash theme={null}
test -f "$SKILLS_DIR/brickken/SKILL.md" && echo "Brickken skill installed"
```

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](/cli/introduction), install the bundled skill with:

```bash theme={null}
npm install -g brickken-cli
brickken skill install
```

By default the installer targets `~/.codex/skills`. Pass `--path` to install into any other agent's skills directory:

```bash theme={null}
brickken skill install --path ~/.claude/skills --force
```

To install without a global CLI install, run the installer through `npx`:

```bash theme={null}
npx brickken-cli skill install --path ~/.claude/skills --force
```

Inspect where the npm package bundles the skill:

```bash theme={null}
brickken skill path
```

## Configure Credentials

### Dapp API

Use the [Dapp API](/api-reference/introduction) when you have a Brickken API key.

```bash theme={null}
export BRICKKEN_API_KEY="YOUR_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](/api-reference/endpoint/agentic-methods-x402) when you want x402-paid flows without a Brickken API key. It runs on Base mainnet (`8453`) and Base Sepolia (`84532`).

```bash theme={null}
export BRICKKEN_PRIVATE_KEY="0xYOUR_PRIVATE_KEY"
export BRICKKEN_RPC_URL="https://sepolia.base.org"   # Base Sepolia
```

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.

<Warning>
  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.
</Warning>

## Example Prompts

```text theme={null}
Use the Brickken skill to prepare a new tokenization with my Dapp API key.
```

```text theme={null}
Use the Brickken skill to register an ERC-8004 agent with the Agentic API and no API key.
```

```text theme={null}
Use the Brickken skill to decide whether this workflow should use the API, CLI, or MCP.
```