Run without an API key#
The independent consumer apps use the real SDK with fixed responses. They are useful for verifying an installation before connecting live inference.
# From a repository checkout, with Node 22.12+:
npm ci
npm run pack:devtools
cd examples/react-vite
npm install
npm run devOpen the URL printed by Vite. Trigger a sample request and open the inspector. Sample answers are fixed; editing a message does not invoke a model.
| Example | What to explore |
|---|---|
| React + Vite | Minimal public-export integration, server plugin, and sample request |
| Next.js App Router | Route Handler, Server Action, and Server Component sharing an adapter |
| Playground | Choice, Score, Noul, Box, retries, failures, and cancellation |
The playground is a local tool. Its production build is not a hosted interactive demo.
Explore complete flows#
Cookbooks are repository examples, not files shipped in npm. Each includes setup and sample limitations.
| Cookbook | Techniques |
|---|---|
| SDE cascade | Returning conditionals and explicit escalation policy |
| Hierarchical classification | Bounded loops, collections, beam versus greedy search |
| Structure recovery | Tasks, runtime requests, and conditional continuation |
| Simple memory | Customer-scoped, run-local sample memory |
| RAG passages | Inspectable passage workflow |
| Skill suggestion | Dynamic questions and application-owned ranking |
Add your own interaction#
For docs contributors: examples can have small, page-specific TypeScript modules. The introduction's fixture switcher is one example. Richer demos can load React or the public package lazily when needed. Keep sample policies labeled and API credentials on a server; the static docs app has no inference backend.
Learn one method at a time#
Flows from scratch has small checked examples for tasks, Jev requests, conditionals, parallel lanes, maps, and loops. Use the API glossary to look up their interfaces.