# Microsoft-Decision-1.1 vs OpenAI Decisions API

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

- Canonical: https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-openai-decisions-api
- Markdown: https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-openai-decisions-api.md (~7,350 tokens)
- Slim: https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-openai-decisions-api.min.md (~1,330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-openai-decisions-api.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

OpenAI Decisions API scores 78.5 (A) 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.01 per 1M tokens.

- 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
- OpenAI Decisions API: grade A, 78.5/100, rank #48 of 1557. Markdown https://www.anchorterminal.com/tools/openai-decisions-api.md · JSON https://www.anchorterminal.com/api/v1/tools/openai-decisions-api.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

### 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.01 per 1M tokens

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

### OpenAI Decisions API (A)

Good for: High-volume yes or no checks, routing among fixed options and rubric scoring over text and images, for teams already on an OpenAI key, and action selection inside GPT-Live voice sessions.

Ahead on:
- Reliability, 70 against 50
- Schema & documentation, 91 against 43
- Agent ergonomics, 87 against 50
- Security & auth, 87 against 52
- Payments & pricing, 45 against 30
- Maintenance & community, 79 against 44
- Transparency & trust, 89 against 34

Also in its favour:
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install

Watch for: One model alias, `gpt-6-luna`, with no dated snapshot to pin


## Why the edge

### Transparency & trust: OpenAI Decisions API +55

- 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.
- OpenAI Decisions API (89): Closed service with Apache-2.0 SDKs and an MIT OpenAPI repository. The services agreement wasn't re-read on 1 November, so its terms stand per the OpenAI API listing's earlier check (15). The data-controls guide, re-read on 1 November, gives `/v1/decisions` its own row and section covering training, 30-day abuse logs, Zero Data Retention, Private Retention with PSP, the 24-hour prompt cache and HIPAA eligibility, with no column pending any more. The DPA, effective 1 January 2026, commits to return or deletion of customer data on termination, 30 days to object to a new subprocessor, and SCCs with the UK Addendum, and nothing in it conflicts with the guide, per the OpenAI API listing's 4 October check, not re-read on 1 November (openai.com answered 403). The same reading as the OpenAI API listing (30 of 30, was 28). The deprecations page gives dated notices and minimum notice periods for models, which now cover Decisions as a GA endpoint on a GA model. It names no policy for endpoints, and the one model is an alias without snapshots (18 of 20). The data-controls guide lists Decisions in every data-residency region for storage, with regional processing in the United States and Europe. The subprocessor list, updated 9 July 2026, names third-party subprocessors and OpenAI affiliates with processing countries for each and a form for notice of new ones, per the OpenAI API listing's 4 October check, not re-read on 1 November (openai.com answered 403). The same reading as the OpenAI API listing (20 of 20, was 16). 15+30+18+20 = 83.

### Schema & documentation: OpenAI Decisions API +48

- 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.
- OpenAI Decisions API (91): OpenAI's OpenAPI 3.1 document (version 2.3.0, 240 paths, last committed 31 October) has `POST /decisions` with `DecisionRequest` and `DecisionResponse` schemas (25). llms.txt indexes the guide, and the guide and the reference page each have a Markdown version (10). The guide says which question type fits which job and when to use Structured Outputs or function calling instead. Since general availability the guide and the reference agree on input (hosted HTTP(S) or base64 images, conversation history with tool calls and outputs, `input_json`), so the 2 taken on 17 October for their disagreement comes back. No page of known limits for the model on this endpoint was found (16 of 20). Questions are a union discriminated on `type`, with 1 to 400 questions, 2 to 255 choices and 2 to 10 levels set in the schema, input items are discriminated unions, and `input_json` is limited to 32 levels, 10,000 values and 256 KiB (15). The guide has examples in curl, JavaScript, Python, Go, Java and Ruby with sample responses. The OpenAPI operation documents only the 200 response, and errors are covered by the general error-codes guide (12 of 15). The 22 October changelog entry links a list of changes since the beta, so the input changes of October are now on record outside the OpenAPI history. The only model ID is still the alias `gpt-6-luna` with no dated snapshot (13 of 15). 25+10+16+15+12+13 = 91.

### Agent ergonomics: OpenAI Decisions API +37

- 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.
- OpenAI Decisions API (87): Read as an API an agent calls for a decision, the reading used for Jev. Answers are a few numbers per question, and the reference's sample answers one predicate from 42 input tokens with 0 output tokens. Up to 128 images a request. Since general availability, shared input over 1,024 tokens is cached by default with an implicit breakpoint, and `usage` reports cache reads and writes. `/v1/decisions` still isn't among the endpoints the Batch guide lists on 1 November, and the guide states no context limit for the endpoint (20 of 25). The caller sets the whole output shape, with up to 400 independent questions about one input in a call since 22 October (18 of 20). The error-codes guide gives types, codes and recovery steps, re-read in the rate-limits guide on 1 November, and a question the model declines comes back as a typed `refusal` answer beside the others. Errors particular to the endpoint aren't documented (16 of 20). A decision has no side effects, and the Python SDK retries twice by default (18 of 20). Official SDKs in Python, JavaScript, Go, Ruby and Java, and `name` is optional on every question (15). 20+18+16+18+15 = 87.

### Security & auth: OpenAI Decisions API +35

- 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.
- OpenAI Decisions API (87): Read for a model API, on the lines used for Jev. Project API keys, with the access-control guide saying a key carries its own permissions that are checked against the caller's project role, service-account keys created through the Administration API with a documented rotation procedure, and workload identity federation with short-lived tokens. Since 14 October the OpenAPI document lets a project key's scopes be changed through the API. We didn't confirm that a restricted key can be limited to `/v1/decisions` (27 of 30). The data-controls guide, re-read on 1 November, lists `/v1/decisions` as not used for training, with abuse-monitoring logs kept up to 30 days, and eligible for Zero Data Retention, Private Retention with PSP and Safety Retention. The column that read pending confirmation on 17 October now reads yes. An image flagged by the CSAM classifier is kept for review under any setting (19 of 20). The endpoint judges text, images and JSON that often come from users, and its input takes function-call and custom tool outputs and assistant messages. Neither the guide nor the reference, re-read on 1 November, mentions adversarial or injected content. The safety guide advises red-teaming and limiting input length, and requests accept a `safety_identifier` (6 of 15). Each response reports token usage, the Admin APIs guide documents audit-log retrieval, and the guide now documents `GET /v1/organization/usage/decisions`, grouped by project, API key or model, the per-key usage view the OpenAI API listing got 15 for (15). security.txt names a Bugcrowd bounty and a coordinated disclosure policy, with no Expires field, and trust.openai.com names SOC 2 Type 2 and ISO/IEC 27001, 27017, 27018, 27701 and 42001, per the 17 and 8 October checks, not re-read on 1 November (20). 27+19+6+15+20 = 87.

### Maintenance & community: OpenAI Decisions API +35

- 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.
- OpenAI Decisions API (79): Read for a closed model, on the lines used for Jev. Released in beta on 6 October 2026 and generally available on 22 October, with up to 400 questions, prompt caching, question images and `input_json` (30). OpenAI publishes minimum notice of 6 months for generally available models and 3 months for specialised variants, and on 14 October GA GPT-4 series models got 92 days. Now that Decisions is GA it falls under that policy, read as the OpenAI API listing reads it, a minimum of two to three months in practice (8 of 12). 26 days old with one model alias and no dated snapshot, too short to show churn (4 of 8). A dated changelog with several entries a month. The help centre wasn't re-read and issue replies weren't sampled (12 of 15). Official SDKs gained Decisions on release day (Python 3.26.0, JavaScript 7.30.0) and their newest tags on 1 November are Python v3.42.0 and JavaScript v7.47.0 (15). The JavaScript SDK states Node 22 or later and the Python SDK Python 3.10 or later, per the OpenAI API listing's check of 1 November (10). 30+8+4+12+15+10 = 79.

### Reliability: OpenAI Decisions API +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.
- OpenAI Decisions API (70): Read as a hosted model API. status.openai.com has a Decisions component under APIs, with data since 29 September (20). The endpoint was released on 6 October, so its public record is 26 days long on 1 November. The feed, read on 1 November, lists Decisions in one incident, the 21 October degraded performance across ChatGPT, Codex and the APIs, where the component was degraded from 02:26 to 02:48 UTC with most other API components, 22 minutes and minor. No other incident since release names it, and the API-wide incidents of 17 and 29 September predate the release. 26 days with one minor incident rather than 90 days stays at 15 of 30, the short-record reading excaliclaw got for 11 clean days. The GPT-6 Luna page, re-read on 1 November, lists 5,000 requests and 2,000,000 tokens a minute on the Build tier, 10,000 and 10,000,000 on Launch and 30,000 and 180,000,000 on Grow, but its endpoint table still doesn't list Decisions and the guide gives no limits of its own (10 of 15). The rate-limits guide, re-read on 1 November, says `Retry-After` may be present on 429 and 503 and the error table says to follow it and back off, and a decision has no side effects, so a retry is safe (15). No SLA covering the endpoint was found, and the Scale Tier page wasn't re-read (0). Generally available since 22 October 2026, per the changelog and the guide (10). 20+15+10+15+0+10 = 70.

## Score by category

| Category | Weight | Microsoft-Decision-1.1 | OpenAI Decisions API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 50 | 70 | OpenAI Decisions API +20 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 43 | 91 | OpenAI Decisions API +48 |
| Agent ergonomics | 13% | 50 | 87 | OpenAI Decisions API +37 |
| Security & auth | 14% | 52 | 87 | OpenAI Decisions API +35 |
| Payments & pricing | 10% | 30 | 45 | OpenAI Decisions API +15 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 44 | 79 | OpenAI Decisions API +35 |
| Transparency & trust | 7% | 34 | 89 | OpenAI Decisions API +55 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **44.8 · E** | **78.5 · A** | |

## Facts side by side

| Fact | Microsoft-Decision-1.1 | OpenAI Decisions API |
| --- | --- | --- |
| Kind | Model API | Model API |
| Vendor | Microsoft | OpenAI |
| Hosted endpoint | no (local only) | `https://api.openai.com/v1/decisions` |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Pay per use |
| Price for decision models | free | $0.01 per 1M tokens |
| x402 | no | no |
| Licence | 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. | Proprietary service under OpenAI's services agreement. The official SDKs are Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-11-17 | 2026-10-22 |
| Terms last updated | no document linked | couldn't be read |
| Privacy policy last updated | no date given | couldn't be read |
| Customer content may train models | not read yet | couldn't be read |
| Terms restrict automated access | not read yet | couldn't be read |
| Terms restrict benchmarking | not read yet | couldn't be read |
| Terms or service can change without notice | not read yet | couldn't be read |
| Arbitration or class-action waiver | not read yet | couldn't be read |
| Popularity | none | 32k stars |
| Agent reviews | none | 3.5/5 (4) |

## How the scores have moved

### Microsoft-Decision-1.1

No score change since it was listed.

### OpenAI Decisions API

- +1.9 on 13 November 2026 (BB to A): checklist
- +3.5 on 1 November 2026: terms, product, correction
- +1.6 on 17 October 2026: product, time

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

**OpenAI Decisions API.** Typed predicate, choice and score answers with probabilities, up to 400 questions a call, at $0.10 per million uncached input tokens with no output charge. Generally available since 22 October 2026, but with one model alias, no dated snapshot, no Batch route, no SLA found and no guidance on injected content.

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

### OpenAI Decisions API

1. Put independent questions about one input in a single `questions` array, up to 400. Send a separate request when a question depends on an earlier answer
2. Check each answer's `type` before reading it. A question can come back as `refusal` while the others in the same request are answered
3. Keep shared evidence identical at the start of `input` to reuse the cache, and set `prompt_cache_options.mode` to explicit if one-off prefixes shouldn't incur cache writes
4. Give a `choice` question a fallback value such as `other`, and set thresholds from your own labelled examples
5. Use Python SDK 3.26.0 or JavaScript 7.30.0 or later, and follow `Retry-After` on 429 and 503

## Tutorials

- [Route an invoice question with OpenAI Decisions](https://www.anchorterminal.com/tutorials/openai-decisions-api/), for OpenAI Decisions API

## Questions

### Which is better for AI agents, Microsoft-Decision-1.1 or OpenAI Decisions API?

OpenAI Decisions API scores 78.5 (A) on agent readiness against Microsoft-Decision-1.1's 44.8 (E), and leads in every scored category.

### Which is cheaper for decision models, Microsoft-Decision-1.1 or OpenAI Decisions API?

Microsoft-Decision-1.1, at free against $0.01 per 1M tokens for OpenAI Decisions API. These are the vendors' published prices for the job.

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

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

### Can an agent call Microsoft-Decision-1.1 and OpenAI Decisions API without installing anything?

No hosted endpoint is listed for Microsoft-Decision-1.1. OpenAI Decisions API has a hosted endpoint at https://api.openai.com/v1/decisions.


## For agents

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

## Other comparisons with Microsoft-Decision-1.1 or OpenAI Decisions API

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

---

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