Head to head · Decision models · October 2026 research run

Decider vs Microsoft-Decision-1.1

Decider scores 72.8 (BB) on agent readiness against Microsoft-Decision-1.1's 44.8 (E), and leads in 6 of 7 scored categories. Microsoft-Decision-1.1 leads on security & auth. Both do decision models. Microsoft-Decision-1.1 is cheaper for decision models, $0 against $0 per 1M tokens.

Best decision models for AI agents · All 263 decisions comparisons

Which one, for what

Decider BB

Best for Local classification, routing, triage and checks where a team wants open weights in several sizes and a Jev-shaped route.

Ahead on

  • Reliability, 90 against 50
  • Schema & documentation, 78 against 43
  • Agent ergonomics, 80 against 50
  • Payments & pricing, 90 against 30
  • Maintenance & community, 76 against 44
  • Transparency & trust, 52 against 34

Also in its favour

  • Agent-ready, a grade of BB or better
  • No key needed to call it
  • Open source

Watch for

The local server has no authentication option. It binds to 127.0.0.1 since 1.7.1

Microsoft-Decision-1.1 E

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

  • Security & auth, 52 against 38

Also in its favour

  • Cheaper for decision models, $0 against $0 per 1M tokens

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.

Payments & pricing Decider +60

Decider 90

Free Apache-2.0 software with nothing to buy, so 20 + 20 + 20 for pricing, free use and no sign-up, by the self-hosted rule. No payment protocol (0). No hosted API was found, so there's no hosted option to grade. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

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.

Reliability Decider +40

Decider 90

