Recipes

Each recipe is a single MDX page with a complete copy-paste flow. You can lift the whole page into an LLM's context, point it at your stack, and get a working integration.

Recipes pull from agentic-commerce/e2e/boson/tests/complete-marketplace-journeys.test.ts — the canonical end-to-end reference.

Full flows

• E2E seller flow — register → list → fulfill → withdraw.
• E2E buyer flow — browse → commit → redeem.
• Mutual dispute resolution — both sides sign, one submits.

Common patterns

• Token-gated launch — restrict offers to NFT holders.
• Digital + physical bundle — one offer, two items.
• ERC-20 approve + commit — the two-step path.
• Gas-less commit (Biconomy) — meta-tx via relayer.
• Threshold-buy agent — autonomous buyer that watches and pulls the trigger.
• Webhook server for state changes — production-grade event listener.

x402 recipes

• x402 buyer paying for a digital asset.
• x402 server email-fulfillment.

Non-code

• Sell via WooCommerce — plugin install and configuration.

Migration

• Migrate from legacy v2 — for teams coming from the older Boson stack.

Why recipes are separate from Build

Build pages explain a single task ("publish an offer") with stack-tabbed snippets. Recipes combine multiple tasks into a working program. The same content might appear in both, but Build is task-focused didactics and Recipes is copy-paste integration. Pick whichever matches what you're trying to do.