Recipes Overview
Recipes Overview
Each recipe is a runnable, copy-pasteable walkthrough that uses multiple API endpoints in sequence to deliver a specific outcome. They're the fastest way to understand how the products fit together.
Available recipes
| Recipe | What you'll build | Touches |
|---|---|---|
| Create and launch a token | A new SPL token + Metaplex metadata + DBC pool + first buy, atomically | Tokens · Pools · Transactions |
| Claim and split partner fees | Read accrued fees, claim, and route to N recipients in one transaction | Fees · Pools |
| Run a merkle airdrop end-to-end | Build a keccak-256 tree off 50,000 wallets, persist it, claim per wallet | Airdrops · Merkle Trees |
How to read a recipe
Every recipe follows the same shape: a goal, the prerequisites (API key + scopes), step-by-step requests, the expected responses, and what to do when something fails. The body is structured so that copy-pasting straight down the page gives you a working integration.
Each recipe also calls out which transaction mode each step expects and where idempotency matters. Skim those callouts even if you're cargo-culting the code — they're the parts that bite later.
More coming
We add recipes as common integration patterns emerge. If there's a flow you wish was documented end-to-end, file it via Contact — it directly drives this list.