User repository on GitHub
JSON-in, typed-decisions-out CLI for the TypeSafe System One API
- Forks
- 0
- Last pushed
- Updated Sep 2026
Repo stats from the GitHub API, cached Oct 2026.
CommunityJev Repos & SDKs
Jev CLI — lhotwll217
A thin Node CLI over the System One API: pass a state string and a question map, get typed answers with probabilities, confidence, latency and token counts back as JSON, one at a time or through a batched worker pool.
- Stars
- 0
- Language
- TypeScript
- Published by
- Community
- Author
- lhotwll217
- Last verified
- Oct 2026
This is one of several Jev listings for the same project. The canonical entry is Jev CLI — shaharia-lab.
About this project
JSON in, typed decisions out. A thin CLI over the TypeSafe System One API (POST /v1/systemone, model jev-latest) for ad-hoc experiments, eval loops, and shelling out from an agent harness. It exists because reaching for an SDK or an agent skill is too much ceremony when you just want to probe how the model behaves across a hundred variations of a prompt state.
Quoted from the project's README. Read the full README.
Works forJev for Classification
Used inJev for Software & DevTools
- Languages
- TypeScript
Highlights
- Question maps are saved by name with jev schemas add, so an eval loop reuses the same typed questions while only the state text changes between runs.
- The key goes to the OS credential store, macOS Keychain, Windows Credential Manager or Linux, with TYPESAFE_API_KEY winning for CI.
- Batches are a client-side worker pool: JSONL on stdout in input order, the summary on stderr, failed rows inline, exit code 5.
- Bad question maps are rejected locally with a pointed message before any network call, so a typo in a 500-row batch costs nothing.
Watch out
The README is direct about the test suite: it runs against an in-process mock server and has not yet been run against the live API, with request and response shapes taken from the published API reference. Cost reporting is therefore opt-in by design, because the API returns token counts only and cost_usd stays null unless you export your own JEV_PRICE_INPUT_PER_MTOK and JEV_PRICE_OUTPUT_PER_MTOK rates; latency and tokens are always reported and never guessed. Retries are on by default at three attempts for 408, 429, 500, 502, 503, 504 and 529 with exponential backoff and jitter, which matters if you are measuring latency. Two operational notes: you need npm install, npm run build and npm link before jev is on PATH, and the published package ships compiled JavaScript for Node 20+ while running from source with node src/index.ts needs type stripping. JEV_CREDENTIAL_SERVICE exists so a sandbox key can sit beside your everyday one. 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.
It does not, by design. The API response carries token counts and no price, so cost_usd comes back null unless you supply the rates yourself through JEV_PRICE_INPUT_PER_MTOK and JEV_PRICE_OUTPUT_PER_MTOK, set to whatever your contract actually says. Latency and token counts are always reported and never estimated, so you can compute spend from them without trusting a hard-coded table.
No, and the README says so. The suite covers retry-then-succeed on 529, non-retry on 422, schema rejection, batch ordering under concurrency, partial-failure exit codes and the login, status and logout round trip, all against an in-process mock server. The live request and response shapes come from the published API reference, so treat the first real run as the actual integration test.
jev auth login uses a hidden prompt and saves to the OS credential store under the service name ai.typesafe.jev-cli, not to a plaintext config file in the repository. TYPESAFE_API_KEY overrides the saved credential for a session, which is what you want in CI, and non-interactive onboarding can read a token from stdin with jev auth login --with-token. JEV_CREDENTIAL_SERVICE lets you point at a different service name to keep two keys side by side.
jev warns once per run, on stderr and silenceable with --no-warn, when a choice has exactly two options: that is a noul with extra steps, paying for a probability map to carry one bit. It stays a warning rather than a rule, since the API allows it and so does the CLI. Anything beyond two options is where the choice type earns its place, since you get the full probability distribution.
npm install && npm run build then npm link puts jev on PATH, and jev auth login saves the key in the OS credential store; TYPESAFE_API_KEY takes precedence for CI or a temporary shell.
jev batch reads a schema and a JSONL of states, runs a client-side worker pool with --concurrency, writes JSONL results to stdout in input order, and sends the per-run summary to stderr.
The API returns token counts only, so cost_usd is null unless you set JEV_PRICE_INPUT_PER_MTOK and JEV_PRICE_OUTPUT_PER_MTOK; latency and token counts are always reported and never guessed.
More Jev resources like this
8GitHub stars
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.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
jomatsu/zod-jevTypeScript
jomatsu/zod-jevTypeScript3GitHub stars
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.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
mateonunez/jodTypeScript
mateonunez/jodTypeScript34GitHub stars
Drop-in Jev client wrapper that averages Choice predictions across option orderings in one request for stabler probabilities.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
TypeLLM/pijevPython
TypeLLM/pijevPython27GitHub stars
SwiftPM client for the TypeSafe System One API that mirrors the official JavaScript SDK, with typed Choice, Noul, and Score questions over Codable answers.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
krzyzanowskim/TypeSafeSwift
krzyzanowskim/TypeSafeSwift15GitHub stars
PHP 8.2+ client for Jev that sends a state with typed noul, choice, and score questions and returns one typed answer per question ID with probabilities and usage.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
sanmai/typesafe-ai-phpPHP
sanmai/typesafe-ai-phpPHP45GitHub stars
Go SDK plus a pipeline-friendly CLI for typed decisions, covering single questions, batched question maps, retries, and line-oriented filtering over stdin.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
mattn/go-jevGo
mattn/go-jevGoFrom the Jev guides
Original write-ups on what this entry is for.
Closed weights have not stopped the ecosystem from rebuilding the shape in the open. API-compatible servers, retrained heads on small models, and inference-time tricks that skip generation entirely.
Jev Repos & SDKs#open-models#research#local
Read article
From the Jev community
Posts from builders shipping with Jev right now.