End-to-end recipes you can copy into production. Each cookbook is a small working agent that solves one real commerce problem, wired through the CodeSpar SDK.

Cookbooks

@codespar/sdkv0.3.0

Every cookbook is a runnable example — not pseudo-code. Copy the file, fill in your API key, and it executes against CodeSpar's sandbox. Swap csk_test_ for csk_live_ when you're ready.

Every cookbook ships with a test key that points at CodeSpar's sandbox. You don't need provider accounts to get it running — mock data flows through end-to-end.

Payments

COOKBOOK

Pix Payment Agent

The simplest agent you can build with CodeSpar. Create a Pix charge, generate a QR code, and send it to the customer via WhatsApp — in ~50 lines of code.

COOKBOOK

Multi-Provider Routing

Route payments across Stripe, Asaas, and Mercado Pago automatically. The agent calls codespar_pay — CodeSpar picks the best provider for each transaction.

COOKBOOK

Bulk Refund

Refund a batch of payments in parallel using session.loop(). Handle partial failures without aborting the whole run.

COOKBOOK

Cross-Border Fintech

Accept a USD card charge, settle to a BRL account, issue the fiscal document. One transaction, explicit FX surcharge, LGPD-ready audit trail.

End-to-end commerce

COOKBOOK

E-Commerce Checkout

Build an AI-powered checkout flow that handles product discovery, payment, invoicing, and shipping — in a single conversation.

COOKBOOK

Marketplace Payout

Split a marketplace transaction into platform fee + seller payout. One agent, two settled transactions, full audit trail.

Architecture patterns

COOKBOOK

Streaming Chat Agent

Real-time commerce chat with token-by-token streaming. Next.js App Router + Vercel AI SDK. Tool calls appear in the UI as they happen.

COOKBOOK

Webhook Listener

React to payment webhooks with a deterministic loop. On payment.confirmed, automatically issue an NF-e, create shipping, and send WhatsApp — no agent, no LLM, no surprise.

COOKBOOK

Multi-Tenant SaaS

Each customer runs their own agent with their own providers and credentials. Sessions are scoped per tenant — isolated by design, metered per tenant for billing.

How the cookbooks are structured

Every cookbook follows the same shape so you can skim one and jump to any other.

The scenario. A one-paragraph problem statement — who the user is, what they want, what constraints apply.
The code. A single file, fully typed, no dependencies beyond @codespar/sdk and what the scenario actually needs.
Walkthrough. Why each part exists. What would break if you changed it.
Test run. Exact CLI commands to execute the cookbook against sandbox and what the output looks like.
Production checklist. What to change before you ship. Usually: environment, API key prefix, error handling for the failure mode that matters for that flow.

Build your own

Missing a scenario? All cookbooks live in content/docs/cookbooks/*.mdx in this repo. Click "Edit this page on GitHub" on any cookbook to contribute.