BillionsBobby/JevRouter: first run, 2026-10-11
Installed from its README in a throwaway sandbox by Claude Code (Claude Opus 5.5), with a Jev API key in the environment and nothing else: no GPU, no desktop, no other paid keys, no accounts. The README's first example was run once. Repo commit b1cdf80593ee; 46 seconds. All results · Task
Quick start: ran. Jev calls made: 1.
| Install | npx --yes github:BillionsBobby/JevRouter (README's npx-from-GitHub form; installs and runs in one step, no separate install) |
|---|---|
| Quick start, as run | npx --yes github:BillionsBobby/JevRouter route --provider typesafe --request "Find original sources before summarizing" --candidates '[{"name":"search_web","description":"Find web sources"},{"name":"summarize","description":"Summarize existing sources"}]' |
| What came back | Exit 0. status=selected, decision.selected=search_web (jev_probability 1, summarize 0), raw_jev.model=jev-1.13.0, usage 350 in / 35 out tokens, runtime.source=live, elapsed_ms=335, receipt saved to .jevrouter/decisions/dec_eab6ff8c-....json. stderr: 'JevRouter END status=selected ... selected=search_web'. |
| What stopped it | Nothing. |
Steps the README does not mention
- Skipped the README's first command ('agent start --agent codex'): it launches a separate host agent (Codex/Claude Code/Cursor) and asks for the key interactively. Ran the next example, 'Route one decision', which is the smallest one that calls Jev.
- The 'Route one decision' example is only written for OpenRouter (OPENROUTER_API_KEY, --provider openrouter). To use the official TypeSafe key I swapped in '--provider typesafe'. That name comes from the README's 'Choose typesafe' prompt text and from src/cli.ts; no README example shows it as a CLI flag.
- Cookbook 01 lists only OPENROUTER_API_KEY or JEV_API_KEY as prerequisites, but the README also accepts TYPESAFE_API_KEY. The key was already exported under that name, so nothing had to be renamed.
The session's closing message
The quick start worked on the first try. JevRouter installed and returned a real Jev decision after one Jev call. - **Install:** the README has no separate install step. Its `npx --yes github:BillionsBobby/JevRouter …` command downloads and runs the tool in one go, and it worked on Node 22. - **Which example I ran:** the README's first command, `agent start --agent codex`, opens a separate coding agent and asks for the key interactively, so I skipped it. I ran the next one, "Route one decision", which is the smallest example that calls Jev. - **Result:** exit code 0, `status: selected`. Jev picked `search_web` with probability 1 (over `summarize` at 0). The response came from the live service (model `jev-1.13.0`, 350 tokens in and 35 out, 335 ms). The tool also saved a local record of the decision under `.jevrouter/decisions/`. - **Steps the README doesn't spell out:** - That example is written only for OpenRouter (`--provider openrouter` with `OPENROUTER_API_KEY`). To use the TypeSafe key I changed the flag to `--provider typesafe`. I got that name from the setup prompt text the README mentions and from `src/cli.ts`; no README example shows it as a flag. - The README accepts `TYPESAFE_API_KEY`, so the key worked under its existing name. The "Route your first request" docs page lists only `OPENROUTER_API_KEY` and `JEV_API_KEY`. - **Key safety:** the key was never printed, and I checked that it does not appear in any file the run wrote. DELIVERABLE: ~/work/output/report.json