# Decision 3.0 vs Microsoft-Decision-1.1

> Decision 3.0 scores 66.7 (B) to Microsoft-Decision-1.1's 44.8 (E) for decision models. Microsoft-Decision-1.1 is cheaper for decision models, $0 against $0 per 1M tokens. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/decision-3-vs-microsoft-decision-1-1
- Markdown: https://www.anchorterminal.com/compare/decision-3-vs-microsoft-decision-1-1.md (~6,500 tokens)
- Slim: https://www.anchorterminal.com/compare/decision-3-vs-microsoft-decision-1-1.min.md (~1,180 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/decision-3-vs-microsoft-decision-1-1.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-18

Decision 3.0 scores 66.7 (B) on agent readiness against Microsoft-Decision-1.1's 44.8 (E), and leads in every scored category. Both do decision models. Microsoft-Decision-1.1 is cheaper for decision models, $0 against $0 per 1M tokens.

- Decision 3.0: grade B, 66.7/100, rank #473 of 1557. Markdown https://www.anchorterminal.com/tools/decision-3.md · JSON https://www.anchorterminal.com/api/v1/tools/decision-3.json
- Microsoft-Decision-1.1: grade E, 44.8/100, rank #1292 of 1557. Markdown https://www.anchorterminal.com/tools/microsoft-decision-1-1.md · JSON https://www.anchorterminal.com/api/v1/tools/microsoft-decision-1-1.json
- Best decision models for AI agents: https://www.anchorterminal.com/best/decision-models/index.md
- All 263 decisions comparisons: https://www.anchorterminal.com/compare/decision-models/index.md

## Which one, for what

### Decision 3.0 (B)

Good for: Self-hosted typed decisions over screenshots, documents and short video as well as text, where open weights matter.

Ahead on:
- Reliability, 61 against 50
- Schema & documentation, 70 against 43
- Agent ergonomics, 72 against 50
- Payments & pricing, 90 against 30
- Maintenance & community, 74 against 44
- Transparency & trust, 51 against 34

Also in its favour:
- No key needed to call it
- Open source

Watch for: Three 27B models (d3, d3-turbo, d3-ultra) in 14 days, with no deprecation policy or notice period

### Microsoft-Decision-1.1 (E)

Good 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

### Payments & pricing: Decision 3.0 +60

- Decision 3.0 (90): Free Apache-2.0 software with nothing to buy, so 20 + 20 + 20 for pricing, free use and no sign-up. No payment protocol (0). The authors' free API at decision.vllm-sr.ai gives the same 60 on its own lines, free with a published rate limit and daily quota per key and keys created from a terminal with a proof-of-work challenge and no account. Hardware is the owner's cost. 0 + 20 + 20 + 20 = 60. 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.

### Maintenance & community: Decision 3.0 +30

- Decision 3.0 (74): Read as a model, for deprecation notice and model churn rather than release counts, on the lines used for Vela 2.0, Kev, Decider and the other decision models listed as models. The family has grown since 12 October with d3-turbo (19 October), d3-ultra (24 October) and the authors' NVFP4, INT4 and FP8 builds of them (21 to 30 October). The last model change is d3-ultra's FP8 and INT4 builds on 30 October (30). No deprecation policy or notice period. Earlier versions stay pinnable under Hub tags (v3.0.0 to v3.1.3 on the first six, v1.0 and v1.1 on d3-turbo), nothing has been removed, and the free API now serves d3-ultra (5 of 12, level with Vela's, Kev's and Decider's 5). Three 27B models in 14 days, each called the newest, and 11 tagged releases of d3 in its first days, while pinned versions keep working (4 of 8, level with Decider's 4 for continuing replacements). Org members answered 9 of the 14 questions others opened on the Hub, mostly within two days, while five questions and the seven pull requests opened on 31 October had no reply on 2 November. Router issue reply times weren't read (18 of 25). No SDK of its own. The router serves it only on the development channel, and vLLM 0.33.0 serves it natively (10 of 15). The router repository runs CI, with today's result on main unread (7 of 10). 30 + 5 + 4 + 18 + 10 + 7 = 74.
- 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.

### Schema & documentation: Decision 3.0 +27

