JevRouter

# JevRouter

**Faster agent decisions.** Models, subagents, skills, MCP tools, CLIs and plugins become one candidate set — Jev answers one typed Choice question, JevRouter enforces availability, permissions, risk and confirmation around it.

[](https://github.com/BillionsBobby/JevRouter/actions/workflows/ci.yml)
[](https://www.jevrouter.co/)
[](LICENSE)
[](package.json)
[](tsconfig.json)
[](CONTRIBUTING.md)

[Website](https://www.jevrouter.co/) · [Quickstart](#quickstart) · [Benchmark](#benchmark) · [Cookbook](docs/cookbook/README.md) · [Documentation](#documentation) · [中文](#中文介绍)

</div>

---

## Why JevRouter

Agents waste reasoning tokens on a question a fast decision model answers better: **which capability should handle this next?** JevRouter puts [Jev](https://www.jevrouter.co/) — a System One model that turns structured state into typed decisions with probability distributions — in front of your tools, while your reasoning model stays the execution and fallback layer.

The key contract is simple: **Jev owns the decision probabilities; JevRouter owns availability, permissions, risk and confirmation.** Router fields live under `router`, while the original `probabilities`, `confidence`, and complete provider response remain intact. Filtered candidates are never re-normalized.

- **Decision-only by default** — nothing executes implicitly; medium/high/critical capabilities require confirmation.
- **One call or a plan** — `route` answers one question; `plan` answers "which capability handles step 1..N" with serial, batch, and decomposed strategies.
- **Every surface** — models, subagents, Skills, MCP tools, CLIs, DSH plugins share one routing contract.
- **Receipts by default** — append-only decision/plan files with provenance hashes; what was decided, why, and at wha