Recipes 01 hands-on 6 min Updated Sep 20, 2026

Prepare materials

API key, SDK or HTTP, optional Gateway; decide atomic judgments, state fields, thresholds, and escalate paths before you code.

Goal

Have accounts, a first call path, and a design checklist before you automate support, RAG, or n8n.

Ingredients

  • TypeSafe API key as TYPESAFE_API_KEY (console).
  • Call path: official Python/JS SDK, or raw System One HTTP; optional Vercel AI Gateway model typesafe-ai/jev.
  • Feel first: Playground (or community jevplayground.com).
  • Optional: Agent skill for coding agents — not required for these tutorials.

Design checklist (before coding)

  1. Which judgments are atomic (one Choice / Score / Noul each)?
  2. Which state fields does each question need — and what stays out?
  3. Which thresholds will code own (confidence / P(yes))?
  4. Where does low confidence go (human, confirm, LLM draft)?

What Jev decides vs code

JevCode
Narrow typed judgmentsControl flow, side effects, composition, escalate

Calling hosted Jev from your laptop, plus independent local runtimes, is on the local deployment checklist. Product notes: Compare.

Next

→ Support routing

Sources