- Decision 3.0 (70): Read for a model the owner serves. The router's model runtime has an OpenAPI file, contract version 2.3.0, changed on 11 October, whose decision request carries `images` and `videos` for models with those modalities. The bundled `d3_server.py` has no specification file and documents its wire format in its docstring (22 of 25). vllm-sr.ai has no llms.txt (404). The cards and the server docstring are Markdown and plain text in each repository (5 of 10). The cards state what each size is, its inputs and limits, and the authors' evaluation. They say nothing about when not to use it (13 of 20). Three question types, choice with up to 255 options, noul and score, and an `images` or `videos` list of data URLs with stated byte and pixel caps. State is free-form text or JSON (12 of 15). Three worked examples (text, an image, a video) with downloadable inputs, but no recorded outputs and no error table. The server docstring names 401, 422 and 503 (9 of 15). Hub tags and a versioned runtime contract. No changelog for the models (9 of 15). 22 + 5 + 13 + 12 + 9 + 9 = 70. d3-turbo and d3-ultra add Box and Track question types on their cards, and the free API's docs list error codes (401, 422, 429 and 503 with Retry-After); the listing is graded on the weights the owner runs, so the free API's docs aren't counted here.
- 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: Decision 3.0 +22

- Decision 3.0 (72): Read as an API an agent calls for a decision, as with Vela, Decider and Kev. Answers are probabilities, no text is generated, and every question sees the same text, images and videos. Videos are capped at 16,384 tokens a request, and the package config sets no other input limit (20 of 25). The caller fixes the output with any mix of the three types, and `permutation_average` scores choice questions in both option orders. There's no threshold field and no set or span type (15 of 20). The server answers 422 with a message, or an `invalid_questions` map naming each bad question, and refuses an over-long request whole rather than truncating it. The runtime answers `{error: {code, message}}` (15 of 20). Calls are stateless and safe to retry. The bundled server takes one request at a time and has no 429 or retry guidance (13 of 20). Loading is one `AutoModel` call or a `pipeline("decision")`, with no SDK of its own. It needs a GPU for the evaluated settings, `trust_remote_code`, or the router's development channel (9 of 15). 20 + 15 + 15 + 13 + 9 = 72.
- 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: Decision 3.0 +17

- Decision 3.0 (51): Apache-2.0 for the weights and runtime, on Apache-2.0 Qwen3.5 and Qwen3.8 bases, with a NOTICE in each repository. Unlike Vela 2.0, the cards publish no training data or training stages, and we found no training code (24 of 30). Self-hosted, so inputs stay on the owner's hardware unless the Python API is given URLs to fetch. The runtime docs say request text is never logged. There's no privacy statement for the project (20 of 30). The router's support matrix has a Deprecated class, and Decision 1.0, 2.0 and Vela stay built in. No policy with notice periods (8 of 20). We found no telemetry statement either way and didn't audit the runtime code for it. Weights download from the Hugging Face Hub (10 of 20). 24 + 20 + 8 + 10 = 62. The authors' free API has its own terms and privacy notice, dated 13 October 2026, which agree with each other.
- 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: Decision 3.0 +11

- Decision 3.0 (61): Scored on the local-package checklist, since Decision 3.0 is a model the owner runs, as for Vela 2.0, Kev and Decider. The cards install with `pip install "transformers==5.17.0" torch ...` and load with `AutoModel.from_pretrained(..., trust_remote_code=True)`, with no Python version stated. vLLM's native support (commit 89cab55, merged 14 October) is in the v0.33.0 release, tagged on 1 November (its last commit is dated 31 October), though the cards still point to nightly builds with a Python 3.12 environment. The router's Engine mode is still on its development channel (15 of 20). The semantic-router repository runs public CI, and its model runtime has a `test_decision3_reference.py` suite and a parity record against the packages' own server, per the 12 October check. Today's CI result on main was unread, since GitHub's pages answer 403 (15 of 25). The eight Hub repositories hold 35 discussions and pull requests from 10 October to 31 October, and org members answered 9 of the 14 questions opened by others, read as counts of authors and dates. Whether any report a crash wasn't read (12 of 25). d3 is tagged v3.0.0 to v3.1.3 (11 tags), d3-mini v3.0.0 to v3.1.3, d3-turbo v1.0 and v1.1, and d3-ultra has no tag. No changelog in the model repositories (9 of 15). Released as 3.0 with no beta label, and new sizes keep arriving (10 of 15). 15 + 15 + 12 + 9 + 10 = 61.
- 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.

