TypeSafe
Jev 1.14
最大上下文
32K
最大輸出
暫無
發布日期
暫無
jev-latestJev Latest 會自動追蹤 TypeSafe Jev 決策模型的最新版本。專為快速分類、路由與評分而設計,能評估文字與應用程式狀態,回傳結構化選擇、機率與分數。它需要 Decision API,不支援標準 Chat Completions。
上下文視窗
32K Token
發布日期
2026年9月18日
模態
| 輸入價格 | 輸出價格 |
|---|---|
| $0.042/M | $0/M |
推理
工具呼叫
Temperature 參數
附件
知識庫
Endpoint 協議
為應用程式邏輯提供結構化判斷、獨立問題評估與機率訊號。
Choice 選擇預先定義的選項,Noul 回傳肯定回答的機率,Score 評估有序等級。程式碼可直接使用這些結構化輸出。
Jev Latest 的 System One 設計針對相同狀態獨立、平行評估型別化問題,再由程式碼組合答案建立工作流程,無需產生推理過程文字。
Choice 和 Score 提供機率分布與信心度,可用於設定路由和審核門檻;高信心度並不保證決策正確。
使用 Jev API 建立文字分類、評分、內容審核和智慧代理路由工作流程。
使用 Jev Latest 進行文字分類、意圖辨識和文字標籤指派,將訊息與記錄歸入預先定義的類別並轉入對應工作流程。
結合客服案件分流、情感分析和緊急程度評分,使用預先定義的類別與等級安排案件優先順序,辨識需要人工審核的請求。
根據明確規則進行內容審核,並結合參考資料驗證大模型答案,標記可能違規或缺乏依據的答案,將不確定結果轉交審核。
依據明確策略協助智慧代理路由、工具呼叫審核和權限判斷,並建立依條件轉交請求的大模型串接流程;實際執行、權限控制與備援行為由應用程式碼負責。
curl 'https://us-api.tokenhub.com/v1/systemone' \
-X 'POST' \
-H "Authorization: Bearer $TOKENHUB_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "jev-latest",
"questions": {
"department": {
"criteria": {
"billing": "Charges and refunds",
"technical": "Product defects"
},
"instructions": "Which team should handle this ticket?",
"type": "choice"
},
"needs_refund": {
"instructions": "Does the customer explicitly request a refund?",
"type": "noul"
},
"urgency": {
"criteria": [
"Routine",
"Needs attention",
"Critical"
],
"instructions": "How urgent is this ticket?",
"type": "score"
}
},
"state": {
"ticket": "I was charged twice. Please refund the duplicate charge."
}
}'了解 Jev Latest 的版本選擇、API 串接、信心度、價格與能力限制。
Jev Latest 是 TypeSafe 的 Jev System One 決策模型最新版本別名。TokenHub 結構化決策文件提供 API 請求、回應及 Python、TypeScript SDK 範例:https://tokenhub.com/zh/docs/ai-model/system-one/create-system-one-decision。TokenHub 提供 API 存取;安裝 SDK 不等於下載模型權重,也不代表取得模型開源授權。
Jev Latest 跟隨新版本,Jev 1.13 指定固定版本。希望取得更新可選 Latest;評估結果和信心度門檻需要與已知模型對應時,應固定版本。上下文長度和請求限制以 TokenHub 目前渠道顯示的設定為準,Latest 更新後應重新確認。
建立 TokenHub API 金鑰,選擇本頁顯示的模型 ID,向 TokenHub API 根位址下的 /v1/systemone 提交 model、state、questions,再從 answers 讀取對應結果。可使用 Python requests、TypeScript fetch,或將 typesafe_sdk、@typesafe-ai/sdk 設定為 TokenHub 的金鑰和 API 根位址。呼叫範例見 TokenHub API 文件:https://tokenhub.com/zh/docs/ai-model/system-one/create-system-one-decision。
Jev Latest 使用 TokenHub 的 /v1/systemone 結構化決策介面。如果 400 錯誤提示協定不相容,請檢查是否誤用了 chat/completions 請求。應提交 model、state 和非空 questions 物件,並檢查各問題的 type、instructions、criteria。請求格式以 TokenHub API 文件為準:https://tokenhub.com/zh/docs/ai-model/system-one/create-system-one-decision。
使用 TokenHub 目前輸入與輸出 Token 單價,統一幣別並依每百萬 Token 計算。API 費用=(計費輸入 Token 數×輸入單價+計費輸出 Token 數×輸出單價)÷1,000,000。輸出單價為零時,僅計算輸入部分。Latest 更新後應確認計費用量和目前費率。
Choice 和 Score 的機率表示選項或等級上的分布,信心度概括該分布;Noul 僅回傳肯定回答的機率。信心度不代表正確率保證,應使用具代表性的業務資料調整決策門檻。
Claude 等 LLM 產生文字,也可以依 Schema 產生 JSON 結構化輸出。Jev Latest 評估預先定義的 Choice、Noul、Score 問題,直接回傳決策,不產生解釋。分類、路由和聚焦檢查可選 Jev;對話、寫作、程式碼生成和長鏈推理應選生成式 LLM。算術與多步任務不是 Jev 的優勢,型別有效也不保證決策正確。
透過一個 API Key 接入 Jev Latest 與更多 AI 模型。
Jev Latest 媒體與示範
精選 Jev Latest 所屬 Jev 系列的公告、教學與社群實驗;這些內容不代表目前 Latest 版本的效能評測。
X (Twitter)
Jev 系列發布公告
Diogo Almeida ·
After co-inventing ChatGPT, I kept asking myself: why have superhuman chat models not led to AGI? I’ve spent the last 2 years in stealth building a new way to train models (RLCD), and a new type of frontier AI model that we are releasing today: Jev • 20-200x faster • 40-400x https://t.co/JSybNG2BKJ
https://pbs.twimg.com/amplify_video_thumb/2099925575637057536/img/l4J_ZhkaxAe8FJXv.jpg查看原文Jev 系列公開存取公告
TypeSafe AI ·
Jev is now available to everyone. No waitlist. Start using it here: https://console.typesafe.ai/
查看原文Vercel 分享 Jev 系列採用情況
Vercel ·
Jev was adopted faster than any other model in AI Gateway history. In the first day, @typesafeai reached ~13% of teams, 2x the GPT-5.6 family and 6x Fable 5.1. https://t.co/kVEuLM1npu
https://pbs.twimg.com/media/HSiGtZba0AEezOP.jpg查看原文Reddit
Jev 系列智慧代理路由實驗
Tried TypeSafe's new "decision-only" model (Jev) as an agent router: 145-271ms end to end, curious if others have tested it
blackbarata ·
查看原文Jev 系列專案構想評分示範
I built a side project to test TypeSafe's Jev model with no generative LLM that scores your project idea
stemonte ·
查看原文Jev 系列社群評測討論
I benchmarked TypeSafe's JEV against LLMs, BERT and Laya.
LowExamination7016 ·
展開全文
Quick context on why I cared. We build voice AI for healthcare, and a big chunk of that work is classification: guardrails, call dispositions, evals. We keep looking for better ways to do all three. So when TypeSafe AI launched JEV last week, it piqued my interest. JEV is a "System One" model. It doesn't generate text. You send it your input plus typed questions, and it returns a probability for each option in a single pass. The pitch: LLM-level classification at a fraction of the latency and cost. No hallucination, no output parsing. Most of what I read about it was either the press release or someone's five-example demo. So I built a small benchmark and ran it properly.Out of curiosity I The setup The setup Six classifiers, three public datasets, 500 held-out examples each. Same label descriptions for every zero-shot model. The datasets, chosen to span difficulty: SST-2: movie sentiment, 2 labels AG News: news topic, 4 labels Banking77: customer intent in a banking app, 77 labels The contenders: JEV (typesafe/jev-1.13) via OpenRouter's Decisions API Claude Sonnet 5 and GPT-5-mini via OpenRouter, with JSON-schema constrained output Laya, Convai's new open-weights answer to JEV, running locally on my Mac DistilBERT fine-tuned per dataset on 10k training examples, also local BART-large-MNLI zero-shot, the classic no-training baseline I measured accuracy, calibration, p50/p95 latency with strictly sequential requests, throughput at fixed concurrency, and cost from the providers' own usage reports. Total API spend: under $10. The results r/AI_India - Accuracy on 500 held-out examples per dataset, p95 latency per request, and API cost. Same label descriptions for every zero-shot model. (https://preview.redd.it/i-benchmarked-typesafes-jev-against-llms-bert-and-laya-v0-cw1rsolk6zqh1.png?width=1488&format=png&auto=webp&s=fe7ef57a6a9e466fe96a7fc77f19da16a088866a) Accuracy on 500 held-out examples per dataset, p95 latency per request, and API cost. Same label descriptions for every zero-shot model. Cost per 1,000 classifications on Banking77: JEV $0.08, GPT-5-mini $0.38, Claude Sonnet 5 $6.43. The local models cost nothing per call. What I found 1. The accuracy claim holds. Across all three datasets, JEV landed within 0.2 to 4 points of Claude Sonnet 5. On the hardest dataset the gap was one point, inside the noise. It did that at a quarter of the p95 latency and at 50 to 77x lower cost. It beat GPT-5-mini outright on the two harder tasks. If you're picking between JEV and an LLM for a classification step, JEV wins on every axis except the last couple of accuracy points against the most expensive model. 2. It does not replace a fine-tuned classifier when you have labels. On Banking77, the cleanest dataset in the set, a fine-tuned DistilBERT beat JEV by 12 points, at 50x lower latency, for zero API cost. The price was 10 minutes of GPU time and 10k labelled examples. If you already have labelled data, a small fine-tuned encoder is still the strongest and cheapest option. JEV's value is when you have no labels, need to ship today, or your label set keeps changing. 3. Latency is flat, and higher than advertised. p50 was 380 ms and p95 around 670 ms, whether I gave it 2 labels or 77. That consistency is a real strength: cost scales with label count, latency doesn't. But TypeSafe quotes 70 to 100 ms, and through OpenRouter I got 4 to 5x that. If latency matters for you, test the direct API. 4. Label count is where the field separates. At 2 labels, all six models landed within 6 points of each other. At 77 labels, three tiers appeared: the fine-tuned model at 88, JEV and the LLMs at 74 to 77, and the small local zero-shot models collapsing to around 40. Holding 77 described options in one pass without degrading is what sets JEV apart from its open-weights lookalike. 5. Laya is a JEV substitute for small label sets only. On 2 and 4 labels it matched or beat JEV, ran in 50 to 70 ms locally, and cost nothing. On 77 labels it fell to 38%, with a calibration error of 0.51. Confidently wrong. For intent routing with under 10 intents, it deserves a serious look. For fine-grained classification, not yet. 6. Dataset quality shaped the ranking as much as model quality. AG News has famously inconsistent Business versus Sci/Tech labels. I found "Greenspan: debt, home prices not dangerous" labelled Sci/Tech and "Oracle quarterly net income rises" labelled Business. The three models that scored around 90 there almost certainly learned that noise, either from fine-tuning or from seeing the dataset in pretraining. JEV's 86 is close to the ceiling for a model that follows the label descriptions honestly. When I rewrote the descriptions to match the dataset's convention, JEV gained only 1.5 points, because the labels themselves don't follow a rule. 7. Calibration is the quiet differentiator. JEV's expected calibration error ranged from 0.03 to 0.13, on par with the fine-tuned model. That means you can threshold on confidence and route uncertain cases to a fallback. In production, that's the pattern that actually matters. The LLMs return a label and nothing else. Caveats, because they matter At n=500 the confidence interval on accuracy is roughly plus or minus 2.5 points, so several of these rankings are ties. The fine-tuned model saw 10k labelled examples that nothing else saw. SST-2 and AG News are old enough that the LLMs have almost certainly seen them in pretraining. Banking77 is the table I trust most. The benchmark code is a small Python project with pluggable datasets and classifiers. Happy to share if there's interest. DM me.
YouTube
Jev 系列入門設定教學
Jev Full Tutorial for Beginners: How to Use & Set up Jev (Typesafe)
Mikey No Code
查看原文Jev 系列社群案例與實作示範
爆火的 TypeSafe AI Jev 模型到底怎么玩?海量社区案例带你入门,附两个实战 Demo
NiceKate AI
查看原文Jev 系列與 System One 模型講解
Jev by TypeSafe AI | What is a System-1 Decision Model | CampusX
CampusX
查看原文