想给业务加自动判断能力的话看这篇,Jev 每百万 token 才 0.042 美元,还跟 GLiDE 等 5 家开源方案对比了。
#Jev
Stripe 收购 OpenRouter 后创始人首次上播客,讲了怎么用便宜的小模型逐条审查智能体的工具调用,还聊了该不该只依赖一家模型厂商。
Vercel 把 Jev 加进了 Python 版 AI SDK,一个 pip 就能装,官方还演示了实时语言检测和逐行写 Python 两个玩法。
Vercel 把 Jev 加进了 Python 版 AI SDK,他们拿「边打字边识别代码还是英语」和「一步步写 Python」两个实验做了演示,写 Python 项目的可以试试。
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.
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.
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.
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.
TypeSafe AI创始人谈Jev模型如何改变SaaS行业,与Claude Code和Codex对比,解释为什么SaaS公司将受益于AI自动化。
TypeSafe AI创始人Diogo Almeida批评行业过度承诺,其Jev模型专注于解决实际工作自动化问题,而非仅优化人类评估。
有人拿非生成式模型 Jev 1.13 和 GPT-6 Sol 在四个医疗基准上跑了对比,便宜快十倍但复杂病例上差 20 多个百分点,概率校准数据挺有意思。
Jev 不再只是个小模型,现在靠几百个实例投票帮你路由到 Opus 5.5 或 GPT-6 Astra,只用 40% 的钱拿到 99% 的跑分,省钱党快看。
TypeSafe AI 创始人在 a16z 节目里讲他们的新模型 Jev,思路和 Claude Code 不一样,输出是带置信度的选项,软件能直接用,聊自动化为什么一直没来。
有人把 GPT Researcher 里的 embeddings 换成 Jev,28 个任务测试下来相关内容多了 59%,盲测 15 比 3 获胜,成本没变,仓库开源可以自己试。
a16z 聊了个新模型 Jev,它不输出文本,而是给软件返回带置信度的选项,开发者能直接用来写自动化程序,跟 Claude Code 思路完全不同。
CodeRabbit 发了个叫 Jev 的东西,主打让 AI 决定哪些代码该写、哪些该删,比单纯自动补全更上一层。
有人用 Jev 半分钟读完 384 条新闻帮 15 个品牌找热点,比 Claude Opus 5 便宜约 390 倍,代码和 skills 都开源了,做 PR 的可以直接抄。
博主拿 Jev 和 Claude Opus 5 跑同一个新闻监控任务,一个 24.9 秒花 0.19 美元,一个只处理了 4 条花 0.77 美元,做品牌借势的可以看看。
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.
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.
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.
阿里云百炼上线了一个类似 Jev 的决策模型,分类筛选路由这些高频小判断扔给它就行,还能用 TypeSafe SDK 直接调,现在免费,做数据管道的可以去试试。
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.
Sinofsky 和 Levie 聊了个有意思的判断:让模型输出百分比再写 if 判断,比纯聊天接口靠谱多了,做开发的会很受启发。
OpenRouter 公布分类请求数据,Jev 拿下 27% 份额,把 DeepSeek V4 Flash 挤到第二,做分类任务可以关注下。
a16z 的 Martin Casado 聊了个有意思的观点:实验室都在造会聊天的存在,但软件其实需要一个从选项里挑答案的模型,Jev 就火了。
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.