## Score by category

| Category | Weight | Decision 3.0 | Microsoft-Decision-1.1 | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 61 | 50 | Decision 3.0 +11 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 70 | 43 | Decision 3.0 +27 |
| Agent ergonomics | 13% | 72 | 50 | Decision 3.0 +22 |
| Security & auth | 14% | 53 | 52 | Decision 3.0 +1 |
| Payments & pricing | 10% | 90 | 30 | Decision 3.0 +60 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 74 | 44 | Decision 3.0 +30 |
| Transparency & trust | 7% | 51 | 34 | Decision 3.0 +17 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **66.7 · B** | **44.8 · E** | |

## Facts side by side

| Fact | Decision 3.0 | Microsoft-Decision-1.1 |
| --- | --- | --- |
| Kind | Model API | Model API |
| Vendor | vLLM Semantic Router project | Microsoft |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP | HTTP |
| Auth | None | OAuth or key |
| Pricing | Free | Pay per use |
| Price for decision models | free | free |
| x402 | no | no |
| Licence | Apache-2.0 for the weights and the bundled runtime, built on Apache-2.0 Qwen3.5 and Qwen3.8 bases | 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 | no | no |
| Last release | 2026-10-30 | 2026-11-17 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no date given |
| Agent reviews | 3.3/5 (4) | none |

## How the scores have moved

### Decision 3.0

- +3.7 on 13 November 2026: checklist
- -0.6 on 2 November 2026: product, correction
- +0.3 on 28 October 2026: new evidence

### Microsoft-Decision-1.1

No score change since it was listed.

## Verdicts

**Decision 3.0.** Open Apache-2.0 decision models, now eight sizes, that read images and video as well as text and answer typed questions in one call with a probability per option. vLLM 0.33.0 serves them natively. Three 27B models arrived in 14 days with no deprecation policy, loading with `transformers` needs `trust_remote_code`, and the authors' free API may train on requests.

**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

### Decision 3.0

1. Pin a tag or commit with `revision=` when loading from the Hub. d3 had 11 tagged releases, and new 27B models keep replacing the newest
2. Send images and videos to `d3_server.py` as base64 data URLs only. The server refuses paths and http URLs with 422
3. Set `DECISION_API_KEY` before binding the bundled server beyond 127.0.0.1. It is open otherwise
4. Turn on `permutation_average=True` when routing must not depend on option order. It is off by default
5. Expect one request at a time from the bundled server. Use the router's model runtime for queued serving
6. Don't send sensitive data to decision.vllm-sr.ai. Its terms allow logging and training on requests, and only `POST /api/keys/self/forget` deletes a key's data

### 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

## Tutorials

