JevRouter

It depends what you measure. On first-five tool-call prediction across 10 Toolathlon tasks with inventories from 9 live MCP servers, Jev serial hit 38% of positions and decompose-plus-thread hit 44%, versus 24% for DeepSeek V4.1 Flash, at 1.58 s per task and about $0.0058 per 10 tasks. It measures ordered routing decisions, not end-to-end task completion.

Nothing executes implicitly. The router returns a decision and lets your code act on it; medium, high, and critical capabilities require confirmation, and exit code 2 signals review or no-decision. Confidence gates, risk levels, and permissions are yours to set in policy.json.

No registry needed: you can pass candidates inline to route or supply a JSON file. Models, subagents, Skills, MCP tools, CLIs, and plugins all share one routing contract, and a discover command builds candidate manifests. Discovery status is carried explicitly so a strict project can set require_verified_candidates and block unverified descriptions.

Not from the dashboard alone. Decisions and plans are written as append-only receipts with provenance hashes, but the local dashboard shows execution outcome as not collected until your host writes execution feedback, so a selected capability is never presented as a completed task.

Node 20 or newer. npx --yes github:BillionsBobby/JevRouter agent start --agent codex (or --agent claude, --agent cursor) installs the Skill and project instructions, checks Jev and launches the host. Choose typesafe or openrouter at the prompt; the key stays in the process environment and is never written to project files, and setup adds .jevrouter/ to .gitignore.

The labelled demo provider, --provider demo, runs everything offline without a key. Candidates can also be passed inline to route so no registry is needed, and the local dashboard reads .jevrouter/decisions and plans with no Jev request and no upload.

An SDK with route() and plan(), an HTTP server (serve --port 8787) exposing POST /route, GET /capabilities and GET /health, and an MCP server (serve-mcp) that exposes a single jev_route tool to MCP-native agents. The CLI exits 0 on a selection, 2 for review or no decision and 1 on error.