Jev API examples

Choice: pick one Jev label

Choice and score calls in real repos ↗ use this same request shape.

The best first Jev integration is a question your application already answers imperfectly with rules or a general-purpose model. Name the output and define the values your code can handle. Pin jev-1.13.0 once the threshold is tuned.

const response = await fetch("https://jevmodel.org/v1/systemone", {
  method: "POST",
  headers: {
    "Authorization": "Bearer " + process.env.JEVMODEL_API_KEY,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    state: message,
    model: "jev-latest",
    questions: {
      topic: {
        type: "choice",
        instructions: "What is this about?",
        criteria: { billing: "payments", bug: "broken product", account: "access" }
      }
    }
  })
});
const result = await response.json();

Score: place Jev on an ordered scale

Ask Jev where the state sits on a 2–10 level rubric you describe in words. The returned score can be fractional. Use it for urgency, risk, lead quality, or review priority — then threshold in code.

Noul: a Jev yes/no probability

A noul is a calibrated probability that a proposition is true. It is the right primitive for escalate / allow / needs-review gates. There is no separate confidence field; the probability is the certainty measure.

Batch related Jev decisions

Ask for topic, severity, and escalation in the same request when they share the same input state. They run together and share the state token cost. Keep each question independently useful so you can measure it.

questions: {
  topic: topicQuestion,
  severity: severityQuestion,
  escalation: escalationQuestion
}

Put a fallback behind every Jev action

A typed value makes branching easier, not risk-free. Log the input, output, probability, model version, and downstream result. Set a confidence threshold and route uncertain cases to GPT, Claude, or a human.