MarkTechPost ★ 95 4 min

Liquid AI Releases d1: A Decision Model That Returns Calibrated Probabilities With Zero Output Tokens

Agentic AIAI InfrastructureLanguage ModelLarge Language ModelMachine Learning

🔗 https://www.marktechpost.com/2026/09/29/liquid-ai-releases-d1-a-decision-model-that-returns-calibrated-probabilities-with-zero-output-tokens/

📌 Liquid AI發布d1:每次呼叫輸出token數永遠是0

TL;DR:d1是不寫文字的決策模型,回傳固定選項的校準機率,API已可用。

當多數團隊還在用完整的LLM做分類、路由、審核這類「選答案」任務時,Liquid AI選擇反其道而行,直接砍掉輸出token,讓模型只回傳機率。

🤔 背景:這解決什麼問題

Liquid AI推出的d1,鎖定的正是許多團隊目前仍丟給一般LLM處理的工作:分類、工單路由、評分、內容審核、重排序,以及LLM-as-judge這類判斷型任務。官方定義很直接:決策模型會評估一個情境,並從你事先定義好的選項中回傳一個有型別的答案,它不寫文字,每一次回應中usage.output_tokens都是0。Liquid的遷移指南給了一個簡單原則:如果答案是N個已知選項之一,就用決策模型;如果模型必須組出一段全新的字串,就繼續用LLM。

🧩 方法或架構:一次呼叫三種提問

d1目前以Liquid API的方式提供服務,模型名稱是d1:free,可以直接串接使用。根據Liquid的模型庫說明,它是「僅限API」且「不可訓練」,因此沒有GGUF、MLX或ONNX格式的權重可以自行部署。每個請求包含三個部分:模型、state(可以是純文字或JSON物件),以及questions。一次請求裡可以混用三種提問類型,模型會在同一次往返中針對同一個state評估所有問題。呼叫端點是POST https://api.liquid.ai/decisions/v1/systemone,API金鑰從console.liquid.ai取得,開頭是liquid_。官方提供Python的typesafe-sdk與TypeScript的@typesafe-ai/sdk兩種客戶端,皆由TypeSafe AI提供。

📊 數據或結果:機率讓門檻值變得可用

Liquid官方的內容審核範例:機率超過0.8就封鎖,低於0.2就放行,中間地帶交由人工審查。路由範例則是當路由器的信心分數低於0.5,系統就會退回到能力最強的模型層級處理。Liquid也表示,同一筆輸入重複評估時結果更一致,能減少判定結果忽上忽下的情況。

💡 深入分析:道路決策Demo與狀態設計的教訓

Liquid提供的road-decider cookbook是一款像素風的生存賽車遊戲:d1用一個Choice問題,在每個決策時間點選擇往左、置中或往右,依遊戲速度大約每秒判斷2到5次。這個範例用純JavaScript寫成、跑在Node.js 18以上,並透過Vite proxy把API金鑰留在伺服器端,不外洩到前端;其中還有個「Jev vs d1」模式,讓d1透過OpenRouter和TypeSafe的typesafe/jev-1.13模型互相競速。從這個demo得到的教訓是:state的設計方式很關鍵,官方發現把賽道拆成「每個車道的摘要+到第一個障礙物的距離」,會比丟一整張原始賽道網格資訊,讓模型做出更有信心的決策。

⚠️ 限制

d1完全走API-only路線,沒有開放權重,無法自行部署或微調。官方也明確劃出界線:摘要、草擬文案、多輪對話、程式碼生成、複雜多步驟推理,這些仍然要交給一般LLM,決策模型不是萬用替代品。

🎯 實務啟示

如果你手上的任務本質是「從已知選項中選一個」,例如工單分類、審核分級、路由決策,d1這類決策模型能省下生成token的成本與延遲,機率輸出也讓你可以設計清楚的門檻策略,例如高分自動放行、低分自動擋、中間交給人工。這個賽道目前正快速形成小型但活躍的競爭格局,Liquid的d1與TypeSafe的Jev已經被直接放在一起比較,值得持續關注這類「零輸出token」模型的定價與能力邊界。

🔗 來源

#LiquidAI #DecisionModels #LLM #API #MachineLearning #Classification #ModelRouting #ContentModeration #AIInfrastructure #TypeSafeAI

原始資料 MarkTechPost · 收集於 2026-09-30
來源原標題
Liquid AI Releases d1: A Decision Model That Returns Calibrated Probabilities With Zero Output Tokens
作者
Asif Razzaq
原始標籤
Agentic AI · AI Infrastructure · AI Shorts · Applications · Artificial Intelligence · Editors Pick · Language Model · Large Language Model · Machine Learning · New Releases · Tech News · Technology
原始連結
https://www.marktechpost.com/2026/09/29/liquid-ai-releases-d1-a-decision-model-that-returns-calibrated-probabilities-with-zero-output-tokens/

摘要原文

Liquid AI has released d1 , a decision model built for structured choices instead of text generation. You give it context and a set of typed questions. It returns calibrated probabilities across a fixed set of outcomes in a single call, with zero generated tokens. The target is the work many teams still send to general LLMs: classification, ticket routing, scoring, moderation, reranking and LLM-as-judge checks. Is it deployable? Yes, today, as a hosted API. d1 runs on the Liquid API under the model name d1:free . Liquid’s model library lists it as API only and not trainable, so there are no GGUF, MLX or ONNX weights to self-host. A decision model evaluates a situation and returns a typed answer from options you define before the call. It does not write text. In every response, usage.output_tokens is 0. Liquid AI’s migration guide gives a simple rule: if the answer is one of N known options, use a decision model. If the model must compose a new string, keep your LLM. You can mix all 3 types in one request. The model evaluates every question against the same state in one round trip. Each request has 3 parts: the model, the state (plain text or a JSON object) and the questions. Calls go to POST https://api.liquid.ai/decisions/v1/systemone . Keys come from console.liquid.ai and start with liquid_ . The clients are TypeSafe AI’s typesafe-sdk for Python and @typesafe-ai/sdk for TypeScript. The migration guide lists the concrete differences against an LLM with structured output: Probabilities make thresholds practical. Liquid’s moderation example blocks above 0.8, allows below 0.2 and sends the middle band to human review. Its routing example falls back to the most capable model tier when router confidence drops below 0.5. Liquid also says repeated evaluations of the same input are more consistent, which reduces verdict flips. Keep an LLM for summarization, drafting, multi-turn chat, code generation and complex multi-step reasoning. Liquid’s road-decider cookbook is a pixel-art survival racer. d1 uses a Choice question to pick left, center or right on every decision tick, about 2 to 5 times per second depending on game speed. The app is vanilla JavaScript on Node.js 18+, with a Vite proxy that keeps the API key server-side. A “Jev vs d1” mode races d1 against TypeSafe’s typesafe/jev-1.13 through OpenRouter. The most useful lesson is about state design. Per-lane summaries with distance to the first obstacle produced more confident decisions than a raw grid of the road. d1 enters a small but fast-moving category of non-generative decision models. Here is how it compares on published features. Data checked September 29, 2026 against each vendor’s primary page. Check out the Decision Models docs , the Migration Guide and the Road Decider demo . All credit goes to the researcher of this project. Also, feel free to follow us on Twitter and don’t forget to join our 150k+ML SubReddit and Subscribe to our Newsletter . Wait! are you on telegram? now you can join us on telegram as well. Need to partner with us for promoting your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar etc.? Connect with us The post Liquid AI Releases d1: A Decision Model That Returns Calibrated Probabilities With Zero Output Tokens appeared first on MarkTechPost .

由 claude-code/sonnet 自動生成