# Microsoft-Decision-1.1 vs Vela 2.0

> Vela 2.0 scores 70.4 (BB) 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/microsoft-decision-1-1-vs-vela
- Markdown: https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-vela.md (~6,600 tokens)
- Slim: https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-vela.min.md (~1,230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-vela.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

Vela 2.0 scores 70.4 (BB) 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.

- 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
- Vela 2.0: grade BB, 70.4/100, rank #300 of 1557. Markdown https://www.anchorterminal.com/tools/vela.md · JSON https://www.anchorterminal.com/api/v1/tools/vela.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 per 1M tokens

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

### Vela 2.0 (BB)

Good for: Self-hosted routing and guardrail checks in one call, where span offsets for personal data or unsupported claims matter.

Ahead on:
- Reliability, 57 against 50
- Schema & documentation, 78 against 43
- Agent ergonomics, 79 against 50
- Security & auth, 63 against 52
- Payments & pricing, 90 against 30
- Maintenance & community, 74 against 44
- Transparency & trust, 54 against 34

Also in its favour:
- Agent-ready, a grade of BB or better
- No key needed to call it
- Open source

Watch for: No version tags on the four Hub repositories, and the 4B and 9B weights were replaced in place on 3 October 2026


## Why the edge

### Payments & pricing: Vela 2.0 +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.
- Vela 2.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). There is no hosted API. Hardware is the owner's cost. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

### Schema & documentation: Vela 2.0 +35

- 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.
- Vela 2.0 (78): Read for a model the owner serves. The router's model runtime carries an OpenAPI 3.0.3 file, contract version 2.2.0 on 8 October and 3.2.0 on 1 November, served at `GET /openapi.yaml`, which covers `/v1/decisions` and its `/v1/systemone` alias. The server bundled in the model repositories has no specification file (22 of 25). vllm-sr.ai has no llms.txt (404). The model cards, USAGE.md, EVALUATION.md and TRAINING.md are Markdown in each repository (5 of 10). Each card states the size's intended place and its evaluation limits, and the router's release note names the signals where the 0.3B is behind Vela 1.0. We found no section on uses to avoid (15 of 20). Five question types with 2 to 255 options, 2 to 10 score levels and 1 to 255 labels, and enums for span head and long-input policy. State is free-form text or named parts (13 of 15). Recorded responses for every example, and error tables for both servers (400, 404, 413, 422, 429 and 503 with codes on the runtime) (14 of 15). The runtime contract is versioned and reports `api_version`, and the router has dated release notes. The models themselves have no tags or changelog (9 of 15).

### Maintenance & community: Vela 2.0 +30

