TypeSafe
Jev 1.14
最大コンテキスト
32K
最大出力
N/A
リリース日
N/A
jev-latestJev Latest は TypeSafe の Jev 意思決定モデルの最新リリースを自動追跡します。高速な分類、ルーティング、スコアリング向けに設計され、テキストとアプリケーション状態を評価して、構造化された選択肢、確率、スコアを返します。Decision API が必要で、標準の Chat Completions には対応していません。
Context Window
32K tokens
Release Date
2026年9月18日
Modalities
| 入力価格 | 出力価格 |
|---|---|
| $0.042/M | $0/M |
Reasoning
Tool calling
Temperature parameter
Attachments
Knowledge Base
Endpoint Protocols
アプリケーションのロジックに、構造化された判断、独立した質問の評価、確率の指標を提供します。
Choiceは定義済みの選択肢を選び、Noulは肯定の確率を返し、Scoreは順序付きの尺度で評価します。構造化された出力をコードから直接利用できます。
Jev LatestのSystem One設計は、同じ状態に対する型付きの質問を独立かつ並列に評価します。推論過程のテキストを生成せず、コードで回答を組み合わせて処理を構築できます。
ChoiceとScoreは確率分布と確信度を返します。振り分けやレビューの閾値に利用できますが、確信度は判断の正しさを保証しません。
Jev APIによる分類、採点、コンテンツ確認、エージェントの振り分けの実用的な処理例です。
Jev Latestでテキスト分類、意図検出、タグ付けを行います。定義済みの分類やラベルを付けて、メッセージやレコードを適切な処理に振り分けます。
問い合わせの振り分け、感情分析、緊急度の評価を組み合わせます。定義した分類と尺度で優先順位を付け、人による確認が必要な依頼を特定します。
テキストと参考資料に、コンテンツ確認の規則やLLM回答の検証基準を適用します。違反の可能性や根拠のない回答を検出し、不確かな結果は確認へ回します。
明示した方針に基づき、エージェントの振り分け、ツール呼び出しの判定、権限チェックを支援します。条件に応じてLLMへ依頼を引き継ぐ構成を作り、実行、権限、フォールバックはコードで制御します。
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."
}
}'TokenHubでJev Latestを使う前に、バージョン選択、API連携、確信度、料金、モデルの制限を確認できます。
Jev LatestはTypeSafeのJev System One判断モデルの最新リリースを指す別名です。TokenHubの構造化判断ドキュメントにはAPIの要求・応答とPython・TypeScript SDKの例があります:https://tokenhub.com/docs/ai-model/system-one/create-system-one-decision。TokenHubはAPIへのアクセスを提供します。SDKの導入はモデルの重みの取得やオープンソースのライセンス取得を意味しません。
Jev Latestは新しいリリースに追従し、Jev 1.13は特定のバージョンを選びます。更新を利用するならLatest、評価や確信度の閾値を既知のモデルに合わせたいなら固定バージョンを選びます。コンテキストとリクエストの上限はTokenHubの利用経路に表示される値を確認し、更新時に再確認してください。
TokenHubのAPIキーを作成し、このページのモデルIDを選びます。TokenHubのAPIルートにある/v1/systemoneへmodel、state、questionsをPOSTし、answersから対応する結果を取得します。Pythonのrequests、TypeScriptのfetch、またはTokenHubの認証情報とAPIルートを設定したtypesafe_sdkや@typesafe-ai/sdkを使えます。例はこちら:https://tokenhub.com/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/docs/ai-model/system-one/create-system-one-decision。
TokenHubの現在の入力・出力料金を、同じ通貨の100万トークン当たりの単価で使います。API費用=(課金対象の入力トークン数×入力単価+出力トークン数×出力単価)÷1,000,000です。出力単価がゼロなら入力分のみです。Latest更新後は使用量と単価を確認してください。
ChoiceとScoreの確率は選択肢やレベルの分布を表し、確信度はその分布を要約します。Noulは肯定の確率のみを返します。確信度は正しさの保証ではありません。代表的な業務データで判断の閾値を調整してください。
ClaudeなどのLLMはテキストやスキーマに沿ったJSONを生成します。Jev Latestは定義済みのChoice、Noul、Score質問を評価し、説明を生成せず判断を直接返します。分類、振り分け、絞った確認にはJev、会話、文章作成、コード生成、長い推論には生成型LLMを選びます。計算や多段階の問題はJevに適さず、出力の型が正しくても判断が正しいとは限りません。
1つの API キーで 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
原文を見る