Why not just use the official SDK directly?

If you need one-off questions, the readme says to use TypeSafeClient directly. Use jod when you want state validation, typed projections with confidence sidecars, and fixtures; everything below the schema layer remains the SDK.

Can one question depend on another in the same call?

No. Questions in the same ask are evaluated independently and one answer never becomes hidden context for another. If a second judgment depends on the first, call ask again against a new state.

How do I handle Jev model alias drift?

jod sets no model and the chain resolves to jev-latest, while the account exposes jev-latest and jev-preview as aliases. Put the id in one place and assert on $model, which returns the concrete version like jev-1.13.0, so a silent alias bump fails your suite.

Can it do arithmetic or resist hostile input?

No. Keep arithmetic in code, keep state small and pointed, and write exact conditions, since Jev has documented jaggedness on arithmetic, counting, dates, and context rot. State is treated as data, not hostile, so sanitize and test before exposing it.

What happens if my state does not match the schema?

Validation runs locally before the request is spent; an invalid state raises JodStateError and no request is made to Jev.

How do I read confidence and probabilities?

ask() returns a flat typed object plus $-prefixed sidecars: $confidence per Choice and Score, $probabilities with the full distribution, $raw, $model, and $usage; the prefix stops sidecars colliding with question ids.

How do I test without the network?

Build a TypeSafeClient with fixtureFetch, which returns a Fetch the SDK uses, so tests keep the SDK's parsing and error handling and give up only the socket.

CommunityJev Repos & SDKs

Jod

TypeScript layer that binds a Standard Schema state to Jev Choice, Score, and Noul questions, validating locally before sending one parallel request with typed projections.

See highlights

Open github.com

Stars: 3
Language: TypeScript
License: MIT
Published by: Community
Author: mateonunez
Last verified: Oct 2026

mateonunez/jod

User repository on GitHub

View on GitHub

Semantic schemas over TypeSafe's Jev — validate the state locally, then project typed answers.

Forks: 0
Last pushed: Updated Sep 2026

Repo stats from the GitHub API, cached Oct 2026.Homepage

About this project

Semantic schemas for TypeScript. Bind a state schema and a set of questions into one artifact, then get typed answers back. Zod validates data you already understand. Jev judges data you don't. jod is the seam: your state is validated locally and for free, every question goes out in one parallel Jev request, and the answers come back as domain values your code can branch on.

Quoted from the project's README. Read the full README.

Tagscommunity jevbest catalog-import awesomejev

Works forJev for Classification

Used inJev for Software & DevTools

Languages: TypeScript

Highlights

Invalid state raises JodStateError before any request, so local validation costs nothing.
All questions in one ask travel together, run in parallel, and stay independent with no hidden context.
Noul thresholds live on the schema with 0.5 default, are never sent to Jev, and raw probabilities stay available.
fixtureFetch supplies deterministic fixtures through real SDK parsing for network-free tests.

Watch out

Built on the official SDK with retries and error taxonomy re-exported; confidence signals whether to act and is not a correctness guarantee. One question is one snap judgment with no chaining, and images, audio, and video are unsupported. Copy reviewed against the repository README on 2026-10-04, not from running it.

Questions about this entry

Short answers drawn from the linked project or page.

More Jev resources like this

zod-jev

Zod 4 companion that adds Jev meaning checks to shape checks: one parseAsync call sends every semantic rule as noul questions in a single request and turns probabilities into ordinary Zod issues.