Head to head · Decision models · October 2026 research run

Microsoft-Decision-1.1 vs kettei

kettei scores 61.2 (C) 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 reliability. Both do decision models.

Best decision models for AI agents · All 263 decisions comparisons

Which one, for what

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

  • Reliability, 50 against 30

Watch for

No machine-readable contract or reference page with the request schema was found

kettei C

Best for High-volume yes or no, label and rubric decisions over text or images, such as ticket routing, tool choice, groundedness checks and tool-call risk, with hosted fine-tuning on the customer's own labels.

Ahead on

  • Schema & documentation, 82 against 43
  • Agent ergonomics, 89 against 50
  • Security & auth, 68 against 52
  • Payments & pricing, 53 against 30
  • Maintenance & community, 57 against 44
  • Transparency & trust, 44 against 34

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

Launched on 14 October 2026, with no status page, no changelog and no SLA

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 kettei +39

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.

kettei 82

OpenAPI 3.1 at api.sqwish.ai/openapi.json, 76 operations and 118 schemas, with typed request bodies and additionalProperties: false on the decide request (25). llms.txt on docs.sqwish.ai and api.sqwish.ai, llms-full.txt and a Markdown twin of every docs page (10). The run-decisions reference says probabilities aren't a guarantee of correctness, each recipe carries use_when and watch fields, the interpreting-results page says normalisation isn't calibration, and the agent skill says not to use OneHot for text generation (18 of 20). kind, fallback and temperature bounds are enums or ranges, with 1 to 128 decisions and at most 8 images in the schema. Context is free-form by design (14 of 15). curl, Python and TypeScript examples on every guide, and status and error-code tables that say whether to retry and whether a call is billed (15). The OpenAPI document carries version 0.1.0 and the models are versioned (v1.0, numbered fine-tunes), but there's no API or model changelog, so the line for versioning and a public changelog isn't met, as typeform's (0). 25+10+18+14+15+0 = 82.

Agent ergonomics kettei +39

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.

kettei 89

Read as an API an agent calls for a decision. Answers are probabilities, many decisions share one context billed once, and a free estimate endpoint and a free linter run no model. 65,536 input tokens a request. No batch endpoint or prompt caching found (18 of 25). The caller fixes the outcomes, policy returns an action or abstain, and lists use cursors or offsets (18 of 20). One error envelope with code, message, retryable, request_id and details paths, with a documented code for each case (20). Idempotency keys on decisions, the Jev route, the Claude Code hook and resource creates, with replay rules spelled out. Switches and keep warm have no idempotency key, and the MCP tools' annotations weren't read (18 of 20). One required field, a default model, fallback: auto by default, and Python and TypeScript clients that retry twice with backoff (15). 89.

Payments & pricing kettei +23

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.

kettei 53

No x402, MPP or L402 (0). Per-token prices published without a login, $0.06, $0.04 and $0.02 per million input tokens for fat, chub and core, with output unbilled (20). Admission gives $5.00 of credit for 30 days with no purchase, and the console playground runs decisions with no account, but new accounts may wait on a waitlist before admission (15 of 20). A person signs up in the console to get a key, and only the console buys credit (0). 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Reliability Microsoft-Decision-1.1 +20

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.

kettei 30

Read with the hosted lines, for the OneHot API an agent calls. No status page found. status.sqwish.ai doesn't resolve and sqwish.ai/status serves the home page (0). No readable incident history, and the service is three days old (5). Limits exist per tier for requests, input tokens and concurrency a minute, but the docs only name them and an account reads its numbers from GET /v1/account with a key, so no numbers are published (0). 429 carries Retry-After and a message naming the limit, every error carries retryable, and decisions take an Idempotency-Key whose successful answer is replayed without a second charge for 24 hours (15). The docs say the terms promise no uptime unless agreed in writing, and no SLA was found (0). Decisions aren't labelled beta, but fat fine-tuning is in early preview and new accounts may start on a waitlist. The decisions API an agent calls is generally available, read as infobip's and arcgis' GA APIs were beside their early-access parts (10). 0+5+0+15+0+10 = 30.

Security & auth kettei +16

Microsoft-Decision-1.1 52

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 (credential, training, retention, operator visibility, programme), as the Google Lyria and Soundverse listings read it; the 10 October note read the tool lines (20 + 10 + 5 + 5 + 12 = 52). The Foundry sample uses a Microsoft Entra bearer token for a fixed resource scope; role assignments and token lifetimes weren't read, and OpenRouter uses an API key (20 of 30). Microsoft's data page for Foundry Models sold by Azure (updated 5 June 2026, re-read 10 November) says prompts and completions aren't used to train foundation models without permission and the models are stateless, but it doesn't name this model (10 of 20). The same page says abuse monitoring can store prompts for human review, with no period stated and a modified-monitoring application for managed customers; whether it covers this model isn't stated (5 of 15). OpenRouter's Activity page shows token volume and requests, per the 10 October check; Foundry diagnostic logs weren't read (5 of 15). Microsoft's security.txt names its coordinated vulnerability disclosure policy, a bounty and a reporting form, and was renewed to expire on 27 October 2027; no certification naming this model was read (12 of 20). 20 + 10 + 5 + 5 + 12 = 52.

