Head to head · Decision models · October 2026 research run

Kev vs Microsoft-Decision-1.1

Kev scores 70.5 (BB) on agent readiness against Microsoft-Decision-1.1's 44.8 (E), and leads in 6 of 7 scored categories. 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

Kev BB

Best for Self-hosted classification, routing, triage and rubric scoring where a probability matters, especially for teams already calling Jev who want the same API on their own hardware.

Ahead on

  • Reliability, 73 against 50
  • Schema & documentation, 77 against 43
  • Agent ergonomics, 78 against 50
  • Payments & pricing, 90 against 30
  • Maintenance & community, 63 against 44
  • Transparency & trust, 55 against 34

Also in its favour

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

Watch for

No package. pip install kev installs an unrelated 2021 ORM, so Kev runs from a Git clone with uv

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.

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 Kev +60

Kev 90

Free Apache-2.0 software with nothing to buy from Kev, so 20 + 20 + 20 for pricing, free use and no sign-up. No payment protocol (0). GPU time is yours, on your own hardware or on Modal at the hourly rates the deploy skill lists. 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.

Schema & documentation Kev +34

Kev 77

Read for a model you serve yourself. The server is FastAPI with Pydantic request models (SystemOneRequest, Noul, Choice, Score) and follows TypeSafe's published System One contract, but Kev publishes no spec file of its own (18 of 25). No llms.txt. The README, model cards, release notes and two agent skills are Markdown in the repository (5 of 10). Each model card has intended and out-of-scope uses, and the README and release notes say where Kev trails Jev, such as knowledge questions, date arithmetic and option order (18 of 20). Three question types with 1 to 255 options or levels, and a 65,536-token state limit enforced with a 422. State is free-form by design (12 of 15). curl and Python examples, a sample response, and the 422 and 401 cases described. No full error table (12 of 15). Hub tags pin every version (v1.0, v1, v1-lora) and the release notes are dated, with no separate changelog (12 of 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.

Agent ergonomics Kev +28

Kev 78

