#Jev

190 stories · 2 in 7 days · 54 in 30 days
Oct 4
Oct 3
Oct 2
How-toBuildersMulti-sourceSelected20:25
Agent model routing implementation

This approach demonstrates how significant cost savings can be achieved without compromising quality by intelligently routing tasks based on complexity. Developers can implement similar routing in their own systems using LangChain middleware, with the decision model Jev offering 50x faster classification. The method is particularly valuable for organizations managing large-scale AI operations where cost efficiency is critical.

Event
shao__meng@shao__meng7 sourcesSource
ModelsBuildersSelected73°03:44
Nace AI releases Drex 1.5 decision model

The 128k context window eliminates preprocessing for long documents, a significant advantage over previous decision models. Developers can now handle entire legal or video analysis tasks in a single pass, with a cost-effective option at $0.04 per 1M tokens. This model's top ranking on the Decision Index makes it a compelling alternative for businesses needing automated decision systems.

Ate-a-Pi@svpinoSource
Oct 1
ProductsBuildersSelected00:20
Jev Model for Search Decisions

Jev's decision-focused approach represents a shift from conversational AI to task-specific evaluation, potentially improving search accuracy and efficiency. Developers building search applications can leverage this pattern to optimize retrieval and ranking processes, with Milvus providing the vector search foundation. The tutorials offer practical implementation examples for various search optimization scenarios.

Milvus@milvusioSource
Sep 30
ModelsBuildersSelected73°11:20
Jev model benchmarks document tasks

Jev's superior performance across multiple metrics demonstrates a practical advancement in document processing efficiency. Developers working with document-heavy applications should consider implementing Jev for tasks requiring rapid decisions, as it offers a balanced solution that outperforms specialized alternatives in most scenarios.

Jerry Liu@jerryjliu0Source
Sep 29
Sep 28
How-toBuildersMulti-sourceSelected73°12:54
Jev and Laya agents battle in Chrome dinosaur game demo

The setup turns local-versus-API latency into a visible, playable comparison — a concrete way to feel how response delay shapes agent behaviour in real time. Builders interested in agent frameworks can clone the GitHub repo and adapt the same head-to-head harness to benchmark their own local models against hosted APIs. It also doubles as a showcase of Typesafe's Jev agent in an unusual adversarial role.

Event
AI Will@FinanceYF53 sourcesSource
PapersBuildersMulti-sourceSelected73°03:54
Jev flags alignment failures with one yes/no question

The cost gap, 62x cheaper than LLM judges, makes calibrated decision models a practical replacement for expensive evaluation pipelines. It also surfaces label errors in three existing benchmarks, which anyone relying on published alignment scores should note. Thresholds do not transfer between benchmarks, so teams adopting this should fit one on roughly 10 labelled items, which lifts median F1 from 0.706 to 0.793.

Event
elvis@omarsar03 sourcesSource
How-toBuildersSelected73°01:21
Jev tested as a fuzzy linter inside agent harnesses

The practical trick is the two-tier confidence output: routing medium-confidence flags back to the agent for verification doubles catch rate without materially inflating false positives. Developers building agent harnesses can offload cheap, deterministic checks like linting to small System One models instead of paying frontier-model prices for every call. DAIR.AI has published related resources at academy.dair.ai for those wanting to replicate the setup.

elvis@omarsar0Source
Sep 27
How-toBuildersMulti-sourceSelected72°05:48
Jev Router Experiment Shows Benchmark Limits in Agent Harness Testing

Independent harness tests like this show why vendor benchmark numbers often fail to predict task-level performance for your own workflows. Builders evaluating model routers or agent harnesses can take the concrete lesson that results depend heavily on the test setup, so replicating with your own workloads matters more than leaderboard rankings. The System One versus System Two framing offers a practical lens for deciding when to route cheaply and when to pay for heavier reasoning.

Event
elvis@omarsar011 sourcesSource
ProductsBuildersMulti-sourceSelected73°00:47
Jev Router brings System One model routing to OpenRouter calls

Routing model selection and reasoning effort to a lightweight System One model shifts cost and latency decisions from static configuration to per-request inference, a pattern that compounds savings on agentic workloads with many calls. Builders writing custom harnesses, especially with the Pi SDK, can plug the router into OpenRouter and reuse the shared implementation to benchmark it against their own fixed-model baseline before committing.

Event
elvis@omarsar04 sourcesSource