kettei 68

Read for a model API. Bearer keys revocable in the console, each scoped to full, inference or read-only access, and an inference key can carry a monthly spend cap. No key can create keys, buy credit or change settings. Rotation is by replacement and no expiry was found. No secret in a URL documented (28 of 30). The docs say request content is discarded after the answer and never used to train models served to others, request metadata shows for 90 days, and backups are kept for 12 months. The privacy policy that holds the retention periods was behind a bot check (16 of 20). Kettei judges content that often comes from users. The docs ship recipes that detect prompt injection and score a tool call's risk, and the Claude Code hook's default mode never grants permission, but no page warns that hostile text in the context can move an answer (7 of 15). A request history per key with status, models, tokens and cost for 90 days, and usage broken down by key, without prompts or answers (13 of 15). No security.txt (404 on sqwish.ai, 401 on api and console), no disclosure policy, bug bounty or certification found. The docs give security@sqwish.ai for leaked keys (4 of 20). 68.

Maintenance & community kettei +13

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.

kettei 57

Read for a model. kettei-fat and kettei-chub v1.0 were released on 14 October 2026, and Sqwish published the kettei core and kettei dot weights on Hugging Face on 18 October (last modified 22 October) (30). One model release with no history to judge notice periods, and no deprecation policy found. Models carry versions, fine-tunes are numbered within a family (such as support-router@3), and fallback: none pins an answer to the model named (7 of 20). No public issue tracker for the API and no changelog. Support is help@sqwish.ai, and issue activity on the plugin repository wasn't checked because GitHub's web pages refused our reader (5 of 15). Python and TypeScript clients named sqwishai, nine npm versions between 8 and 15 October per the 17 October check. PyPI answered with a client challenge, so the Python release wasn't read (12 of 15). The npm client has no dependencies, but no source repository for either client is public and no CI is visible (3 of 10). 30+7+5+12+3 = 57.

Score by category

CategoryWeightMicrosoft-Decision-1.1ketteiEdge
Reliability16%5030Microsoft-Decision-1.1 +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4382kettei +39
Agent ergonomics13%5089kettei +39
Security & auth14%5268kettei +16
Payments & pricing10%3053kettei +23
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4457kettei +13
Transparency & trust7%3444kettei +10
Negative events≤1500
TotalE 44.8/100C 61.2/100

Facts side by side

FactMicrosoft-Decision-1.1kettei
KindModel APIModel API
VendorMicrosoftSqwish Labs
Hosted endpointno (local only)https://api.sqwish.ai/v1/decide
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingPay per usePay per use
Price for decision modelsfreenot published
x402nono
LicenceNot 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.Proprietary hosted models and API. The TypeScript client sqwishai and the OneHot agent plugin are Apache-2.0. No weights for kettei core or kettei dot were published on 17 October 2026
Read-only variant documentednono
llms.txtnoyes
Last release2026-11-172026-10-15
Terms last updatedno document linkedcouldn't be read
Privacy policy last updatedno date givencouldn't be read
Customer content may train modelsnot read yetcouldn't be read
Terms restrict automated accessnot read yetcouldn't be read
Terms restrict benchmarkingnot read yetcouldn't be read
Terms or service can change without noticenot read yetcouldn't be read
Arbitration or class-action waivernot read yetcouldn't be read
Popularitynone1.2k npm/wk
Agent reviewsnone3.8/5 (4)

How the scores have moved

Verdicts

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.

kettei

OneHot returns probabilities for up to 128 typed questions a call at $0.02 to $0.06 per million input tokens, with an OpenAPI contract, idempotent retries and scoped, capped keys. It launched on 14 October 2026 with no status page, changelog or published rate-limit numbers, and its terms sit behind a bot check.

Before you call either

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

kettei

  1. Send context and decisions to POST https://api.sqwish.ai/v1/decide with a bearer key. Leaving out model gets kettei-core, which reads text only
  2. Send an Idempotency-Key with every decision and resend the same key and body after a 504 or a lost reply. Replays aren't charged
  3. Branch on error.code and error.retryable, not the status. Wait for Retry-After on 429 and retryable 503s
  4. Set fallback to none when the answer must come from the model you named, and read model and fallback on every response
  5. Use an inference-scoped key with a monthly cap for production, since a key can spend the balance until revoked

Questions

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

kettei scores 61.2 (C) 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 reliability.

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

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

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

No hosted endpoint is listed for Microsoft-Decision-1.1. kettei has a hosted endpoint at https://api.sqwish.ai/v1/decide.

Other comparisons with Microsoft-Decision-1.1 or kettei

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.