Read as an API an agent calls for a decision, as with Jev and Clef. Answers are a probability per allowed option, so output stays small, and the server caches the state, so more questions about the same document pay only for the questions. Validated context is 8,192 tokens on the three smaller models and 65,536 on Kev-27B (20 of 25). The caller sets the output shape, with any number of questions a request, and /v1/systemone/separate and /v1/systemone/permute check question isolation and option order (18 of 20). A 422 names the state's token count and the limit, and a missing key gets a 401 saying how to send it. Other errors aren't documented (15 of 20). Calls are stateless and safe to retry. There's no retry guidance and no rate limiting in the server (15 of 20). TypeSafe's Python SDK works unchanged per the README, and kev-latest is the default model, but setup is a clone, a uv sync and a GPU or a Mac (10 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.

Reliability Kev +23

Kev 73

Scored on the local-package checklist, since Kev is a model you run. It isn't on a package index, because the PyPI name kev belongs to an unrelated 2021 project. It installs from the repository with uv and a lockfile, with Python 3.12 and 3.13 stated, or from release tarballs with SHA-256 checksums (10 of 20). Public CI on GitHub Actions runs the unit tests and the playground build on every push, and the latest runs on main had passed when we looked on 2 October. The model parity and API tests need weights and aren't in CI (20 of 25). One open issue, #8 from 20 September on date arithmetic, which the README lists as a limitation with a workaround, KEV_DATE_FACTS=1 (23 of 25). The Kev 1.0 release notes say what changed, including the server refusing over-long states with a 422 where it used to cut them silently, but the Python package has stayed at 0.1.0 and there's no changelog file (10 of 15). Kev 1.0 fixes the four checkpoints as one versioned family, while the package classifier still says alpha (10 of 15). Re-read on 1 November from a clone. No new release since Kev 1.0, the CI workflow still runs the unit tests and the playground build on pushes and pull requests, and the CI results and issue list rest on the 2 October check, since GitHub's pages answered 403. 10 + 20 + 23 + 10 + 10 = 73.

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.

Transparency & trust Kev +21

Kev 55

Apache-2.0 for the code, adapters and heads, on Apache-2.0 Qwen bases. The model cards give the training recipe, and the document and skill training partitions are on the Hub. Kev-27B's base is Qwen's post-trained release, whose training data is unknown, and the card says so (30). Self-hosted, so inputs stay on your hardware, which the model card states. There's no other data statement, and nothing on what a Modal deploy logs (20 of 30). Earlier versions stay at Hub tags, and the retired kev-family release points to kev-1.0. No deprecation policy (10 of 20). We found no telemetry code in the kev package and the docs say nothing 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.

Maintenance & community Kev +19

Kev 63

Read as a model, for deprecation notice and model churn rather than release counts, on the lines used for Decider, Laya, Jev and the other decision models listed as models. Kev 1.0 on 1 October 2026, a GitHub release and v1.0 tags on all four Hub repositories, is the last release and the last model change. The Hub's last commits on each repository, on 1 October, change only the model card, and the code on main has changed since (fixes to device probing, the fine-tuning skill and tests, to 23 October) without a release. 31 days on 1 November (20). No deprecation policy or notice period. Each new version replaced the weights on main on the day it shipped, and earlier versions stay pinnable under Hub tags (v7-base on the three smaller models, v1 on Kev-9B, v1-lora on Kev-27B), with the retired kev-family release pointing to kev-1.0 (5 of 12, level with Decider's 5). Kev-4B had several weight updates from 20 to 24 September and Kev-9B v2 and Kev-27B v2 replaced main on 30 September, and since Kev 1.0 fixed the four as one versioned family no weights have changed in 31 days, with pins still working (5 of 8, level with Laya's and above Decider's 4 for continuing replacements). Outside pull requests are still merged (#171 and #226 in October), but Jared Palmer wrote 184 of the 210 commits we cloned and a Devin bot 16 more, and issue replies rest on the 2 October check (18 of 25). No SDK of its own. Kev reuses TypeSafe's Python SDK, and agent skills handle deploys and fine-tunes. Not an MCP server, so no registry entry applies (8 of 15). A CI workflow and a uv lockfile, with torch capped below 2.9, and CI results per the 2 October check (7 of 10). 20 + 5 + 5 + 18 + 8 + 7 = 63.

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

CategoryWeightKevMicrosoft-Decision-1.1Edge
Reliability16%7350Kev +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7743Kev +34
Agent ergonomics13%7850Kev +28
Security & auth14%5252even
Payments & pricing10%9030Kev +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6344Kev +19
Transparency & trust7%5534Kev +21
Negative events≤1500
TotalBB 70.5/100E 44.8/100

Facts side by side

FactKevMicrosoft-Decision-1.1
KindModel APIModel API
VendorJared PalmerMicrosoft
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthNoneOAuth or key
PricingFreePay per use
Price for decision modelsfreefree
x402nono
LicenceApache-2.0 (code, adapters 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-012026-11-17
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno date given
Agent reviews3.5/5 (2)none

How the scores have moved

Verdicts

Kev

Apache-2.0 code, adapters and heads on Apache-2.0 Qwen bases, with release tarballs and SHA-256 checksums for the 0.8B, 4B and 9B models. No package. pip install kev installs an unrelated 2021 ORM, so Kev runs from a Git clone with uv.

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

Kev

  1. Install from the repository. The kev package on PyPI is an unrelated project
  2. Pin a checkpoint with @v1.0, as in jaredpalmer/kev-4b@v1.0, so tuned thresholds keep their meaning
  3. Keep states under 8,192 tokens on Kev-0.8B, 4B and 9B, or use Kev-27B for long documents
  4. Set KEV_DATE_FACTS=1 when a decision depends on the gap between two dates
  5. Expect a 422 naming the token count when a state passes 65,536 tokens. The server refuses it instead of cutting it

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, Kev or Microsoft-Decision-1.1?

Kev scores 70.5 (BB) on agent readiness against Microsoft-Decision-1.1's 44.8 (E), and leads in 6 of 7 scored categories.

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

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

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

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

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

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

Are Kev and Microsoft-Decision-1.1 open source?

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

Other comparisons with Kev 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.