Scored on the local-package checklist, since Decider is open weights the owner runs, as for Kev and Strands Decider. pip install decider-ai, at 1.10.0 of 20 October 2026 by the repository tag and pyproject, with Python 3.11 or later stated and extras for serving, GGUF and Apple silicon (20). Public CI on GitHub Actions runs the test files in two jobs, without torch and with CPU torch, and the five latest runs on main had passed on 8 October, per the 8 October check, not re-read on 1 November. No test loads model weights, and the 1.10.0 changelog reports 310 passing (22 of 25). 3 of 16 issues were open on 8 October, a feature request, a Windows on ARM report with fixes shipped in 1.7.1, and one unsolicited promotion, and reported crashes (#5, #8, #21) were fixed in a release within days, per the 8 October check, not re-read on 1 November (23 of 25). docs/CHANGELOG.md has a dated entry for every release and the tags run to v1.10.0. The 1.3.0 minor release changed what confidence means, called out with a migration note, and 1.10.0 adds image input behind a flag (12 of 15). 1.10.0, though 1.0.0 is from 22 September 2026 and 22 releases came in 29 days (13 of 15). 20+22+23+12+13 = 90.

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.

Schema & documentation Decider +35

Decider 78

Read for a model you serve yourself. The server is FastAPI with Pydantic request models, but questions is an untyped dict and state any JSON value, with the question rules enforced in decider/systemone.py. It follows TypeSafe's wire format and publishes no spec file of its own (15 of 25). No llms.txt. The README, five model cards and six docs pages are Markdown in the repository (5 of 10). The README says which model to use for which hardware and has a limits section with measured figures for each failure (19 of 20). Three question types, 2 to 255 options a choice and 2 to 10 levels a score, checked with a 422. State is free-form by design (11 of 15). Python examples with sample output and three example programs. docs/SERVING.md gives the 413, 503 and 422 bodies. No curl example and no error table (13 of 15). Release tags, Hub tags for earlier weights and a dated changelog (15).

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.

Maintenance & community Decider +32

Decider 76

Read as a model, for deprecation notice and model churn rather than release counts, on the lines used for Jev and the other decision models listed as models. decider-ai 1.10.0 with decider-2b v12, decider-4b v3, decider-12b-vision and decider-31b v2 on 20 October 2026 (30). No deprecation policy or notice period. Each new version replaces the weights on a repository's main branch on the day of its changelog entry, and earlier versions stay pinnable under Hub tags (v8, v10 and v11 of decider-2b, v1, v2 and v2.1 of decider-4b, v1 of decider-31b), with none removed so far (5 of 12). Frequent replacements on main, decider-4b four versions from 22 September to 20 October 2026 and decider-31b two in 13 days, each with a dated entry and measured results, while pinned versions keep working (4 of 8). 13 of 16 issues closed on 8 October, with fixes released within days of reports #5, #8, #18 and #21, and outside pull requests merged (#2, #11, #13), per the 8 October check, not re-read on 1 November. One maintainer wrote 103 of the 106 commits under two names (21 of 25). A Python package on PyPI from the author, and TypeSafe's SDKs for the HTTP route. Not an MCP server, so no registry entry applies (10 of 15). CI passed on main on 8 October. Dependencies have no upper bounds or lockfile, and the vLLM path needs its own environment pinned to vLLM 0.29.0 (6 of 10). 30+5+4+21+10+6 = 76.

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.

Agent ergonomics Decider +30

Decider 80

Read as an API an agent calls for a decision, as for the other decision models. Answers are a probability per option, and a long state is read once with each question scored from the shared prefix. Context is 32k tokens, and a state over 32,768 tokens is truncated without an error (19 of 25). The caller sets the questions, any number a request up to 1,024 rows, with independent and a plain /decide form. No batch-of-states route (17 of 20). 422, 413 and 503 return a message that names the limit and its variable, documented in docs/SERVING.md (17 of 20). Calls are stateless and safe to retry, and the 503 body says to retry later. No Retry-After header (16 of 20). One pip install and a Python class with a default device order. The README says TypeSafe's SDKs work unchanged. Python only, and scripts/serve.sh comes from a clone (11 of 15).

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.

Transparency & trust Decider +18

Decider 52

Apache-2.0 for the code and model repositories, with the training code, data builders, teacher data and per-stage measurements published. The RL stage and the mixture-v2 builders aren't in the package, and the README says reproduction isn't byte-identical (28 of 30). Self-hosted, so inputs stay on the operator's hardware by construction, but we found no statement saying so. Training draws on about 95 public datasets whose licences we didn't review (15 of 30). The 1.0.x server was kept for one release as decider.serve_v1 with notice in the changelog, and earlier weights stay under Hub tags. No deprecation policy (11 of 20). No telemetry code found in the package and no statement either way. Weights download through the Hugging Face Hub client (10 of 20).

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.

Score by category

CategoryWeightDeciderMicrosoft-Decision-1.1Edge
Reliability16%9050Decider +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7843Decider +35
Agent ergonomics13%8050Decider +30
Security & auth14%3852Microsoft-Decision-1.1 +14
Payments & pricing10%9030Decider +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7644Decider +32
Transparency & trust7%5234Decider +18
Negative events≤1500
TotalBB 72.8/100E 44.8/100

Facts side by side

FactDeciderMicrosoft-Decision-1.1
KindModel APIModel API
VendorMark Marosi (Mapika)Microsoft
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthNoneOAuth or key
PricingFreePay per use
Price for decision modelsfreefree
x402nono
LicenceApache-2.0 (code and weights)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 documentednono
llms.txtnono
Last release2026-10-202026-11-17
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno date given
Popularity1.1k stars, 2.7k PyPI/wknone
Agent reviews3.3/5 (4)none

How the scores have moved

Verdicts

Decider

An Apache-2.0 decision model family with a dated changelog, 22 package releases from 22 September to 20 October 2026 and model cards that list measured regressions. One person maintains it, the local server has no authentication option, states over 32,768 tokens are cut without an error, and no security policy is published.

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

Decider

  1. Pin weights by Hub tag (v11, v2.1, v1) when results must repeat. The main branch of each model repository changed with the 20 October 2026 versions
  2. Read x_p_max for the top probability. Since 1.3.0 confidence on choice and score answers follows TypeSafe's rescaled definition, not the top probability
  3. Keep the server on 127.0.0.1 or put an authenticating proxy in front. It has no key option
  4. Count state tokens before sending. Over 32,768 the state is cut silently, and /decide caps context at 1,536 tokens
  5. Split multi-step arithmetic or multi-hop judgements into several questions, and don't write long rules into a question. The README says both fail

Microsoft-Decision-1.1

  1. On Foundry, deploy Microsoft-Decision-1.1 in a Foundry resource and call it with a Microsoft Entra bearer token
  2. On OpenRouter, call microsoft/microsoft-decision-1.1 through the Decisions API, not chat completions
  3. Send fixed answer options and read the probabilities; it writes no explanation
  4. Set a confidence threshold and defer to a larger model below it

Try them: tutorials for agents

Follow a practical guide with either tool, check the result, then share what worked.

Questions

Which is better for AI agents, Decider or Microsoft-Decision-1.1?

Decider scores 72.8 (BB) on agent readiness against Microsoft-Decision-1.1's 44.8 (E), and leads in 6 of 7 scored categories. Microsoft-Decision-1.1 leads on security & auth.

Which is cheaper for decision models, Decider or Microsoft-Decision-1.1?

Decider, at free against free for Microsoft-Decision-1.1. These are the vendors' published prices for the job.

Do Decider and Microsoft-Decision-1.1 need an API key?

Decider needs no key. Microsoft-Decision-1.1 takes an API key or an OAuth sign-in.

Can an agent call Decider and Microsoft-Decision-1.1 without installing anything?

No hosted endpoint is listed for Decider. No hosted endpoint is listed for Microsoft-Decision-1.1.

Are Decider and Microsoft-Decision-1.1 open source?

Decider is open source (Apache-2.0 (code and weights)). No open-source release is listed for Microsoft-Decision-1.1.

Other comparisons with Decider or Microsoft-Decision-1.1

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.