Skip to content
Jev Guide

Field notes / Jev

Small decisions.
Real possibilities.

Explore how Jev turns text into structured decisions, with practical examples, code, and community projects.

Start with the basics.

The input below is a sample. Open the message routing recipe to run this question yourself.

Experiment 01

Where should this message go?

Sample

Read-only preview. Nothing here is sent anywhere.

Run
Run this with your own keyOpens the message routing recipe, which asks this same question.
Output

No recorded answer for this sample yet. The message routing recipe runs this question for real, and the guide below shows the request and the shape of the answer.

Make your first API request

Three ways to put Jev to work.

Route a message, score its urgency, or check whether a reply covers the request. Explore an example, then try your own.

  1. 01 / CHOICE

    Route a message

    Choose which department should handle a customer message.

    Customer message

    “Hi, I was charged twice for my subscription this month. The two charges show up on my card statement on the 3rd and the 4th. Can you refund one of them?”

    1. billing(charges)
    2. account(login)
    3. technical(bugs)
    4. sales(pricing questions)
    5. other(anything that does not fit the departments above)
    Illustrative example

    Diagram only. Probabilities appear once a live or recorded result is shown.

    Try message routing
  2. 02 / SCORE

    Score urgency

    Evaluate how urgently a message needs attention.

    Message

    “Our largest customer's dashboard has been showing stale data since this morning, and they are presenting it to their board right now. Could someone look at this immediately?”

    RoutineTime-sensitiveUrgent

    Score 1.82 of 2: a read against the rubric above, not a measurement.

    Illustrative example
    Try urgency scoring
  3. 03 / NOUL

    Check a reply

    Check whether a draft reply addresses the customer's explicit requests.

    Customer

    “Can you refund my last payment and send me a confirmation email once it's done?”

    Draft reply

    “I've processed a refund for your last payment. You'll receive a confirmation email at the address on file within the next few minutes.”

    Addresses all explicit requests

    Diagram only. A real answer returns one probability from 0 to 1.

    A coverage check, not a fact check.

    Illustrative example
    Try reply checking
Browse all recipes

Start building / Guide 01

Your first Jev request.

Route a support message with TypeScript. Define the departments, send the message, and use the returned decision.

TypeScript · Beginner

  1. 1

    Provide the message

    The text Jev evaluates.

  2. 2

    Define the departments

    The options it can choose from.

  3. 3

    Use the decision

    Handle the result in your application.

Read the TypeScript guide Try the message routing recipe

More guides

message-routing.tsTypeScript
const message = "Hi, I was charged twice for my subscription this month. The two charges show up on my card statement on the 3rd and the 4th. Can you refund one of them?";

const { answers } = await client.systemOne({
  state: message,
  model: "jev-latest",
  questions: {
    department: choice(
      "Which department should handle this customer message?",
      {
        billing: "Charges, invoices, refunds, payment methods, subscription costs",
        account: "Login, password, profile, permissions, closing or changing an account",
        technical: "Bugs, errors, outages, integrations, something not working",
        sales: "Pricing questions, plan comparisons, upgrades, purchasing for a team",
        other: "Anything that does not fit the departments above",
      },
    ),
  },
});

const { choice: result, probabilities, confidence } = answers.department;
Excerpt. Setup and the complete example are in the guide.
answers.departmentResponse shape
{
  choice: "billing" | "account" | "technical" | "sales" | "other",
  probabilities: { … },
  confidence: 0–1
}

No recorded response yet. This is the shape only, not a result. See the guide for a full response.

Community

Built with Jev.

Three projects to start with. Every entry is checked against its own repository. Listing is not an endorsement.

Explore all projects
  1. Coding agents

    Jev Review

    by devagrawal09

    Runs a staged pipeline of Jev judgments over a git diff or a whole codebase and reports findings in a local dashboard, keeping every threshold in code.

    View repository (opens in a new tab)
  2. Automation and integrations

    HA-Jev

    by AboveColin

    Turns Jev questions about Home Assistant entities into sensors and automation actions, with a daily token budget and per-day spend reporting.

    View repository (opens in a new tab)
  3. SDKs and developer tools

    pg-jev

    by realZachi

    A PostgreSQL extension that lets plain-language conditions filter, rank, and classify table rows by sending batches to Jev, with no embeddings or vector column.

    View repository (opens in a new tab)

Official resources