# Clef vs Microsoft-Decision-1.1

> Clef scores 68.3 (B) to Microsoft-Decision-1.1's 44.8 (E) for decision models. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/cloudflare-clef-vs-microsoft-decision-1-1
- Markdown: https://www.anchorterminal.com/compare/cloudflare-clef-vs-microsoft-decision-1-1.md (~6,850 tokens)
- Slim: https://www.anchorterminal.com/compare/cloudflare-clef-vs-microsoft-decision-1-1.min.md (~1,230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/cloudflare-clef-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

Clef scores 68.3 (B) on agent readiness against Microsoft-Decision-1.1's 44.8 (E), and leads in every scored category. Both do decision models.

- Clef: grade B, 68.3/100, rank #389 of 1557. Markdown https://www.anchorterminal.com/tools/cloudflare-clef.md · JSON https://www.anchorterminal.com/api/v1/tools/cloudflare-clef.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

### Clef (B)

Good for: Classification, routing and rubric scoring over text, JSON and images inside Cloudflare, with audio and video through Clef-omni, or self-hosted where data can't leave.

Ahead on:
- Reliability, 68 against 50
- Schema & documentation, 78 against 43
- Agent ergonomics, 75 against 50
- Security & auth, 72 against 52
- Payments & pricing, 60 against 30
- Maintenance & community, 59 against 44
- Transparency & trust, 87 against 34

Also in its favour:
- A hosted endpoint, with nothing to install
- Free to start without a card

Watch for: Hosted Clef-flash's context fell from 64K to 24K tokens on 9 October 2026, announced in the changelog the day it took effect

### 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:
- No incidents deducted, where Clef loses 3 points for them

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


## Why the edge

### Transparency & trust: Clef +53

- Clef (87): Weights and scoring code under Apache-2.0, following the Qwen base models. Training code and data aren't published (27 of 30). The Workers AI data page and the launch post agree, no training without consent and nothing kept unless you store it. Cloudflare's privacy policy and DPA exist, per the Cloudflare MCP check (26 of 30). The Workers AI changelog posts dated notices, such as the 8 May notice for Kimi K2.5, but we found no deprecation policy (10 of 20). Cloudflare's subprocessor page names 12 third parties and 16 group companies with locations, per the Cloudflare MCP check of 1 October. Where Clef inference runs isn't stated (14 of 20). Clef-omni is Apache-2.0 on its Hugging Face card, and we didn't check whether it publishes training code or data. The churn point sits under maintenance, so the deprecation item stays at 10 of 20. Hugging Face still shows all three models under apache-2.0 on 1 November. 27 + 26 + 10 + 14 = 77.
- 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.

### Schema & documentation: Clef +35

- Clef (78): The model page publishes a JSON Schema for input and output, with `model` limited to `clef` or `clef-flash`, 1 to 64 questions and image limits, and the account API's `GET /ai/models/schema` returns a model's schemas. Cloudflare's public OpenAPI, updated 2 October, has only the generic `/ai/run/{model_name}` path (22 of 25). llms.txt for the developer docs (10). The page says what Clef does, 'turns a state and a schema of typed questions into decisions', and the launch post adds use cases, but neither says when not to use it (10 of 20). Typed question kinds behind a `type` enum, with question-count and image limits. State is free-form by design (13 of 15). Examples in JavaScript, Python and curl, and a Workers AI error table with internal and HTTP codes, though nothing specific to Clef (13 of 15). Model IDs carry no version and the Hugging Face repositories have commit history. The Workers AI page in the docs still stops at 16 June 2026, but Cloudflare's product changelog for Workers AI, read with its RSS feed on 1 November, has dated Clef entries for 1 October and 9 October 2026, the second naming the Clef-flash price and context changes (10 of 15, 7 before, when only the docs page was read). Clef-omni has its own page with a JSON Schema and media limits, published the same way. 22 + 10 + 10 + 13 + 13 + 10 = 78.
- 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.

### Payments & pricing: Clef +30

