Loki Jev Companion
The Loki agent offers Jev as an optional typed-decision companion and session model router.
Added to Jevfast
How it uses Jev
Loki exposes Jev through an optional `typesafe_ask` tool for Choice, Score, and Noul judgments over supplied state. Its optional autorouter can classify the first task and select a model from the currently selected gateway, keeping that route for the session.
What Jev decides
Choose a model for the agent taskExample answers · not a recorded Jev response · Source ↗
Question 1 · route model
YOUR APP
INSTRUCTION
Choose exactly one model from the provided criteria for this agent task. The model must be sufficiently capable for the task, including tools, reasoning, context, or vision when those are relevant. Prefer lower cost when capability is sufficient; pay more only for material task needs.
STATE
Tested routing example: task “write a regex”, gateway OpenRouter, current model vendor/current, balanced cost preference. Two same-gateway candidates are offered: vendor/current (tools, 128,000 context, $4/M input and output) and vendor/cheap (tools, 128,000 context, $0.2/M input and output).
JEV · CHOICE
- vendor/current
- vendor/cheap
App workflow
- Configure optional Jev
Configure the Jev companion and API key through Loki setup or settings.
- Enable tool or routing
Enable the tool for the session or opt into the autorouter.
- Submit typed judgments
Submit structured state and typed questions through `typesafe_ask`; route an initial task when autorouting is enabled.
- Return answers to the agent
Return structured answers to the agent and keep the selected route sticky for the session.
Why it is interesting
The optional tool accepts caller-supplied state and a list of typed questions, validates them, and returns structured System One results to Loki.