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

Microsoft-Decision-1 E

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

CategoryWeight this runMicrosoft-Decision-1SPEVEdge
Reliability16%203045SPEV +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24381SPEV +38
Agent ergonomics13%16.25076SPEV +26
Security & auth14%17.55233Microsoft-Decision-1 +19
Payments & pricing10%12.52030SPEV +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84049SPEV +9
Transparency & trust7%8.82954SPEV +25
Negative events≤150-2
TotalE 38.8/100D 51.1/100

Facts side by side

FactMicrosoft-Decision-1SPEV
KindModel APIModel API
VendorMicrosoftSprag
Hosted endpointno (local only)https://api.sprag.ai/v1/decisions
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingPay per usePay per use
Price for decision modelsfreenot published
x402nono
LicenceNot 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 documentednono
llms.txtnoyes
Last release2026-10-092026-10-14
Terms last updatedno document linked2026-09-01
Privacy policy last updatedno date given2026-08-01
Customer content may train modelsyes, with an opt-out
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot 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

  1. Use OpenRouter's Decisions method, not an OpenAI chat-completions SDK. OpenRouter says chat completions SDKs will not work with this model
  2. 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
  3. 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
  4. 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
  5. Measure latency and calibration on your own labelled cases before relying on Microsoft's latency and 'nine times out of 10' statements

SPEV

  1. Send model: "spev" to POST https://api.sprag.ai/v1/decisions with a bearer key. /v1/systemone returns 410
  2. Ask every question about one piece of evidence in one request. Answers come back in question order
  3. Send audio as base64 in input_audio with format, not as a data URL, and at most one image across all messages
  4. Keep evidence and questions under 8,192 tokens. Over the limit returns 400 model_limit_exceeded
  5. Back off on 429 and 503 for Retry-After seconds. Limits are 60 requests a minute per organisation by default
  6. 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

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.