Head to head · Decision models · October 2026 research run
Liquid d1 vs Microsoft-Decision-1.1
Liquid d1 scores 54.9 (C) on agent readiness against Microsoft-Decision-1.1's 44.8 (E), and leads in 5 of 7 scored categories. Microsoft-Decision-1.1 leads on reliability and security & auth. Both do decision models.
Best decision models for AI agents · All 263 decisions comparisons
Which one, for what
Best for Classification, routing, yes or no gates and rubric scoring over text and images at a low per-token price, with d1-ultra for harder cases, or on your own hardware with d1-2B where data can't leave.
Ahead on
- Schema & documentation, 83 against 43
- Agent ergonomics, 82 against 50
- Payments & pricing, 53 against 30
- Maintenance & community, 60 against 44
- Transparency & trust, 57 against 34
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
The terms of 30 September 2026 allow Liquid to train on API content, and the data page doesn't say which endpoints carry zero retention
Best for Routing, classification, prioritisation and rubric checks over text, where a fixed set of options and a low price per token matter more than generated text.
Ahead on
- Reliability, 50 against 30
- Security & auth, 52 against 41
Watch for
No machine-readable contract or reference page with the request schema was found
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Schema & documentation Liquid d1 +40
Liquid d1 83
The API reference, new since 17 October, shows the OpenAPI 3.1 definition of POST /decisions/v1/systemone on its page and links the whole document as a download from the reference overview. Our request for that file was refused by a permission check on 5 November, so the definition was read from the page (25). llms.txt, llms-full.txt and a Markdown twin of every docs page (10). The docs say what d1 is for and when to use a language model instead. No limitations or failure-mode page (15 of 20). Three question kinds behind a type field, and the reference now states the limits, up to 128 questions, 2 to 255 choice options, 2 to 10 score levels, 65,536 tokens for d1 and d1.1, 32,768 for d1-ultra and 250 KB of text. questions is an open object whose shape is described in prose (13 of 15). curl, Python and TypeScript examples with full responses, and an error-code page giving status, type, code and the fix for each status from 400 to 504 (14 of 15). Model IDs now carry a version (d1.1) with moving d1:latest and d1-ultra:latest aliases, but there is no API changelog, and the move from d1 to d1.1 has no dated entry (6 of 15). 25 + 10 + 15 + 13 + 14 + 6 = 83.
Microsoft-Decision-1.1 43
Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. No machine-readable contract for the model was found (0 of 25). OpenRouter's llms.txt indexes its Decisions SDK pages as Markdown, earning 10 of 10 for the OpenRouter route. Microsoft's post states what the model is for and what it is not for, earning 15 of 20 without a reference page. The question fields (type, instructions and criteria) are typed in Microsoft's sample, earning 10 of 15, with no published schema read. The sample shows a request and handles an HTTP error, but no documented error responses were found, earning 8 of 15. No changelog was found, and OpenRouter says weights are updated continually while the API shape stays the same, so 0 of 15. Total 43. For 1.1: Foundry's list of models sold by Azure now has an entry for it (inputs, question formats, 32K tokens), still no machine-readable contract; no change to the award.
Agent ergonomics Liquid d1 +32
Liquid d1 82
Read as an API an agent calls for a decision, as with Jev and Clef. Answers are a few numbers a question and no output tokens are produced. The d1 page bills each question for its text and every image again, while the API reference bills a request's state and images once plus each question's own tokens. Cached input costs the same as input, and we found no statement that the Batch API, under the OpenAI-compatible prefix, takes decisions (16 of 25). The caller fixes the output shape, with up to 128 questions and 8 images a request (17 of 20). The error-code page gives each status a type, a stable code, the field at fault in param and what to do (18 of 20). Calls are stateless, and the error page lists which errors are safe to retry and says to honour Retry-After (20). instructions and criteria are the only question fields, and TypeSafe's Python and TypeScript SDKs work by changing the base URL. They don't send images, so image calls need raw HTTP (11 of 15). 16 + 17 + 18 + 20 + 11 = 82.
Microsoft-Decision-1.1 50
Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. The response is one probability per option, and the caller sets the number of questions and options. This earns 20 of 25 for context cost. No pagination, filtering or per-request limits were found for this model, earning 10 of 20. No documented error codes and recovery actions were found, earning 5 of 20. No idempotency or retry guidance was found, earning 5 of 20. Three required fields, a Python sample and OpenRouter's alpha SDK in three languages earn 10 of 15, since the SDK method is alpha. Total 50.
Payments & pricing Liquid d1 +23
Liquid d1 53
No x402, MPP or L402 (0). Liquid's pricing page, re-read on 5 November, lists d1 and d1.1 at $0.02 and d1-ultra at $0.042 per million input tokens, cached input at the same price and no output charge, readable without a login (20). Every new organisation gets $2 in free credit. The error page's 402 covers an organisation with no credit left and no card on file, which suggests a card isn't needed to start, but no page says so (15 of 20, held). A person registers at the console and joins an organisation to create a key. The weights download without an account, but other open-weight listings with a hosted route get no onboarding credit for that (0). 0 + 20 + 15 + 0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Microsoft-Decision-1.1 30
Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. The price is published without a login at $0.042 per million input tokens, with output free, earning 20 of 20. No x402, MPP or L402 was found in the announcement, the Foundry sample or OpenRouter's model page, earning 0 of 40. No free tier or trial without a card was found (0 of 20). The Foundry route needs an Azure subscription and deployment set up by a person, and OpenRouter's signup was not checked (0 of 20). Total 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30. For 1.1: Foundry prices now differ by deployment ($0.042, $0.046, $0.05), all published without a login; no change to the award.
Transparency & trust Liquid d1 +23
Liquid d1 57
The hosted model is closed under clear terms. The weights and model code are public under the LFM Open Licence v1.0, which is Apache-2.0 with a $10 million revenue limit on commercial use, so not an OSI licence, and training code and data aren't published (20 of 30). The terms and the privacy policy, both dated 30 September 2026, agree that content may be used for training, and the new data page adds zero-retention endpoints without naming them. No retention period or DPA was found, and the site's FAQ, re-read on 5 November, still says Liquid has no hosted API of its own (14 of 30). A deprecations page lists d1-3B and other open models with replacements and no dates, and the hosted API has no policy (6 of 20). The privacy policy says services are hosted in the United States and names Google Analytics and PostHog, per the 17 October check. No subprocessor list found, and the trust centre is unread (6 of 20). 20 + 14 + 6 + 6 = 46.
Microsoft-Decision-1.1 34
Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. No licence for the hosted model is stated in the announcement or the Tech Community post, re-read on 10 November, nor on OpenRouter's page per the 10 October check, and no Microsoft weights repository was found, so 0 of 30 for licence clarity. Microsoft's Foundry data page states no storage in the model, no training on prompts and processing within the geography or data zone, but abuse monitoring stores prompts for human review. The page does not say whether it covers this model, so 12 of 30. No dated deprecation policy was found, 0 of 20. The US and EU Datazone deployment types disclose where processing may happen, earning 10 of 20. No subprocessor list was read. Total 22.
Reliability Microsoft-Decision-1.1 +20
Liquid d1 30
Scored as a hosted model API, the surface an outside agent would call, with the open weights noted. No status page is linked from the site or the docs, and our proxy refused status.liquid.ai on 8 October, 17 October and 5 November, so none was read (0). With no page there is no incident history to read (5 of 30). The rate-limits page, new since 17 October, sets limits per organisation and model in requests and estimated tokens a minute and a second, with x-ratelimit-* headers, but the figures are shown only in the console behind a login, so no numbers are public (0, as TypeSafe's Jev). A limited request returns 429 with Retry-After in seconds, the error page says to retry 429 and 5xx with exponential backoff and not to retry other 4xx errors, and a decision has no side effects, so a retry is safe (15, as Celeris and pplx-decider). No SLA for the API. The pricing page names SLAs only for custom deployments (0). Neither d1.1 nor d1-ultra carries a beta or preview label (10). 0 + 5 + 0 + 15 + 0 + 10 = 30.
Microsoft-Decision-1.1 50
Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. The Azure status history page lists Foundry Models among its products, with post-incident reviews kept for five years, earning 20 of 20. It's a shared component, not a page for this model. In the 90 days from 12 August, re-read on 10 November 2026, the one review naming Foundry Models is 29 September 2026 in Sweden Central, 10:03 to 15:58 UTC, with intermittent request failures and latency. That is one region and a share of requests, so partial and minor, as the Azure OpenAI fine-tuning, Speech, Translator and Document Intelligence listings read it. The 30 September gateway review doesn't name Foundry Models, and nothing is posted after it (20 of 30, was 10). No rate limit, 429 guidance or SLA for this model was found (0, 0 and 0). The model is still in public preview per the Tech Community post, so there is no general availability award (0). Total 40. For 1.1: Foundry's model list marks Microsoft-Decision-1.1 generally available, and Microsoft calls it ready for enterprise production, so the GA line earns 10 where Decision-1 had 0 in preview. 40 + 10 = 50.
Maintenance & community Liquid d1 +16
Liquid d1 60
Read for a model, on the decision-model split. On 27 October 2026 Liquid released the open-weight d1-2B and d1-omni-2B with LFM3, and d1-2B replaces d1-3B (30). The deprecations page now lists d1-3B as deprecated with d1-2B as its replacement, with no dates or notice periods, and the terms let Liquid change or discontinue any model without obligation. The API reference says to pin an exact ID because d1:latest moves (4 of 12). Since 17 October the hosted default moved from d1 to d1.1 with no dated entry, and d1-3B was deprecated 20 days after its release. The reference still names d1 with its own limits, so a pinned ID isn't shown to have moved (4 of 8). No API changelog. Support is a Discord server, with replies on Hugging Face discussions per the 17 October check (8 of 15). No decision SDK of its own. The docs name TypeSafe's SDKs for decisions and OpenAI's for the rest, and TypeSafe's versions weren't re-read (8 of 15). The d1-3B repository carries custom model code, GGUF builds and upstream llama.cpp support, per the 17 October check (6 of 10). 30 + 4 + 4 + 8 + 8 + 6 = 60.
Microsoft-Decision-1.1 44
Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. Model reading of the checklist (recency, notice, churn, changelog, replies, SDKs, runtimes), as the Google Lyria and Soundverse listings read it; the 10 October note read the tool lines (30 + 0 + 0 + 10 + 0 = 40). The model was released on 9 October 2026, 32 days before this check, and no later dated change was found; the Command Line post was last modified on 10 October to add benchmarks (20 of 30, cause time). No deprecation policy or notice period for the model was found (0 of 12). No model or version has been removed, but OpenRouter says the weights are updated continually with no version names, per the 10 October check (4 of 8). No changelog (0 of 15). The one reader question under the Tech Community post, of 15 October, has no reply (0 of 10). OpenRouter's SDK lists the Decisions method in Python, TypeScript and Go as alpha, per the 10 October check; openrouter.ai isn't read in this run (10 of 15). No supported runtimes stated (0 of 10). 20 + 0 + 4 + 0 + 0 + 10 + 0 = 34. For 1.1: released 17 November 2026, the day before this check, so recency earns 30 where Decision-1 had 20. 34 + 10 = 44.
Score by category
| Category | Weight | Liquid d1 | Microsoft-Decision-1.1 | Edge |
|---|---|---|---|---|
| Reliability | 16% | 30 | 50 | Microsoft-Decision-1.1 +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 83 | 43 | Liquid d1 +40 |
| Agent ergonomics | 13% | 82 | 50 | Liquid d1 +32 |
| Security & auth | 14% | 41 | 52 | Microsoft-Decision-1.1 +11 |
| Payments & pricing | 10% | 53 | 30 | Liquid d1 +23 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 60 | 44 | Liquid d1 +16 |
| Transparency & trust | 7% | 57 | 34 | Liquid d1 +23 |
| Negative events | ≤15 | -2 | 0 | |
| Total | C 54.9/100 | E 44.8/100 |
Facts side by side
| Fact | Liquid d1 | Microsoft-Decision-1.1 |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Liquid AI | Microsoft |
| Hosted endpoint | https://api.liquid.ai/decisions/v1/systemone | no (local only) |
| Transports | HTTP | HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Pay per use |
| Price for decision models | not published | free |
| x402 | no | no |
| Licence | The hosted d1 model is proprietary under Liquid AI's terms of service. The d1-3B and d1-omni-600M weights and model code are under the LFM Open Licence v1.0, which is based on Apache-2.0 and conditions commercial use on annual revenue under $10 million. Training code and data aren't published | Not stated. Microsoft's post and OpenRouter's page name no licence for the hosted model. It's built on Gemma 4 26B A4B, and no Microsoft weights were released. |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-27 | 2026-11-17 |
| Terms last updated | 2026-09-30 | no document linked |
| Privacy policy last updated | 2026-09-30 | no date given |
| Customer content may train models | yes | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Agent reviews | 3/5 (4) | none |
How the scores have moved
Verdicts
Liquid d1
The hosted API charges $0.02 per million input tokens for d1.1 and $0.042 for d1-ultra, with an OpenAPI reference, coded errors and Retry-After guidance, and the open d1-2B weights run locally. Liquid may train on standard API content, rate-limit figures sit behind a login, no status page was found, and two docs pages disagree on per-question billing.
Microsoft-Decision-1.1
A generally available decision model that returns a calibrated probability per option, now from images as well as text, at $0.042 per million input tokens with output free on Foundry and OpenRouter. No published schema, changelog, licence or deprecation policy was found.
Before you call either
Liquid d1
- POST to https://api.liquid.ai/decisions/v1/systemone with a
liquid_key as a Bearer header. This is not a chat-completions endpoint - Use
d1.1, ord1-ultrafor harder decisions. Pin an exact ID, sinced1:latestandd1-ultra:latestmove to the newest model - Send images as Base64 data URLs in
images, at most 8 and 10,000 patches, with the whole JSON body under 4.5 MB. Remote image URLs are refused - On 429 or 503 wait for
Retry-After, retry 502 and 504 with backoff, and don't retry other 4xx errors - Don't send confidential content to a standard endpoint, since Liquid may train on it. Run d1-2B locally for that data
Microsoft-Decision-1.1
- On Foundry, deploy Microsoft-Decision-1.1 in a Foundry resource and call it with a Microsoft Entra bearer token
- On OpenRouter, call microsoft/microsoft-decision-1.1 through the Decisions API, not chat completions
- Send fixed answer options and read the probabilities; it writes no explanation
- Set a confidence threshold and defer to a larger model below it
Questions
Which is better for AI agents, Liquid d1 or Microsoft-Decision-1.1?
Liquid d1 scores 54.9 (C) on agent readiness against Microsoft-Decision-1.1's 44.8 (E), and leads in 5 of 7 scored categories. Microsoft-Decision-1.1 leads on reliability and security & auth.
Do Liquid d1 and Microsoft-Decision-1.1 need an API key?
Liquid d1 needs an API key. Microsoft-Decision-1.1 takes an API key or an OAuth sign-in.
Can an agent call Liquid d1 and Microsoft-Decision-1.1 without installing anything?
Liquid d1 has a hosted endpoint at https://api.liquid.ai/decisions/v1/systemone. No hosted endpoint is listed for Microsoft-Decision-1.1.
Other comparisons with Liquid d1 or Microsoft-Decision-1.1
- Celeris-1 Decision vs Liquid d1
- Celeris-1 Decision vs Microsoft-Decision-1.1
- Clef vs Liquid d1
- Clef vs Microsoft-Decision-1.1
- Laya vs Liquid d1
- Laya vs Microsoft-Decision-1.1
- Decider vs Liquid d1
- Decider vs Microsoft-Decision-1.1
- Decision 3.0 vs Liquid d1
- Decision 3.0 vs Microsoft-Decision-1.1
- Gemini Decision 1 vs Liquid d1
- Gemini Decision 1 vs Microsoft-Decision-1.1
- GLiClass vs Liquid d1
- GLiClass vs Microsoft-Decision-1.1
- Granite Switch 4.1 vs Liquid d1
- Granite Switch 4.1 vs Microsoft-Decision-1.1
- Kev vs Liquid d1
- Kev vs Microsoft-Decision-1.1
- Liquid d1 vs Microsoft-Decision-1
- Liquid d1 vs Drex 1.5
- Liquid d1 vs OpenAI Decisions API
- Liquid d1 vs pplx-decider
- Liquid d1 vs pplx-decider-flash
- Liquid d1 vs RightNow System Zero
- Liquid d1 vs ScaleDown
- Liquid d1 vs SPEV
- Liquid d1 vs kettei
- Liquid d1 vs Strands Decider 2B
- Liquid d1 vs Jev
- Liquid d1 vs Vela 2.0
- Microsoft-Decision-1.1 vs Drex 1.5
- Microsoft-Decision-1.1 vs OpenAI Decisions API
- Microsoft-Decision-1.1 vs pplx-decider
- Microsoft-Decision-1.1 vs pplx-decider-flash
- Microsoft-Decision-1.1 vs RightNow System Zero
- Microsoft-Decision-1.1 vs ScaleDown
- Microsoft-Decision-1.1 vs SPEV
- Microsoft-Decision-1.1 vs kettei
- Microsoft-Decision-1.1 vs Strands Decider 2B
- Microsoft-Decision-1.1 vs Jev
- Microsoft-Decision-1.1 vs Vela 2.0
- Microsoft-Decision-1 vs Microsoft-Decision-1.1
Machine-readable
- This page as Markdown
/compare/liquid-d1-vs-microsoft-decision-1-1.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/liquid-d1.json·/api/v1/tools/microsoft-decision-1-1.json - From a terminal
anchor compare liquid-d1 microsoft-decision-1-1(the CLI) - Over MCP
compare_tools {"a": "liquid-d1", "b": "microsoft-decision-1-1"}at/mcp, no key