Head to head · Decision models · October 2026 research run

Celeris-1 Decision vs Microsoft-Decision-1.1

Celeris-1 Decision scores 51 (D) on agent readiness against Microsoft-Decision-1.1's 44.8 (E), and leads in 3 of 7 scored categories. Microsoft-Decision-1.1 leads on security & auth. Both do decision models. Celeris-1 Decision is cheaper for decision models, $0 against $0 per 1M tokens.

Best decision models for AI agents · All 263 decisions comparisons

Which one, for what

Celeris-1 Decision D

Best for Multimodal classification, routing and bounded decisions with probabilities and optional explanations

Ahead on

  • Schema & documentation, 60 against 43
  • Agent ergonomics, 80 against 50
  • Transparency & trust, 55 against 34

Also in its favour

  • Cheaper for decision models, $0 against $0 per 1M tokens
  • A hosted endpoint, with nothing to install

Watch for

Early-access terms and capacity-dependent workspace activation

Microsoft-Decision-1.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 45

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

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Agent ergonomics Celeris-1 Decision +30

Celeris-1 Decision 80

Compact probability answers earn 25. Multiple questions, bounded options and image controls earn 15 of 20; the docs now state a 131,072-token window but no output-budget control, so the line stays partly met. Actionable errors earn 20. Retry guidance earns 10 of 20 because duplicate inference can be billed and no idempotency contract was found. Simple required fields and documented compatible Python clients earn 10 of 15; no Celeris-owned decision SDKs in two languages found. 25 + 15 + 20 + 10 + 10 = 80.

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.

Transparency & trust Celeris-1 Decision +21

Celeris-1 Decision 55

Closed model with service terms earns 15. Privacy and security statements explain processing and 90-day usage records, but not prompt retention or a training exclusion, earning 15 of 30. No dated deprecation policy found, and the move to celeris-1.1-decision carries no dated notice (0). Named subprocessors and regional-routing disclosure earn 15 of 20; a decision-specific residency guarantee was not found. 15 + 15 + 0 + 15 = 45.

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.

Schema & documentation Celeris-1 Decision +17

Celeris-1 Decision 60

No public machine-readable decision contract found (0). Markdown and llms.txt earn 10. Purpose and limitations earn 20, typed question variants and explicit limits 15, and examples and errors 15. Versioned paths alone do not establish a public changelog (0). The docs now give the decision model's context window (131,072 tokens, with a fixed part reserved for answers). 0 + 10 + 20 + 15 + 15 + 0 = 60.

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.

Security & auth Microsoft-Decision-1.1 +7

Celeris-1 Decision 45

Revocable bearer keys earn 20. Workspace isolation earns 10 of 20 for least privilege, but no scoped inference permissions or per-key limits were found. No decision-specific prompt-injection mitigation found (0). Usage records and trace IDs earn 15. SOC 2 appears in enterprise marketing without a reviewed report or trust evidence, so no security-programme award (0). Security and privacy pages per the 9 October check. 20 + 10 + 0 + 15 + 0 = 45.

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.

Score by category

CategoryWeightCeleris-1 DecisionMicrosoft-Decision-1.1Edge
Reliability16%5050even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6043Celeris-1 Decision +17
Agent ergonomics13%8050Celeris-1 Decision +30
Security & auth14%4552Microsoft-Decision-1.1 +7
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4444even
Transparency & trust7%5534Celeris-1 Decision +21
Negative events≤15-20
TotalD 51/100E 44.8/100

Facts side by side

FactCeleris-1 DecisionMicrosoft-Decision-1.1
KindModel APIModel API
VendorCeleris (Marqo Inc)Microsoft
Hosted endpointhttps://inference.celeris.ai/celeris-1-decision/v1/systemoneno (local only)
TransportsHTTPHTTP
AuthAPI keyOAuth or key
PricingPay per usePay per use
Price for decision modelsfreefree
x402nono
LicenceProprietary hosted model under Celeris terms of serviceNot 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.
Read-only variant documentednono
llms.txtyesno
Last release2026-10-082026-11-17
Terms last updated2026-09-08no document linked
Privacy policy last updated2026-07-23no date given
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet

How the scores have moved

Verdicts

Celeris-1 Decision

Typed probabilities, image inputs and optional explanations suit routing and classification inside an agent, through System One or OpenAI Decisions request formats. The service is still early access under its terms, needs a card and prepaid credit, and moved to a 1.1 model name without a dated notice. The accuracy and latency figures are Celeris measurements.

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.

Before you call either

Celeris-1 Decision

  1. Send model: celeris-1.1-decision on the celeris-1-decision URL path. This model has no chat, Responses or models endpoint
  2. Use at most 512 questions per request, or 64 with explanations. Both endpoints reject streaming.
  3. Preserve x_celeris in a custom Jev SDK response model when reading explanations. The default response type drops it.
  4. Retry 429 with Retry-After and backoff. Stop on 402 until workspace credit is replenished.
  5. Read usage.input_tokens for cost, including images and request overhead. Track credit expiry separately from token consumption.

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

Questions

Which is better for AI agents, Celeris-1 Decision or Microsoft-Decision-1.1?

Celeris-1 Decision scores 51 (D) on agent readiness against Microsoft-Decision-1.1's 44.8 (E), and leads in 3 of 7 scored categories. Microsoft-Decision-1.1 leads on security & auth.

Which is cheaper for decision models, Celeris-1 Decision or Microsoft-Decision-1.1?

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

Do Celeris-1 Decision and Microsoft-Decision-1.1 need an API key?

Celeris-1 Decision needs an API key. Microsoft-Decision-1.1 takes an API key or an OAuth sign-in.

Can an agent call Celeris-1 Decision and Microsoft-Decision-1.1 without installing anything?

Celeris-1 Decision has a hosted endpoint at https://inference.celeris.ai/celeris-1-decision/v1/systemone. No hosted endpoint is listed for Microsoft-Decision-1.1.

Other comparisons with Celeris-1 Decision or Microsoft-Decision-1.1

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.