DEV Community

Cover image for Build with Brickken Dev Campaign
Stefan Gherghe
Stefan Gherghe

Posted on

Build with Brickken Dev Campaign

#agents #api #mcp #web3

Build with Brickken: a 6-week programme on tokenization + agentic infra ($2K prize pool)

TL;DR
We're running a 6-week developer programme from Aug 7 to Sep 17. Build a working tokenization or agentic workflow against Brickken's sandbox using the REST API, CLI, MCP server, or Brickken Skill.

  • Five prizes
  • $2,000 pool
  • Deadline Sep 17 at 23:59 CET.

Landing page: https://landing.brickken.com/build-with-brickken?utm_source=dev.to&utm_medium=organic&utm_campaign=b2b_buildcampaign

Hey DEV, I'm Stefan, Social Media Manager at Brickken. Disclosure upfront: this is a Brickken programme and I work there.

If you've been experimenting with x402, ERC-8004 identity, MCP servers, or tokenized real-world assets and want a concrete brief to build against, here's one with real infra and a prize pool behind it.

What you can build with

Brickken exposes four surfaces you can mix and match:

  • REST API for institutional tokenization workflows (issuance, transfers, compliance, lifecycle).
  • CLI, chain-agnostic, for scripted deploys and agent-driven flows.
  • MCP server so any MCP-compatible client (Claude, GPT, custom agents) can call Brickken as a tool.
  • Brickken Skill for agent frameworks that consume Skills directly.

On top of those, the campaign gives you a testnet-only playground for:

  • x402 for per-call USDC payments over HTTP
  • ERC-8004 for on-chain agent identity
  • ERC-7943 (uRWA), the tokenized real-world asset standard co-authored by our Head of Blockchain
  • ERC-8226 (RAMS) for regulated agent mandates
  • Chainlink CCIP for cross-chain flows

Sandbox, not mainnet

All work runs against:

  • https://api.sandbox.brickken.com/
  • https://dapp.sandbox.brickken.com/

Testnet faucet assets only. No real USDC, no bridging, no mainnet keys.

Target networks depend on which challenge you're building for:

  • Agentic challenge: Ethereum Sepolia or Base Sepolia (x402 settlement is available on both)
  • API-key builds: Polygon Amoy is also supported
  • RAMS operations: Ethereum Sepolia only for now

Full API reference and quickstart at docs.brickken.com.

What we're looking for in a submission

  • Working implementation. Not a mockup, not a slide deck. It has to actually run.
  • Public repo, or a private one with a Brickken reviewer added, plus a README on what it does, how to run it, and which surfaces (REST, MCP, CLI, Skill) and methods you called.
  • Real, verifiable calls against the Brickken sandbox. Your submission must include the chainId and the transaction hashes your build produced. We verify claimed usage against our own transaction and payment records.
  • 2 to 3 minute demo recording, or a live URL we can hit.
  • An EVM wallet address for potential reward payout.

If you use AI tools in your build, disclose them in the README. AI assistance is fine; wholesale generation without meaningful developer contribution is not.

How to submit

Both channels are required for your entry to count:

  1. Post in the Discord #submit-your-builds channel
  2. Email build@brickken.com

Deadline is the same for both: Sep 17 at 23:59 CET.

How it's judged

Reviewed by the Brickken engineering team on four criteria:

  • Technical execution
  • Depth of Brickken infrastructure use
  • Originality of the use case
  • Clarity of documentation

Decisions are final.

Prizes

$2,000 pool across the top 5 submissions, regardless of which challenge you build in. One deadline, five payouts.

A few build ideas to prime the pump

Not requirements, just angles that fit the stack well:

  • An MCP server that lets a chat client issue and transfer tokenized assets against sandbox
  • An agent that discovers itself on ERC-8004, sells a data or compute service, and gets paid per call via x402
  • A CLI wrapper that deploys an ERC-20 and an ERC-7943 uRWA in one command across two testnets
  • A CCIP-powered cross-chain redemption flow for a tokenized asset
  • Anything that composes at least two of REST / CLI / MCP / Skill in a workflow that would look ridiculous to build without automation

How to join

  1. Read the brief: https://landing.brickken.com/build-with-brickken?utm_source=dev.to&utm_medium=organic&utm_campaign=b2b_buildcampaign
  2. Request a sandbox API key
  3. Join the Discord for build support and submissions
  4. Ship before Sep 17, 23:59 CET

Ask me anything in the comments. If your question is more of a "how do I call X endpoint," docs.brickken.com or the Discord support channel will get you a faster answer than I can.

Good luck. Curious to see what you build.

AI #Campaign #Dev #Build #Tokenization

Top comments (0)