Skip to main content
Brickken issues API keys by hand. Submit the form below and it reaches the team directly — no email to send yourself. It asks for everything we need, so the first reply you get is your key rather than a list of follow-up questions.

​
What a key gets you

  • The full Dapp API: tokenization, STOs, security-token operations, and reads — over HTTP or through the MCP server.
  • The Agentic API in client-signed mode, without paying x402 per call.
  • A plan with a separate credit balance for each write method, and higher rate limits on prepare-transactions.
Join the Developer Build Programme. Start with the API Challenge — Hello World to build with your sandbox API key, or take the Agentic Challenge — Hello World to register an ERC-8004 agent and deploy its token with the Brickken CLI and x402.
Sandbox and production keys are separate. See Authentication for what each credential reaches.

​
What Brickken needs from you

The form asks for all of it. If you would rather email tech@brickken.com yourself, include:
  • Your name, company or project, and a reply-to address
  • The email registered on your Brickken account — it can be the same as or different from your reply-to address; sign up for a sandbox account if needed
  • Sandbox (API key requests are not currently available for production)
  • Your target sandbox networks — Sepolia, Polygon Amoy, or Base Sepolia — and the token symbols you plan to issue
  • What you are building, roughly which methods you expect to call, and your expected volume

​
What happens next

A Brickken engineer replies to the address you gave, from tech@brickken.com. Whitelisting the wallet you will use as signerAddress is handled in the same thread, once we know which environment you are on. Going to production? Book an onboarding call so the right plan and limits are in place before you launch.
Never include a private key or seed phrase in this request. Brickken never asks for one.