[KongchangAI]
ModelDecision-1

Microsoft-Decision-1

A specialized decision-scoring model introduced by Microsoft, post-trained from Qwen3.5-9B. It focuses on four task types: routing, classification, verification, and agent control, with calibrated probabilities and structured output as core capabilities, offering very low latency and cost.

Core Facts

Timeline (last 90 days)

Oct 13

Microsoft-Decision-1 was released on October 9, with an input price of $0.042 / 1M tokens, free output, and undisclosed weights and context.

Unverified50%
Oct 12

The model input cost for 100,000 requests × 2,000 billed input tokens is about $8.40 (excluding retries, retrieval, moderation, and platform fees).

Unverified50%
Oct 12

OpenRouter lists Microsoft-Decision-1's context window as 32,768 tokens, with text-only input and structured decision output, and no support for images or audio.

Unverified50%
Oct 12

The choice type always selects one option, and if no abstention option is provided, the model is forced to give an answer even when evidence is insufficient; the Learn documentation recommends adding an abstention option when a choice should not be forced.

Unverified50%
Oct 12

In Copilot quality scoring, Microsoft-Decision-1 is on par with GPT-5.6 Luna and about 100 times faster (Microsoft's statement).

Unverified50%
Oct 12

Under eight kinds of input perturbation, Microsoft-Decision-1's average decision flip rate is only 1.3%; when option descriptions are reworded or option order is reversed/shuffled, there are zero flips (vendor data).

Unverified50%
Oct 12

According to Achint Srivastava's blog, Microsoft-Decision-1 had the highest accuracy in Microsoft's comparison of 36 benchmarks, with about 150,000 questions kept blind during training.

Unverified50%
Oct 12

The model ID for Microsoft-Decision-1 on OpenRouter is microsoft/microsoft-decision-1, and the official documentation states that the chat-completions SDK cannot be used and the Decisions / System One interface must be used instead.

Unverified50%
Oct 12

The endpoint path for Microsoft-Decision-1 on Foundry is <your-foundry-resource-endpoint>/providers/microsoft/v1/systemone, and the model field in the request is filled with the deployment name rather than the model string.

Unverified50%
Oct 12

A Microsoft-Decision-1 request is not a chat completion; it requires passing in state (a string or JSON) plus named questions.

Unverified50%

40 more timeline events

All Facts (20)

Verified

Calibrated confidence means that when the system gives a score of 0.9, the probability of being correct should be close to 90%.

75%
Partially Verified

Microsoft launched Microsoft-Decision-1 on Product Hunt, a decision scoring model specifically designed for decision-making.

80%
Unverified

Microsoft CEO Nadella stated that Microsoft is testing the model across various areas of the company, covering scenarios such as incident response, quality control, and scientific discovery

70%
Partially Verified

Microsoft reported that Decision-1 achieved the highest accuracy in a comparison across 36 benchmarks covering nearly 150,000 questions, and claimed its P50 latency is approximately 35 times faster than GPT-6 Sol.

65%
Partially Verified

The Xbox research team used Decision-1 to categorize over 10,000 pieces of feedback, achieving performance comparable to GPT-6 Sol but more than 14 times faster and 200 times cheaper.

65%
Partially Verified

Decision-1 is live on Microsoft Foundry, priced at $0.042 per million input tokens, with output being free.

65%
Unverified

d1-3B's question types include noul (returns P(yes)), choice (returns the selected option, confidence, and the probability of each option), and score (returns the expected rating, confidence, and probability distribution on a 2–10 ordinal scale).

60%
Partially Verified

Microsoft-Decision-1 has gone live on the Microsoft Foundry and OpenRouter platforms

65%
Unverified

Microsoft-Decision-1 was released on October 9, with an input price of $0.042 / 1M tokens, free output, and undisclosed weights and context.

50%
Unverified

A Microsoft-Decision-1 request is not a chat completion; it requires passing in state (a string or JSON) plus named questions.

50%
Unverified

The model ID for Microsoft-Decision-1 on OpenRouter is microsoft/microsoft-decision-1, and the official documentation states that the chat-completions SDK cannot be used and the Decisions / System One interface must be used instead.

50%
Unverified

OpenRouter lists Microsoft-Decision-1's context window as 32,768 tokens, with text-only input and structured decision output, and no support for images or audio.

50%
Unverified

In Copilot quality scoring, Microsoft-Decision-1 is on par with GPT-5.6 Luna and about 100 times faster (Microsoft's statement).

50%
Unverified

The endpoint path for Microsoft-Decision-1 on Foundry is <your-foundry-resource-endpoint>/providers/microsoft/v1/systemone, and the model field in the request is filled with the deployment name rather than the model string.

50%
Unverified

According to Achint Srivastava's blog, Microsoft-Decision-1 had the highest accuracy in Microsoft's comparison of 36 benchmarks, with about 150,000 questions kept blind during training.

50%
Unverified

The choice type always selects one option, and if no abstention option is provided, the model is forced to give an answer even when evidence is insufficient; the Learn documentation recommends adding an abstention option when a choice should not be forced.

50%
Unverified

The model input cost for 100,000 requests × 2,000 billed input tokens is about $8.40 (excluding retries, retrieval, moderation, and platform fees).

50%
Unverified

Under eight kinds of input perturbation, Microsoft-Decision-1's average decision flip rate is only 1.3%; when option descriptions are reworded or option order is reversed/shuffled, there are zero flips (vendor data).

50%
Unverified

The balance between speed and quality in specialized decision models attempts to make trade-offs between two metrics that often conflict with each other.

50%
Unverified

Embedding a decision model into incident response workflows can automate the first two steps of the 'alert triage → root cause localization → remediation matching' pipeline.

50%

Source Articles