OpenRouter integrates Jev into its smart routing system: calculates cache losses before switching models.

Insight Beating AI Flash News: OpenRouter has launched Jev Router, integrating the type-safe Jev into its model routing system. Before each request is dispatched, Jev evaluates task difficulty, precision requirements, and the adequacy of the current model and inference tier, then decides whether to keep the existing setup, boost inference intensity, or switch to another model. OpenRouter’s original Auto Router previously selected models based on task type: it first identifies the task category, then references seven days of usage data for similar requests to route. Jev Router goes a step further by assessing the specific difficulty of each individual round. For simple tasks, it can lower inference tiers; for complex ones, it increases reasoning effort. If the same model can still handle the task, it avoids switching unnecessarily. A critical practical factor here is context caching: when switching models during a long conversation, cached context typically cannot be reused, forcing the new model to reprocess the entire chat history. Jev Router accounts for this loss, only switching models if the expected benefit of the switch exceeds the switching cost, prioritizing retaining the same model whenever possible. OpenRouter’s internal testing shows that across four agent benchmarks totaling 423 tasks, Jev Router completed 237 tasks, compared to 130 for Auto Router—an ~82% increase in task completion. Additionally, in five other agent benchmarks, its median first-token latency was lower than that of other tested routers. Similar approaches have previously existed in the Jev community. For example, `gholtzap/jev-codex-model-and-effort-router` uses Jev to select models and inference tiers for Codex, then locks the entire thread to reuse caching; `Jev-Auto-Router` attempts to reselect models per call. OpenRouter has now integrated this approach directly into its official routing service.