Each card names its repo path and how to run it. The agent examples use a deterministic mock LLM provider where possible, so they run in CI with no keys — the parts that need a real key say so.
A React chat UI, a Bun API running a real server-side agent loop (model → tool_calls → execute → final answer) through the gateway, and the whole app exposed as an MCP tool — one binary, one origin.
riz new ai-chat && cd ai-chat && riz --dev[agent] block makes the binary a delegable A2A agentThe other scaffoldable starter beside ai-chat: a Bun API and a React/Vite client colocated on one binary, one origin — no second host, no CORS. riz new typescript-todo.
Three plain functions — lookup_order, list_inventory, create_ticket — that auto-become typed MCP tools, including a typed JSON-Schema body.
riz --config examples/riz.agent.toml runA Python Agent SDK script that discovers riz tools over MCP and completes a conditional task — look up an order, open a ticket if it's delayed.
ANTHROPIC_API_KEY + a running rizAn agent loops over a batch of orders, chaining tool calls — the case where "what did this request cost in tokens?" stops being trivial.
--dev Tokens panelA wasm32-wasip1 handler that validates and prices an order entirely under WASI — deny-by-default, sub-ms cold start, not an echo toy.
db (Postgres) grant — best-effort, no DSN in guest memoryA Bun chat handler on the API Gateway v2 WebSocket contract — $connect, $default, $disconnect — with server→client push over @connections. Also callable as an MCP session tool.
The canonical "how do I build an HTTP API" example — GET/POST/PUT/PATCH/DELETE over /accounts/{id} with method dispatch, an in-memory store, and response-cache read receipts. No framework, just the AWS handler shape.
servedAt receipt shows cached vs freshThe API Gateway simple-response authorizer contract as two tiny handlers: auth-allow-bun authorizes and hands context to the handler; auth-deny-bun is the 401 path — distinct from the JWT/JWKS config recipes below.
The same echo handler in Bun, Node, Python, Rust, Go, and WASM — six runtimes asserted byte-equivalent by CI. Want the "how do I write a handler in X" reference? riz new scaffolds one per runtime.
Working riz.toml files for every posture — every one parsed and validated by the test suite, so the cookbook can't rot.
riz.agent.toml — the MCP/agent demo fleetriz.prod.toml — telemetry, auth, deploy gatingriz.workos.toml · riz.clerk.toml · riz.jwt.toml — JWT/JWKS auth recipeshttp-basic) on riz unmodified
(CI: aws_official_samples_run_on_riz_unmodified).
Browse all examples ↗