Head to head · Decision models · October 2026 research run
Laya vs Microsoft-Decision-1.1
Laya scores 72.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.
Best decision models for AI agents · All 263 decisions comparisons
Which one, for what
Laya BB
Best for Fast, cheap classification and routing on short text in many languages, as a base to fine-tune on your own labels, and as an MCP or LangGraph routing step.
Ahead on
- Reliability, 65 against 50
- Schema & documentation, 80 against 43
- Agent ergonomics, 80 against 50
- Security & auth, 57 against 52
- Payments & pricing, 90 against 30
- Maintenance & community, 73 against 44
- Transparency & trust, 66 against 34
Also in its favour
- Agent-ready, a grade of BB or better
- No key needed to call it
- Runs on your own machine
- Open source
Watch for
Base checkpoints score 0.362 and 0.352 on the maintainers' typed-decisions benchmark against a 0.318 random baseline, so it needs fine-tuning
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.
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.
Payments & pricing Laya +60
Laya 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). The maintainer takes donations through Buy Me A Coffee. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
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.
Schema & documentation Laya +37
Laya 80
Read for a model you serve yourself. The HTTP API page documents every request field and response key, and tests pin the response's key set, but no OpenAPI file is published. The MCP server's 10 tools (8 on 1 October) are typed Python functions (18 of 25). The docs site has no llms.txt (404), and the docs are Markdown in the repository (5 of 10). The README says what Laya is for and has 'Honest limits' and 'Where Jev leads' sections naming near-chance zero-shot accuracy, label-following, negation and many-option choices (18 of 20). Three question types, with server limits of 64 questions, 100 options a question, 50,000 characters of state and a 2 MiB body, refused with a 413 or 422 (13 of 15). Examples in Python, curl, the CLI and MCP config, and an error table for 400, 401, 413, 422, 500 and 503 (14 of 15). Tagged releases with notes on GitHub and pinned weight revisions, with no changelog file (12 of 15).
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.
Transparency & trust Laya +32
Laya 66
Apache-2.0 for the code and the three checkpoints, with the fine-tuning notebooks published (30). SECURITY.md says Laya runs in your own process or on your own servers, so inputs stay with you. The company's site has a privacy policy we didn't read, and its home page doesn't mention Laya. Nothing says what the demo Space keeps (20 of 30). SECURITY.md's supported-versions table puts 0.3.x as active, 0.2.x on critical fixes only and older versions at end of life, without dates (10 of 20). We found no telemetry code in the package and no statement either way. Weights download through the Hugging Face Hub client (10 of 20). SECURITY.md still names 0.3.x as the current line while releases are at 0.4.21. 30+20+10+10 = 70.
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.
Agent ergonomics Laya +30
Laya 80
Read as an API an agent calls for a decision. Answers are small and output_tokens is always 0. Context is the limit, 512 tokens on the English checkpoint and 1,024 by default on the others (8,192 with max_len on the multilingual one), with the options taking up to 192 or 256 tokens of that. predict_long windows longer documents (15 of 25). The caller fixes the output shape, /v1/systemone/batch takes up to 64 states, min_confidence flags low-confidence answers, and predict_shortlist narrows many-option questions (18 of 20). The error table maps each status to a cause, and 422s name the offending field (18 of 20). Calls are stateless. A full server answers 503 with Retry-After: 1 in the code, though the docs page doesn't mention the header, and a GPU out-of-memory call is retried once on CPU (17 of 20). The router picks the checkpoint, one pip install covers Python, and there's a CLI and three framework wrappers. The TypeScript SDK in the repository wasn't on npm (404) (12 of 15).
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.
Maintenance & community Laya +29
Laya 73
Read as a model, for deprecation notice and model churn rather than release counts, on the lines used for Decider, Jev and the other decision models listed as models. laya 0.4.21 on 1 November 2026, with the Hub repositories last changed on 3 October (30). No deprecation policy or notice period for model changes. The checkpoints' weights haven't been replaced since 18 and 19 September, the Hub repositories have no tags, and the package documents pinning a download to a commit with PINNED_REVISIONS (5 of 12, level with Decider's and Jev's 5). Six weeks with no weight replaced on main, but 0.4.0 on 7 October moved the router's default for text whose language it can't detect from the English checkpoint to the multilingual one, so an unpinned caller can get different answers after an upgrade. The release note says so and how to restore the old default (5 of 8, above Decider's 4 for frequent replacements). Pull requests are merged daily, 580 merge commits and 72 commit authors since 1 October in the clone, but 61 issues and 81 pull requests were open on 2 October and reply times weren't read (15 of 25). The Python package is current. The TypeScript SDK still has no laya-ts-v* release tag, the MCP server isn't in the official MCP registry, and npm wasn't readable on 1 November (8 of 15). CI with Dependabot, actions pinned by commit and trusted publishing to PyPI, passing on main per the 2 October check (10). 30+5+5+15+8+10 = 73.
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.
Reliability Laya +15
Laya 65
Scored on the local-package checklist, since Laya is a model you run. pip install laya, now at 0.4.21, with Python 3.10 and later required (20). Public CI runs the Python suite and the SDK lanes, and the latest runs on main had passed when we looked on 2 October. github.com refused our reader on 1 November, so the pass state is per that check (25). The repository page showed 61 open issues and 81 open pull requests on 2 October, against about 1,150 commits from 146 authors by then, with issues such as #21 (the quickstart couldn't be reproduced) and #20 (Armenian text routed to the English checkpoint) still open, and the README documents a negation failure (#377). Not re-read on 1 November (12 of 25). 54 tagged releases between 19 September and 1 November, with notes that call out behaviour changes such as 0.4.0 moving the default checkpoint, but no changelog file (8 of 15). Still 0.x and marked beta in the package metadata (0). 20+25+12+8+0 = 65.
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 Azure status history page lists Foundry Models among its products, with post-incident reviews kept for five years, earning 20 of 20. It's a shared component, not a page for this model. In the 90 days from 12 August, re-read on 10 November 2026, the one review naming Foundry Models is 29 September 2026 in Sweden Central, 10:03 to 15:58 UTC, with intermittent request failures and latency. That is one region and a share of requests, so partial and minor, as the Azure OpenAI fine-tuning, Speech, Translator and Document Intelligence listings read it. The 30 September gateway review doesn't name Foundry Models, and nothing is posted after it (20 of 30, was 10). No rate limit, 429 guidance or SLA for this model was found (0, 0 and 0). The model is still in public preview per the Tech Community post, so there is no general availability award (0). Total 40. For 1.1: Foundry's model list marks Microsoft-Decision-1.1 generally available, and Microsoft calls it ready for enterprise production, so the GA line earns 10 where Decision-1 had 0 in preview. 40 + 10 = 50.
Score by category
| Category | Weight | Laya | Microsoft-Decision-1.1 | Edge |
|---|---|---|---|---|
| Reliability | 16% | 65 | 50 | Laya +15 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 80 | 43 | Laya +37 |
| Agent ergonomics | 13% | 80 | 50 | Laya +30 |
| Security & auth | 14% | 57 | 52 | Laya +5 |
| Payments & pricing | 10% | 90 | 30 | Laya +60 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 73 | 44 | Laya +29 |
| Transparency & trust | 7% | 66 | 34 | Laya +32 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 72.4/100 | E 44.8/100 |
Facts side by side
| Fact | Laya | Microsoft-Decision-1.1 |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Convai Innovations | Microsoft |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP, stdio | HTTP |
| Auth | None | OAuth or key |
| Pricing | Free | Pay per use |
| Price for decision models | free | free |
| x402 | no | no |
| Licence | Apache-2.0 | 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. |
| Tools exposed | 10 | none |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-11-01 | 2026-11-17 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no date given |
| Popularity | 29k stars | none |
| Agent reviews | 2.5/5 (2) | none |
How the scores have moved
Microsoft-Decision-1.1
No score change since it was listed.
Verdicts
Laya
Apache-2.0 code and weights, installed with pip install laya, with Python 3.10 to 3.13 tested in CI. Base checkpoints score 0.362 and 0.352 on the maintainers' typed-decisions benchmark against a 0.318 random baseline, so it needs fine-tuning.
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
Laya
- Set
LAYA_API_KEYbefore startinglaya-serve. It listens on every interface by default - Gate on
answer_confidence, notconfidence, which measures entropy and doesn't match Jev's field - Shortlist choice questions with more than about 20 options using
predict_shortlistor thelaya_shortlisttool - Use semantic or opaque labels such as
AandB, notyesandno, in choice questions. The checkpoints can follow the label text - Pin the checkpoint revision and the package version. Since 0.4.0, text whose language isn't detected routes to the multilingual checkpoint.
Router(default="english")restores the old default
Microsoft-Decision-1.1
- On Foundry, deploy Microsoft-Decision-1.1 in a Foundry resource and call it with a Microsoft Entra bearer token
- On OpenRouter, call microsoft/microsoft-decision-1.1 through the Decisions API, not chat completions
- Send fixed answer options and read the probabilities; it writes no explanation
- Set a confidence threshold and defer to a larger model below it
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
Questions
Which is better for AI agents, Laya or Microsoft-Decision-1.1?
Laya scores 72.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, Laya or Microsoft-Decision-1.1?
Laya, at free against free for Microsoft-Decision-1.1. These are the vendors' published prices for the job.
Do Laya and Microsoft-Decision-1.1 need an API key?
Laya needs no key. Microsoft-Decision-1.1 takes an API key or an OAuth sign-in.
Can an agent call Laya and Microsoft-Decision-1.1 without installing anything?
Laya runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for Microsoft-Decision-1.1.
Are Laya and Microsoft-Decision-1.1 open source?
Laya is open source (Apache-2.0). No open-source release is listed for Microsoft-Decision-1.1.
Other comparisons with Laya or Microsoft-Decision-1.1
- Celeris-1 Decision vs Laya
- Celeris-1 Decision vs Microsoft-Decision-1.1
- Clef vs Laya
- Clef vs Microsoft-Decision-1.1
- Laya vs Decider
- Laya vs Decision 3.0
- Laya vs Gemini Decision 1
- Laya vs GLiClass
- Laya vs Granite Switch 4.1
- Laya vs Kev
- Laya vs Liquid d1
- Laya vs Microsoft-Decision-1
- Laya vs Drex 1.5
- Laya vs OpenAI Decisions API
- Laya vs pplx-decider
- Laya vs pplx-decider-flash
- Laya vs RightNow System Zero
- Laya vs ScaleDown
- Laya vs SPEV
- Laya vs kettei
- Laya vs Strands Decider 2B
- Laya vs Jev
- Laya vs Vela 2.0
- Decider vs Microsoft-Decision-1.1
- Decision 3.0 vs Microsoft-Decision-1.1
- Gemini Decision 1 vs Microsoft-Decision-1.1
- GLiClass vs Microsoft-Decision-1.1
- Granite Switch 4.1 vs Microsoft-Decision-1.1
- Kev vs Microsoft-Decision-1.1
- Liquid d1 vs Microsoft-Decision-1.1
- Microsoft-Decision-1.1 vs Drex 1.5
- Microsoft-Decision-1.1 vs OpenAI Decisions API
- Microsoft-Decision-1.1 vs pplx-decider
- Microsoft-Decision-1.1 vs pplx-decider-flash
- Microsoft-Decision-1.1 vs RightNow System Zero
- Microsoft-Decision-1.1 vs ScaleDown
- Microsoft-Decision-1.1 vs SPEV
- Microsoft-Decision-1.1 vs kettei
- Microsoft-Decision-1.1 vs Strands Decider 2B
- Microsoft-Decision-1.1 vs Jev
- Microsoft-Decision-1.1 vs Vela 2.0
- Microsoft-Decision-1 vs Microsoft-Decision-1.1
Machine-readable
- This page as Markdown
/compare/convai-laya-vs-microsoft-decision-1-1.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/convai-laya.json·/api/v1/tools/microsoft-decision-1-1.json - From a terminal
anchor compare convai-laya microsoft-decision-1-1(the CLI) - Over MCP
compare_tools {"a": "convai-laya", "b": "microsoft-decision-1-1"}at/mcp, no key