Skip to main content
The REST API, the CLI, the MCP server, and the Skill all talk to the same backend at api.brickken.com. They differ in who is driving and which credential they carry.

​
Start from what you already have

​
The four surfaces

REST API

Plain HTTP. Everything the platform can do. API key for the Dapp API, x402 or API key for agentic methods.

MCP server

Hosted at https://mcp.brickken.com/mcp. The only client that reaches the full Dapp API with just an API key.

CLI

brickken-cli on npm. Agentic and RAMS workflows from your terminal. Does not reach the Dapp API.

Skill

Brickken knowledge for AI coding agents, with or without the CLI installed.

​
What each surface can reach

The CLI cannot call the legacy Dapp API. Two independent reasons: it has no commands or method mappers for the Dapp methods, and it attaches x-api-key only to RAMS reads and typed-data fetches. brickken tx prepare --method newTokenization forwards the method name, but the backend answers API key is required for this method.For Dapp API work, use MCP if an agent is driving, or plain HTTP if your own code is.

​
Same backend, same rules

Whichever surface you pick, the mechanics are identical: writes are prepared into unsigned transactions, signed, then sent; preparing an agentic operation is free and only the send costs anything; and your private key never leaves your machine. The surface changes the ergonomics, not the semantics — you can prepare with the CLI and send with curl.

Authentication

The credential matrix in full.

Quickstart

A first call on each of the four surfaces.