Question 1

Is this just a thin curl wrapper, or does it save me writing plumbing?

Accepted Answer

It saves the plumbing. Four commands cover all three primitives plus a batch runner that sends multiple questions in one System One request instead of one call per question. Input can be a literal, stdin, an @file path, or --json-state with named fields your instructions can reference. Output is compact JSON by default, --value prints only the primary number for shell scripts, and exit codes are structured for automation.

Question 2

Will my provider key end up in shell history or in the process list?

Accepted Answer

Not through the normal paths. auth set deliberately refuses the key as a command-line argument; you paste it at a hidden prompt or pipe it in, and TYPESAFE_API_KEY from the environment takes precedence over the credential file. The fallback credential path follows XDG conventions, the directory is created mode 0700, and credentials.json is written atomically with mode 0600. auth status and auth test never print the key.

Question 3

Can I point the custom provider at a proxy I do not fully control?

Accepted Answer

You can, and the README says to be careful: the CLI sends JEV_API_KEY to that endpoint as a bearer token, so it advises using only a trusted HTTPS endpoint. --endpoint replaces JEV_ENDPOINT for a single command, while JEV_ENDPOINT, JEV_API_KEY, and JEV_MODEL configure it for the process. The custom provider exists specifically to keep proxy credentials isolated from the built-in ones.

Question 4

Do the MCP tools reject bad input before spending an API call?

Accepted Answer

Yes for the cardinality rules. jev-mcp ships with the CLI and exposes noul, choice, score, and run over stdio. choice requires at least two options and score at least two levels, and a smaller request is rejected as a tool error before any provider call. Every argument is described in the published tool schemas so a host can build a valid call without reading the docs.

Question 5

How do I install it, and what does it require?

Accepted Answer

uv tool install jev-cli, which keeps both jev and jev-mcp on your PATH; uv is required and installs a compatible Python 3.13+ interpreter when needed. You also need an API key for whichever provider you use, with the official TypeSafe API as the default.

Question 6

How does auth keep the key out of shell history and the process list?

Accepted Answer

auth set uses a hidden prompt and does not accept the key as a command-line argument, so it never lands in process arguments or shell history. TYPESAFE_API_KEY takes precedence over the credential file, which falls back to XDG config with a 0700 directory and an atomically written 0600 file.

Question 7

Which providers can it talk to besides TypeSafe?

Accepted Answer

Vercel AI Gateway (typesafe-ai/jev), OpenRouter (typesafe/jev-1.13), Cloudflare Workers AI (clef-flash, or clef), and a Jev-compatible custom proxy using JEV_MODEL or jev-latest. Select one per command with --provider or for the process with JEV_PROVIDER, and --model can override the provider default.

Jev CLI — tumf

About this project

Highlights

Quickstart

Questions about this entry

Reactions & coverage

From the Jev guides

From the Jev AI model community