Start with the official playground
The TypeSafe playground is the clearest first stop for a Jev sample because it is connected to the official console. The quick start explains the state and question flow; it does not turn a playground session into a benchmark for your application.
Use a small, non-sensitive state and ask one question whose answer space is explicit. A Choice selects one allowed option, a Score expresses an ordered level, and a Noul answers an independent yes-or-no question. Keep parsing, permissions and the final action in ordinary code.
Choose a demo by the job it demonstrates
| Entry point | Useful for | Check before adapting it |
|---|---|---|
| Official playground | Learning the request and answer shapes | Which model and account settings the session uses |
| nexibeo/jev-cookbook | Task examples such as triage, tagging, extraction and retrieval | Its README describes a community resource and its provider path |
| Jev Showcase | Viewing several typed answers in one interactive example | It is an independent showcase, not the official console |
| Jev Ultrafast | Choosing a browser operation and a visible target | The separate language model writes text for TYPE_TEXT; Jev chooses the operation |
These entries answer different questions. A playground teaches the interface, a cookbook shows composition, a showcase makes output easy to inspect, and a browser integration places one bounded decision inside a larger loop. The cookbook guide has the longer recipe list and links to the official patterns.
Read the output before judging the demo
Look for the mapping from each answer to a stable application value. A useful example shows what happens when no option fits, when evidence is missing, and when confidence is too low for an automatic action. A colored label or a polished animation does not explain those boundaries.
For a search or retrieval demo, preserve the source ID next to the selected passage. For a routing demo, keep the chosen tool or owner separate from the model's explanation. For a browser demo, bind the numeric target to the same live snapshot and verify the result after execution. Those boundaries make a sample reusable instead of merely impressive.
A short checklist for a runnable Jev sample
- Identify the project owner and whether the entry point is official or community-maintained.
- Record the provider, model ID, SDK version and credential location.
- Write down the state fields and every allowed answer, including the fallback.
- Run an ambiguous input and an out-of-scope input, not only the happy path.
- Check whether the demo sends text, images, files or history to a remote service.
- Measure your own labeled examples before connecting an external action.
For a conceptual explanation of the primitives, read what Jev is. For a comparison that includes calibration, coverage and cost, use the evaluation guide. The directory's demos category is a discovery list; each repository still needs its own source and limit check.