Why not just script the HTTP endpoint with curl and jq?

Raw requests leave retries, timeouts, validation, and output shaping to you. This adds typed validation, two retries on rate limits and server errors, JSON and distribution output, and pipe-friendly exit codes.

Does batching actually save round trips and effort?

Yes for round trips: questions in one document are evaluated together, so four questions cost one request. Speculative questions are cheap enough to include and ignore when unused.

How do I avoid blowing the shared context budget with logs?

Keep state small and name the field each question targets, since keyed and explicitly referenced state scores better in the documented examples. Only the state is sent with the key in the header.

Can I trust mid-range scores and unanimous distributions?

Treat mid-range values as leans rather than verdicts, low confidence as a branch signal, and unanimous tails as ordering rather than fine-grained calibration. Question ids only label answers and are never sent.

What key sources does it check, and in what order?

The flag first, then the TYPESAFE_API_KEY environment variable, then a path in TYPESAFE_API_KEY_FILE, then apiKey or apiKeyFile in the shared pi-jev config, and finally a token file in your home directory. The pi-jev file can also set the model and endpoint, and verbose output names the source it used.

What do the exit codes mean for scripting?

Zero means an answer was returned, one means the request failed after retrying rate limits and server errors twice, and two means the command line or the questions document was invalid. Everything except the answer goes to stderr, so stdout stays pipeable and validation failures exit before any billed request.

Can I run it without a global install?

Yes. The checkout runs the TypeScript source directly, so nix run and node src/cli.ts need no build step, and the flake exposes a default package so a system or home configuration can put jev on PATH. npm is the exception: Node refuses to strip types under node_modules, so the published package compiles src to dist first.

CommunityJev Tools & CLIs

TypeSafe CLI — y0usaf

Shell CLI that sends state plus noul, choice, and score questions to Jev in one request and prints probabilities, choices, and rubric positions for pipes and scripts.

See highlights

Open github.com

Stars: 4
Language: TypeScript
License: MIT
Published by: Community
Author: y0usaf
Last verified: Oct 2026

y0usaf/typesafe-cli

User repository on GitHub

View on GitHub

Ask Jev typed questions from the shell: noul, choice, and score answers as numbers, not prose

Forks: 0
Last pushed: Updated Sep 2026

Repo stats from the GitHub API, cached Oct 2026.

About this project

A shell command for Jev: state and typed questions in, typed answers out. Jev does not write prose, so nothing here parses any. A noul comes back as the probability that the answer is yes, a choice as one of the options you supplied plus the confidence behind it, and a score as a position on your rubric. Jev evaluates the questions in one request in parallel and in isolation, so asking four costs one round trip of about 0.3s and not four. That is what ask is for: a whole document per call, not a loop.

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

Tagscommunity jevbest catalog-import awesomejev

Works forJev for Classification Jev for Ranking

Used inJev for Software & DevTools

Languages: TypeScript

Highlights

Single-question commands plus an ask mode that batches a whole JSON document in one parallel round trip.
Key resolution checks flags, environment, key files, and the shared pi-jev config with verbose sourcing.
Local validation, JSON output, distribution display, and exit codes built for scripting and pipes.
Documents practical shaping tips like naming state fields and treating low confidence as a branch signal.

Watch out

State and questions share one context budget, so large logs can crowd out question room; validation failures exit before any billed request. 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.

Other listings of this project

Forks and copies of this project in the directory. This entry is the canonical one.

typesafe-cli

Stdlib-only Python CLI and agent skill that evaluates a state against typed Choice, Score and Noul questions over the System One API without generating prose.

Jev Agents & MCP#community#jevbest#catalog-import

Community

geilt/typesafe-cliPython

More Jev resources like this

draftpulse

A local React and Express editor that scores an X draft across six dimensions, from hook strength to a slop penalty, by asking Jev several narrow rubric questions in one structured call, with a deterministic fallback when no key is set.