Head to head · Decision models · October 2026 research run
Microsoft-Decision-1 vs SPEV
SPEV scores 51.1 (D) on agent readiness against Microsoft-Decision-1's 38.8 (E), and leads in 6 of 7 scored categories. Microsoft-Decision-1 leads on security & auth. Both do decision models.
Best decision models for AI agents · All 136 decisions comparisons
Which one, for what
Best for Routing, classification, prioritisation and rubric checks over text, where a fixed set of options and a low price per token matter more than generated text.
Ahead on
- Security & auth, 52 against 33
Watch for
Public preview only. Microsoft's post gives no general availability date and states no licence for the hosted model
SPEV D
Best for Typed decisions over raw audio, such as end-of-turn detection, call triage and flagging, plus text and single images, hosted or self-hosted.
Ahead on
- Reliability, 45 against 30
- Schema & documentation, 81 against 43
- Agent ergonomics, 76 against 50
- Payments & pricing, 30 against 20
- Maintenance & community, 49 against 40
- Transparency & trust, 54 against 29
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
Published on 14 October 2026, with no service record, no status page and no API changelog
Score by category
| Category | Weight this run | Microsoft-Decision-1 | SPEV | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 30 | 45 | SPEV +15 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 43 | 81 | SPEV +38 |
| Agent ergonomics | 13%16.2 | 50 | 76 | SPEV +26 |
| Security & auth | 14%17.5 | 52 | 33 | Microsoft-Decision-1 +19 |
| Payments & pricing | 10%12.5 | 20 | 30 | SPEV +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 40 | 49 | SPEV +9 |
| Transparency & trust | 7%8.8 | 29 | 54 | SPEV +25 |
| Negative events | ≤15 | 0 | -2 | |
| Total | E 38.8/100 | D 51.1/100 |
Facts side by side
| Fact | Microsoft-Decision-1 | SPEV |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Microsoft | Sprag |
| Hosted endpoint | no (local only) | https://api.sprag.ai/v1/decisions |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Pay per use |
| Price for decision models | free | not published |
| x402 | no | no |
| Licence | Not stated. The announcement and OpenRouter's model page name no licence, and no weights repository was found. | Apache-2.0 (weights and inference code, following the Qwen3-Omni base). Training code and data aren't published |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-09 | 2026-10-14 |
| Terms last updated | no document linked | 2026-09-01 |
| Privacy policy last updated | no date given | 2026-08-01 |
| Customer content may train models | yes, with an opt-out | |
| Terms restrict automated access | not found in the text | |
| Terms restrict benchmarking | not found in the text | |
| Terms or service can change without notice | not found in the text | |
| Arbitration or class-action waiver | not found in the text |
Verdicts
Microsoft-Decision-1
Microsoft publishes $0.042 per million input tokens, with output free, and the model is callable through Microsoft Foundry and OpenRouter. It is in public preview. No licence, model-specific retention statement, rate limit or deprecation policy was found, and the Foundry route needs an Azure deployment and an Entra token. Latency and accuracy figures are Microsoft's claims.
SPEV
SPEV answers typed questions over text, audio or an image in one call, with a public OpenAPI schema and Apache-2.0 weights on Hugging Face. It is a day old, has an 8,192-token context, no status page or changelog, and Sprag's terms let it train on API content unless the customer opts out by email.
Before you call either
Microsoft-Decision-1
- Use OpenRouter's Decisions method, not an OpenAI chat-completions SDK. OpenRouter says chat completions SDKs will not work with this model
- On Foundry, send the request to the deployment's /providers/microsoft/v1/systemone path with a Microsoft Entra token for https://cognitiveservices.azure.com/.default, not an API key
- Take the deployment name from the Foundry quickstart before the first call. Microsoft says to confirm the route and authentication header, and the pages reviewed do not give the name
- Keep each request within OpenRouter's 32,768-token context and send only fixed options, since the model is not intended for open-ended generation
- Measure latency and calibration on your own labelled cases before relying on Microsoft's latency and 'nine times out of 10' statements
SPEV
- Send
model: "spev"toPOST https://api.sprag.ai/v1/decisionswith a bearer key./v1/systemonereturns 410 - Ask every question about one piece of evidence in one request. Answers come back in question order
- Send audio as base64 in
input_audiowithformat, not as a data URL, and at most one image across all messages - Keep evidence and questions under 8,192 tokens. Over the limit returns 400
model_limit_exceeded - Back off on 429 and 503 for
Retry-Afterseconds. Limits are 60 requests a minute per organisation by default - Handle an answer of type
refusal, which carries no probabilities
Questions
Which is better for AI agents, Microsoft-Decision-1 or SPEV?
SPEV scores 51.1 (D) on agent readiness against Microsoft-Decision-1's 38.8 (E), and leads in 6 of 7 scored categories. Microsoft-Decision-1 leads on security & auth.
Do Microsoft-Decision-1 and SPEV need an API key?
Microsoft-Decision-1 takes an API key or an OAuth sign-in. SPEV needs an API key.
Can an agent call Microsoft-Decision-1 and SPEV without installing anything?
No hosted endpoint is listed for Microsoft-Decision-1. SPEV has a hosted endpoint at https://api.sprag.ai/v1/decisions.
Other comparisons with Microsoft-Decision-1 or SPEV
- Celeris-1 Decision vs Microsoft-Decision-1
- Celeris-1 Decision vs SPEV
- Clef vs Microsoft-Decision-1
- Clef vs SPEV
- Laya vs Microsoft-Decision-1
- Laya vs SPEV
- Decider vs Microsoft-Decision-1
- Decider vs SPEV
- Decision 3.0 vs Microsoft-Decision-1
- Decision 3.0 vs SPEV
- GLiClass vs Microsoft-Decision-1
- GLiClass vs SPEV
- Kev vs Microsoft-Decision-1
- Kev vs SPEV
- Liquid d1 vs Microsoft-Decision-1
- Liquid d1 vs SPEV
- Microsoft-Decision-1 vs Drex 1.5
- Microsoft-Decision-1 vs OpenAI Decisions API
- Microsoft-Decision-1 vs pplx-decider
- Microsoft-Decision-1 vs ScaleDown
- Microsoft-Decision-1 vs Strands Decider 2B
- Microsoft-Decision-1 vs Jev
- Microsoft-Decision-1 vs Vela 2.0
- Drex 1.5 vs SPEV
- OpenAI Decisions API vs SPEV
- pplx-decider vs SPEV
- ScaleDown vs SPEV
- SPEV vs Strands Decider 2B
- SPEV vs Jev
- SPEV vs Vela 2.0
Machine-readable
- This page as Markdown
/compare/microsoft-decision-1-vs-sprag-spev.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/microsoft-decision-1.json·/api/v1/tools/sprag-spev.json - From a terminal
anchor compare microsoft-decision-1 sprag-spev(the CLI) - Over MCP
compare_tools {"a": "microsoft-decision-1", "b": "sprag-spev"}at/mcp, no key