Independent. Not affiliated with TypeSafe AI, the maker of Jev. Disclosures

Decision LayerUnofficial

Try “routing”, “confidence”, “leads” or “noul”.

    How-tos · 10 planned

    From first call to production, in order

    Each guide ends with something working. Code is checked against a named Jev version and dated, because the model and its gateways are changing fast.

    Start

    1. 01Make your first Jev callAn API key, one request with curl, then the same request in Python and JavaScript.In the works
    2. 02Call Jev through Vercel, OpenRouter or CloudflareThe same question on each gateway, and what changes (Vercel calls the yes/no type “boolean”).In the works
    3. 03Pick the right question typeChoice for a set of options, Score for a scale, Noul for yes or no, with a test for each.In the works

    Build

    1. 04Write questions Jev answers wellNarrow, one-property questions instead of one broad one, and why that matters.In the works
    2. 05Shape the state you sendOnly what the decision needs, as structured JSON, with numbers and dates turned into words.In the works
    3. 06Set confidence thresholdsAct, ask a stronger model, or ask a person, with thresholds set from your own data.In the works
    4. 07Combine answers into one scoreMany small questions in one request, weighted in code: the QA scorecard pattern.In the works

    Production

    1. 08Test Jev on your own dataA small private evaluation: labels, accuracy, calibration, cost and speed, in an afternoon.In the works
    2. 09Estimate your monthly costTokens per decision times volume, at $0.042 per million input tokens, with output free.In the works
    3. 10Replace an LLM classifier with JevRun both side by side, compare, then switch, as Vercel and Jack & Jill describe doing.In the works

    Preview of guide 01

    The smallest useful request

    One piece of state, one yes/no question. This is TypeSafe’s own quick-start request; the guide walks through every field and the answer you get back.

    curl -X POST https://api.typesafe.ai/v1/systemone \
  -H "Authorization: Bearer $TYPESAFE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "state": "Hi, I’ve been trying to connect my Stripe account for 3 days and the integration keeps failing.",
    "model": "jev-latest",
    "questions": {
      "urgency": {
        "type": "noul",
        "instructions": "Does this message express urgency?"
      }
    }
  }'

    Keep your key in an environment variable, never in code or a chat window. Request adapted from TypeSafe’s quick start (state shortened).