j.jevmanual.
IndependentChecked 2026-09-21·jev-1.13.0

The Jev Manual

A practical desk reference for state, typed questions, API contracts, models, and production decisions.

On this pageFind your guideA useful starting point

Find your guide

Jev API Reference & Practical Guide

Authentication, state, typed questions, response fields, curl examples, rate limits, and version pinning.

Jev Models: Aliases, Versions and Production Pinning

Understand jev-latest, jev-preview, actual response models, language support, context limits, and model listing.

Jev Pricing Explained: Cost per Request & Token Calculator

Calculate direct input cost, understand shared-state billing, and distinguish provider accounting.

Jev State Guide: How to Structure Context Correctly

Build focused state with clear fields, relevant policies, and enough evidence for each typed question.

Jev Choice vs Score vs Noul: Complete Guide

Choose a fixed category, an ordered rubric, or the probability of a single proposition.

Jev Choice: Options, Probabilities, Confidence & Examples

Write distinct Choice criteria, inspect the distribution, and route safely with confidence.

Jev Score: Rubrics, Levels, Probabilities & Examples

Design ordered Score rubrics and interpret weighted results without confusing them with exact numerical measurement.

Jev Noul Explained: Yes/No Probability from 0 to 1

Interpret Noul values, define yes/no criteria, and choose thresholds using the costs of mistakes.

Jev Confidence Explained: Thresholds, Probability & Human Review

Separate probability from confidence and choose action thresholds using labeled data, risk, and review capacity.

Ask Multiple Jev Questions in One Request

Share state across independent questions, understand both token limits, and keep dependent evaluations separate.

Jev Limitations: 9 Things Jev 1.13 Can Get Wrong

The nine documented Jev failure modes, concrete bad examples, and practical alternatives.

A useful starting point

Make a first request, inspect the distribution, then add the review path. The same support-ticket state appears throughout the core pages to keep concepts connected.

Search the manual