- Clef (60): No x402, MPP or L402 on Workers AI (0). Per-token prices published without a login, $0.24 per million input tokens for Clef, $0.038 for Clef-flash and $0.15 for Clef-omni, with neurons at $0.011 per 1,000 (20). Workers AI includes 10,000 neurons a day on the Free plan, and Cloudflare's Free plan needs no card per the 30 September check (20). The hosted route needs a person to sign up in a browser. The weights download from Hugging Face without an account, but other open-weight listings get no onboarding credit for that, so Clef doesn't either (0). Prices re-read on the pricing page (last updated 20 October 2026) on 1 November, and Machine Payments on `POST /ai/run` still lists four other models. 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
- 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.

### Agent ergonomics: Clef +25

- Clef (75): Read as an API an agent calls for a decision, as with Jev, since Clef doesn't call tools or generate text. Answers are a probability per allowed option, so output stays small and the cost is the state, within 65,536 tokens. No batch or caching found for Clef (18 of 25). The caller fixes the output shape, with up to 64 questions and up to 4 images a call (18 of 20). Workers AI errors carry internal codes and messages, and a 429 tells a spent free allocation from a capacity limit. Nothing Clef-specific, such as which question failed validation, is documented (14 of 20). Calls are stateless and safe to retry, but there's no retry guidance beyond 'please try again' (15 of 20). Callable over REST and from a Worker through the `AI` binding. There's no Clef SDK, the body repeats the model name the URL already carries, and we found no documented way to point TypeSafe's SDKs, which post to `/v1/systemone`, at Clef (10 of 15). Clef-omni adds audio and video with documented token costs, but media must be base64-embedded, and long text state is truncated without a documented signal. Net unchanged. 18 + 18 + 14 + 15 + 10 = 75.
- 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.

### Security & auth: Clef +20

- Clef (72): Read for a model API. Cloudflare API tokens scoped to Workers AI permissions on an account and revocable, per the Cloudflare MCP listing's check of 1 October. Permission is per account, not per model (27 of 30). The Workers AI data page (updated 16 October 2026, per the Clairic listing's 1 November check) says standard inference keeps no inputs or outputs after the response and Customer Content isn't used to train models, and the launch post says Cloudflare doesn't read, store or train on Clef requests or responses outside the fine-tuning service (18 of 20). Clef is pitched at support triage and threat intelligence, both untrusted input, and we found no guidance on adversarial or injected content in the model page, the launch post or the model card. Self-hosting runs custom code from the model repository (3 of 15). The launch post's fine-tuning flow captures datasets through AI Gateway, and gateway logs record each request when one is used. Account audit logs record token changes per the Cloudflare MCP check (6 of 15). security.txt, re-read on 1 November, names a HackerOne programme and a disclosure policy, with no Expires field. Cloudflare's ISO certifications page, read on 1 November, says Cloudflare is certified to ISO 27001 (since 2019, now to its 2022 edition), ISO 27018 and ISO 27701, with a scope of the Cloudflare global cloud platform. 2 held back for the missing Expires field, as cloudflare-clairic, cloudflare-r2, cloudflare-workers-ai and cloudflare-ai-gateway read the same evidence (18 of 20, 15 before, when certifications went unread). Clef-omni widens user-supplied input to audio and video, and Cloudflare publishes no guidance on hostile media. 27 + 18 + 3 + 6 + 18 = 72.
- 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.

### Reliability: Clef +18