- 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.
- Vela 2.0 (74): Read as a model, for deprecation notice and model churn rather than release counts, on the lines used for Kev, Decider, Laya and the other decision models listed as models. Vela 2.0 launched on 6 October 2026, and the four Hub repositories were last changed on 7 October (card edits only). 26 days on 1 November (30). No deprecation policy or notice period. The 4B and 9B weights were replaced in place on 3 October, the repositories have no tags, and the router pins the revisions it loads. When Vela 3.0's vela3-fast replaced Vela 2.0 0.3B as the router's default on 28 October (pull request #5512), the docs gave the line that restores the 0.3B the same day, and the support matrix still lists nothing as deprecated (5 of 12, level with Kev's and Decider's 5). No Vela 2.0 weights have changed since 3 October and pinned revisions still load, but Vela 3.0, six new models launched on 26 October, took over the router's default 22 days after Vela 2.0's launch (5 of 8, level with Laya's 5 for a default switch with a restore path). The router repository's 200 newest commits span 13 October to 1 November under 57 author names, and the four Hub repositories have no discussions. Issue reply times rest on the 8 October check, since GitHub's pages answered 403 (17 of 25). No SDK of its own. The cards point to `typesafe-sdk`, and the clone's publish workflow ships the `vllm-sr` CLI to PyPI on a stable and a development channel, with 0.4.0 the last stable tag. pypi.org didn't resolve from the shell on 1 November, and the 8 October reading of PyPI's JSON endpoint, a path its robots.txt disallows, is struck (10 of 15). The router repository runs CI, a security scan and a package check, with today's result on main unread (7 of 10). 30 + 5 + 5 + 17 + 10 + 7 = 74.

### Agent ergonomics: Vela 2.0 +29

- 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.
- Vela 2.0 (79): Read as an API an agent calls for a decision, as with Jev, Clef and Kev. Answers are probabilities and spans, `output_tokens` is always 0, and the decoders read the state once and fork it per question. Input is 16,384 tokens a sequence, or 8,192 on the 0.3B (20 of 25). The caller fixes the output shape with any mix of the five types, a `threshold` per question, a `head` override for spans and `/v1/bundle` for several tasks in one call (18 of 20). The runtime answers with `{error: {code, message}}`, and a failed question carries its own code without failing the others. The bundled server answers 422 with `loc`, `msg` and `type`, and 413 for oversize questions (16 of 20). Calls are stateless and safe to retry. The runtime answers 429 `overloaded` past 256 queued requests a model. We found no `Retry-After` header in the runtime code and no retry guidance (15 of 20). `typesafe-sdk` works against the bundled server per USAGE.md, and loading is one `AutoModel` call. Setup needs `trust_remote_code`, about 17 GB of GPU memory for the 4B, or the router's development channel (10 of 15).

### Transparency & trust: Vela 2.0 +20

- Microsoft-Decision-1.1 (34): Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. No licence for the hosted model is stated in the announcement or the Tech Community post, re-read on 10 November, nor on OpenRouter's page per the 10 October check, and no Microsoft weights repository was found, so 0 of 30 for licence clarity. Microsoft's Foundry data page states no storage in the model, no training on prompts and processing within the geography or data zone, but abuse monitoring stores prompts for human review. The page does not say whether it covers this model, so 12 of 30. No dated deprecation policy was found, 0 of 20. The US and EU Datazone deployment types disclose where processing may happen, earning 10 of 20. No subprocessor list was read. Total 22.
- Vela 2.0 (54): Apache-2.0 for the weights, code and documentation, on Apache-2.0 Decision 2.0 and Qwen3.5 bases, with MODIFICATIONS.md and ATTRIBUTIONS.md in each repository. The 0.3B's tokeniser keeps the Gemma Terms of Use, and training data isn't redistributed and keeps its own licences, some CC BY-SA. We found no training code (26 of 30). Self-hosted, so inputs stay on the owner's hardware. The runtime docs say request text is never logged and metrics carry no request content. There's no privacy statement for the project (22 of 30). The router's support matrix defines a Deprecated class and says nothing is in it, and the release note gives the lines that restore each Vela 1.0 model. No policy with notice periods (10 of 20). We found no telemetry statement either way and didn't audit the runtime's code for it. Weights download from the Hugging Face Hub (10 of 20).

### Security & auth: Vela 2.0 +11

- 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.
- Vela 2.0 (63): Read as a model, for retention, training and zero-retention options in place of read-only modes, on the lines used for Kev and the other decision models listed as models. No account. The bundled `vela2_serve.py` binds to 127.0.0.1 and is open unless `VELA2_API_KEY` is set, after which it requires one bearer key, compared in constant time. The router's model runtime has no authentication, and its docs say to expose it only on a trusted network (13 of 30). Self-hosted, so nothing reaches the authors and no caller data can train a model. The model runtime reference says request text is never logged and metrics carry no request content. Nothing says what the router's other components keep (18 of 20, level with Kev). The models are trained to flag prompt attacks, each question sees only the state and its own block, and the router's SECURITY.md names adversarial input to classification models in its threat model. Nothing documents how hostile text in the state can move an answer (10 of 15). The runtime exposes Prometheus metrics and, on request, the revision, digest and timings that answered a call. The bundled server keeps no record of calls (9 of 15). SECURITY.md takes private reports through GitHub Security Advisories, with severity classes and a disclosure policy, re-read in the clone on 1 November. Weights are safetensors with a SHA256SUMS manifest in the decoder repositories, and the runtime checks every file's SHA-256 and never runs code from a model repository. The `transformers` route does run repository code through `trust_remote_code=True`, with no tag to pin. No bug bounty, and no security.txt on vllm-sr.ai (404 on 1 November) (13 of 20). 13 + 18 + 10 + 9 + 13 = 63.

## Score by category

| Category | Weight | Microsoft-Decision-1.1 | Vela 2.0 | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 50 | 57 | Vela 2.0 +7 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 43 | 78 | Vela 2.0 +35 |
| Agent ergonomics | 13% | 50 | 79 | Vela 2.0 +29 |
| Security & auth | 14% | 52 | 63 | Vela 2.0 +11 |
| Payments & pricing | 10% | 30 | 90 | Vela 2.0 +60 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 44 | 74 | Vela 2.0 +30 |
| Transparency & trust | 7% | 34 | 54 | Vela 2.0 +20 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **44.8 · E** | **70.4 · BB** | |

## Facts side by side

| Fact | Microsoft-Decision-1.1 | Vela 2.0 |
| --- | --- | --- |
| Kind | Model API | Model API |
| Vendor | Microsoft | vLLM Semantic Router project (with KR Labs) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | None |
| Pricing | Pay per use | Free |
| Price for decision models | free | free |
| 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. | Apache-2.0 (weights, code and documentation). The 0.3B's tokeniser keeps the Gemma Terms of Use, and training data keeps its own licences |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-11-17 | 2026-10-06 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no date given | no document linked |
| Popularity | none | 6.1k stars |
| Agent reviews | none | 4.3/5 (4) |

## How the scores have moved

### Microsoft-Decision-1.1

No score change since it was listed.

### Vela 2.0

- +3.8 on 13 November 2026 (B to BB): checklist
- -0.4 on 1 November 2026: correction
- +0.5 on 27 October 2026: checklist

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

**Vela 2.0.** One self-hosted call answers routing, prompt-attack, personal-data and unsupported-claim questions with probabilities and character offsets, under Apache-2.0 with SHA-256 manifests. The Hub repositories carry no version tags, the authors' own figures put the larger sizes below their Decision 2.0 bases, and Vela 3.0 replaced the 0.3B as the router's default on 28 October 2026.

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

### Vela 2.0

1. Pin a commit hash with `revision=` when loading from the Hub. The repositories have no tags, and `main` changed after launch
2. Send the served name in `model`, for example `vllm-sr/Vela-2.0-4B`. The bundled server answers 422 to any other name
3. Name span questions `pii`, `halu` or `toxic`, or set `"head": "router"`, to get the trained router head. Other labels go to the broad head
4. Keep input under 16,384 tokens a sequence (8,192 on the 0.3B). The bundled server answers 413 when the questions alone don't fit
5. Set `VELA2_API_KEY` before binding the bundled server beyond 127.0.0.1, and keep the model runtime on a trusted network
6. Name `vllm-sr/Vela-2.0-0.3B` as the `primary` deployment's artifact to keep Vela 2.0. Router builds since 28 October default to vela3-fast

## Tutorials

- [Find contact details in a message with Vela](https://www.anchorterminal.com/tutorials/vela/), for Vela 2.0

## Questions

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

Vela 2.0 scores 70.4 (BB) 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 Vela 2.0?

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

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

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

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

No hosted endpoint is listed for Microsoft-Decision-1.1. No hosted endpoint is listed for Vela 2.0.

### Are Microsoft-Decision-1.1 and Vela 2.0 open source?

No open-source release is listed for Microsoft-Decision-1.1. Vela 2.0 is open source (Apache-2.0 (weights, code and documentation). The 0.3B's tokeniser keeps the Gemma Terms of Use, and training data keeps its own licences).


## For agents

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

## Other comparisons with Microsoft-Decision-1.1 or Vela 2.0

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