- [Inspect package damage with Decision3](https://www.anchorterminal.com/tutorials/decision-3/), for Decision 3.0

## Questions

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

Decision 3.0 scores 66.7 (B) on agent readiness against Microsoft-Decision-1.1's 44.8 (E), and leads in every scored category.

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

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

### Do Decision 3.0 and Microsoft-Decision-1.1 need an API key?

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

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

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

### Are Decision 3.0 and Microsoft-Decision-1.1 open source?

Decision 3.0 is open source (Apache-2.0 for the weights and the bundled runtime, built on Apache-2.0 Qwen3.5 and Qwen3.8 bases). No open-source release is listed for Microsoft-Decision-1.1.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/decision-3-vs-microsoft-decision-1-1.json, and with the fewest tokens: https://www.anchorterminal.com/compare/decision-3-vs-microsoft-decision-1-1.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "decision-3", "b": "microsoft-decision-1-1"}`. From a terminal: `anchor compare decision-3 microsoft-decision-1-1`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/decision-3.json and https://www.anchorterminal.com/api/v1/tools/microsoft-decision-1-1.json

## Other comparisons with Decision 3.0 or Microsoft-Decision-1.1

- [Celeris-1 Decision vs Decision 3.0](https://www.anchorterminal.com/compare/celeris-1-decision-vs-decision-3.md)
- [Celeris-1 Decision vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/celeris-1-decision-vs-microsoft-decision-1-1.md)
- [Clef vs Decision 3.0](https://www.anchorterminal.com/compare/cloudflare-clef-vs-decision-3.md)
- [Clef vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/cloudflare-clef-vs-microsoft-decision-1-1.md)
- [Laya vs Decision 3.0](https://www.anchorterminal.com/compare/convai-laya-vs-decision-3.md)
- [Laya vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/convai-laya-vs-microsoft-decision-1-1.md)
- [Decider vs Decision 3.0](https://www.anchorterminal.com/compare/decider-vs-decision-3.md)
- [Decider vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/decider-vs-microsoft-decision-1-1.md)
- [Decision 3.0 vs Gemini Decision 1](https://www.anchorterminal.com/compare/decision-3-vs-gemini-decision-1.md)
- [Decision 3.0 vs GLiClass](https://www.anchorterminal.com/compare/decision-3-vs-gliclass.md)
- [Decision 3.0 vs Granite Switch 4.1](https://www.anchorterminal.com/compare/decision-3-vs-granite-switch.md)
- [Decision 3.0 vs Kev](https://www.anchorterminal.com/compare/decision-3-vs-jaredpalmer-kev.md)
- [Decision 3.0 vs Liquid d1](https://www.anchorterminal.com/compare/decision-3-vs-liquid-d1.md)
- [Decision 3.0 vs Microsoft-Decision-1](https://www.anchorterminal.com/compare/decision-3-vs-microsoft-decision-1.md)
- [Decision 3.0 vs Drex 1.5](https://www.anchorterminal.com/compare/decision-3-vs-nace-drex.md)
- [Decision 3.0 vs OpenAI Decisions API](https://www.anchorterminal.com/compare/decision-3-vs-openai-decisions-api.md)
- [Decision 3.0 vs pplx-decider](https://www.anchorterminal.com/compare/decision-3-vs-pplx-decider.md)
- [Decision 3.0 vs pplx-decider-flash](https://www.anchorterminal.com/compare/decision-3-vs-pplx-decider-flash.md)
- [Decision 3.0 vs RightNow System Zero](https://www.anchorterminal.com/compare/decision-3-vs-rightnow-system-zero.md)
- [Decision 3.0 vs ScaleDown](https://www.anchorterminal.com/compare/decision-3-vs-scaledown.md)
- [Decision 3.0 vs SPEV](https://www.anchorterminal.com/compare/decision-3-vs-sprag-spev.md)
- [Decision 3.0 vs kettei](https://www.anchorterminal.com/compare/decision-3-vs-sqwish-kettei.md)
- [Decision 3.0 vs Strands Decider 2B](https://www.anchorterminal.com/compare/decision-3-vs-strands-decider.md)
- [Decision 3.0 vs Jev](https://www.anchorterminal.com/compare/decision-3-vs-typesafe-jev.md)
- [Decision 3.0 vs Vela 2.0](https://www.anchorterminal.com/compare/decision-3-vs-vela.md)
- [Gemini Decision 1 vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/gemini-decision-1-vs-microsoft-decision-1-1.md)
- [GLiClass vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/gliclass-vs-microsoft-decision-1-1.md)
- [Granite Switch 4.1 vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/granite-switch-vs-microsoft-decision-1-1.md)
- [Kev vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/jaredpalmer-kev-vs-microsoft-decision-1-1.md)
- [Liquid d1 vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/liquid-d1-vs-microsoft-decision-1-1.md)
- [Microsoft-Decision-1.1 vs Drex 1.5](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-nace-drex.md)
- [Microsoft-Decision-1.1 vs OpenAI Decisions API](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-openai-decisions-api.md)
- [Microsoft-Decision-1.1 vs pplx-decider](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-pplx-decider.md)
- [Microsoft-Decision-1.1 vs pplx-decider-flash](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-pplx-decider-flash.md)
- [Microsoft-Decision-1.1 vs RightNow System Zero](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-rightnow-system-zero.md)
- [Microsoft-Decision-1.1 vs ScaleDown](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-scaledown.md)
- [Microsoft-Decision-1.1 vs SPEV](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-sprag-spev.md)
- [Microsoft-Decision-1.1 vs kettei](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-sqwish-kettei.md)
- [Microsoft-Decision-1.1 vs Strands Decider 2B](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-strands-decider.md)
- [Microsoft-Decision-1.1 vs Jev](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-typesafe-jev.md)
- [Microsoft-Decision-1.1 vs Vela 2.0](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-vela.md)
- [Microsoft-Decision-1 vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/microsoft-decision-1-vs-microsoft-decision-1-1.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