- Clef (68): Scored as a hosted model on Workers AI. www.cloudflarestatus.com is a Statuspage with Workers AI as its own component (20). Clef's public record runs from its release on 1 October 2026, 31 days before 1 November. The incidents feed read on 9 October for the Workers AI listing held 21 September to 8 October, none naming Workers AI. The feed read on 20 October for the Clairic listing held 5 to 19 October, with one Workers AI incident, minor, on 15 October, errors on five DeepSeek and GLM models, not Clef. The feed read on 1 November holds 50 incidents from 16 to 31 October. Workers AI is named only in "Issues with AI Security for Apps" on 27 October, intermittent failures in unsafe topic detection with impact none, which doesn't touch Clef. The 23 October network incident, labelled major, describes some traffic between Ashburn and Atlanta and some customers in North America, and the 27 October major affected customers whose traffic passes through an external vendor firewall, so both read as partial, as cloudflare-clairic and cloudflare-workers-ai read them. The history page, read on 1 November, shows nothing naming Workers AI from 29 October to 1 November. So Clef's whole life is read and nothing touched it. A record this short reads as 15 of 30 in this run, as cloudflare-clairic (13 days) and pplx-decider (31 days) read theirs, so the 10 October 8, which isn't a checklist value, is brought into line (15). The model page lists Clef under Text Generation, whose default limit is 300 requests a minute, though Clef isn't named on the limits page (13 of 15). The errors page gives 429 two internal codes, 3036 for a spent free allocation and 3040 for capacity, per the Workers AI listing's check. No `Retry-After` was found for a 3040. A call has no side effects, so a retry is safe (10 of 15). No SLA for Workers AI found (0). The Clef and Clef-flash model pages, re-read on 1 November, carry no beta label (10). 20 + 15 + 13 + 10 + 0 + 10 = 68.
- 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 | Clef | Microsoft-Decision-1.1 | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 68 | 50 | Clef +18 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 78 | 43 | Clef +35 |
| Agent ergonomics | 13% | 75 | 50 | Clef +25 |
| Security & auth | 14% | 72 | 52 | Clef +20 |
| Payments & pricing | 10% | 60 | 30 | Clef +30 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 59 | 44 | Clef +15 |
| Transparency & trust | 7% | 87 | 34 | Clef +53 |
| Negative events | ≤15 | -3 | 0 | |
| **Total** | | **68.3 · B** | **44.8 · E** | |

## Facts side by side

| Fact | Clef | Microsoft-Decision-1.1 |
| --- | --- | --- |
| Kind | Model API | Model API |
| Vendor | Cloudflare | Microsoft |
| Hosted endpoint | `https://api.cloudflare.com/client/v4/accounts/{account_id}/ai/run/@cf/cloudflare/clef` | 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 | Apache-2.0 (weights and scoring code, following the Qwen base models). 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-09 | 2026-11-17 |
| Terms last updated | 2025-09-12 | no document linked |
| Privacy policy last updated | no date given | no date given |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Agent reviews | 3/5 (2) | none |

## How the scores have moved

### Clef

- +2.5 on 13 November 2026: checklist
- -0.2 on 1 November 2026: new evidence, correction, negative event
- +0.1 on 28 October 2026: checklist

### Microsoft-Decision-1.1

No score change since it was listed.

## Verdicts

**Clef.** Apache-2.0 weights for all three models, ungated on Hugging Face, and Clef-omni (9 October 2026) adds audio and video input. Hosted Clef-flash's context fell from 64K to 24K tokens on 9 October, announced in the changelog that day, and no SLA or stated notice period for model changes was found for Workers AI.

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

### Clef

1. Send `model` in the body as `clef`, `clef-flash` or `clef-omni`, matching the model in the URL. The input schema requires it
2. Ask every independent question about one state in one call. Up to 64 are allowed
3. Try `clef-flash` first for text-only triage under 24k tokens. It costs $0.038 per million input tokens against $0.24 for Clef
4. Send Clef-omni audio and video as base64 data URIs in `audio` and `videos`. Remote URLs are not accepted
5. Media and questions count towards the context window. If they exceed it, the request fails. Otherwise text state is truncated to fit
6. Read the internal code on a 429. 3036 means the day's 10,000 free neurons are spent, 3040 means capacity, so retry later
7. Treat an answer about user-supplied text, images, audio or video as a judgement that hostile input can steer. Cloudflare publishes no guidance on 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

## Tutorials

- [Flag an outage report with Cloudflare Clef](https://www.anchorterminal.com/tutorials/cloudflare-clef/), for Clef

## Questions

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

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

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

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

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

Clef has a hosted endpoint at https://api.cloudflare.com/client/v4/accounts/{account_id}/ai/run/@cf/cloudflare/clef. No hosted endpoint is listed for Microsoft-Decision-1.1.


## For agents

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

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

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