Place an item on an ordered scale
Four or more companies' docs show a full fit.
What counts as done
A probability per level and an expected score.
Measured, for our own tests: the chosen reading places at least 85 percent of the caller's labelled items in the right level and no critical item below the urgent cut. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: how urgent is this
, what fraud risk level is this transaction
, rate this on a 1 to 5 rubric
, how severe is this incident
Does the job 17
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Celeris-1 Decision D Marqo Inc | score returns a probability per level, the probability-weighted average level and a legend, up to 64 levels. Thresholding guidance is generic. source |
| Clef B Cloudflare, Inc. | score questions over ordered options return a probability per option. No threshold guidance from Cloudflare. source |
| Decider BB Mark Marosi (Mapika) | score over 2 to 10 described levels returns a probability per level and the expected level, with a fitted temperature per answer type. source |
| Decision 3.0 B vLLM Semantic Router project | score questions return a probability per level; the readout temperature is 1.0 with no calibration figure. source |
| elephant-1 D Baseten Labs, Inc. | score over 2 to 10 ordered levels returns a probability per level and the expected level; a Brier term in training discourages overconfidence. source |
| joey-1 C Baseten Labs, Inc. | score over 2 to 10 ordered levels returns a probability per level and the expected level; a Brier term in training discourages overconfidence. source |
| Liquid d1 C Liquid AI, Inc. | score returns the probability-weighted position and a probability per level; the guide's scoring and reranking examples set thresholds on the probabilities. source |
| mammoth-1 D Baseten | score over 2 to 10 ordered levels returns a probability per level and the expected level; a Brier term in training discourages overconfidence. source |
| Microsoft-Decision-1 E Microsoft | score over ordered levels returns an expected score and probabilities; Learn says to validate on your own labelled examples and prefer scores for ordering and thresholds over absolute ratings. source |
| Drex 1.5 BB Nace AI, Inc. | score returns the expected score, a legend, a probability per level and confidence; levels are the criteria array in order. source |
| OpenAI Decisions API A OpenAI OpCo, LLC | score over 2 to 10 ordered levels returns the probability-weighted average level, probabilities and confidence. source |
| pplx-decider BB Perplexity AI, Inc. | score over up to 10 levels returns the probability-weighted score, legend and probabilities; confidence formula is documented. source |
| pplx-decider-flash B Perplexity AI, Inc. | score over up to 10 levels with expected score, legend and probabilities; same documented confidence formula. source |
| ScaleDown E Carbon ScaleDown, Inc. | score over 2 to 10 levels returns the probability-weighted expected value and a probability per level, with the calculation worked through in the docs. source |
| SPEV D Sprag AI, Inc. | score over 2 to 10 levels returns the expected level, probabilities and confidence; vendor figures only. source |
| kettei C Sqwish Ltd, trading as Sqwish Labs | ordinal decisions over 2 to 255 levels with a rubric line each return probabilities and expected_level. source |
| Jev B TypeSafe AI, Inc. | score with probabilities per level, expected score and confidence, plus confidence-routing guidance for answers split across levels; fraud triage on 100 transactions and routing on 80 prompts ran against Strands with Jev stronger on fraud. source |
Does the job, with a limit 8
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Laya BB Convai Innovations Pvt. Ltd. | score questions are supported in one pass at 33 ms, with answer_confidence to gate on, but issue 131 reports laya-multilingual never selecting the first-listed score option and calibration error is high. source |
| Drex Max v1 C Nace AI, Inc. | score over ordered levels with expected score and probabilities. Vendor figures only; licence cap. source |
| Granite Switch 4.1 B International Business Machines Corporation | Ordered labels can be scored, but there is no score type, legend or expected level; the caller derives them from label logprobs. source |
| Kev BB Jared Palmer | score over 1 to 255 levels with expected level and probabilities; issue 161 measured a slot-0 logit offset on identical score options, fixed in PR 236, so pin v1.0 or later weights. source |
| JEV-27B-VL C AutoTrust AI Lab | Rate 0 to 5 on text and images with a probability per level; vendor figures only. source |
| RightNow System Zero B RightNow AI, Inc. | score returns an expected level, legend and probabilities, flagged uncalibrated. source |
| Strands Decider 2B B Amazon Web Services, Inc. | score with expected level and probabilities; fraud triage scored 61 of 100 matching words in option descriptions, and the card says confidence bands hold for short classification only. source |
| Vela 2.0 BB vLLM Semantic Router project (with KR Labs) | score over 2 to 10 levels returns the expected level and distribution; USAGE.md says Choice and Score confidence are distribution statistics, not calibrated probabilities. source |
1 listings in the category were added after this reading and aren't marked yet.
What stops agents finishing
- expected score rounds a critical item into a lower queue when probability is spread
- a one-point rubric cutoff hides borderline cases
Around it
Before: support.fetch-ticket, payments.fetch-transaction. After: support.set-priority, human-review.
Where this comes from
Weight 8 of 100 in Decision models: 4 of 41 accounts; the AWS fraud and delivery tests, the Kev score-order issue and the Dataiku score threshold finding
The same as data: /api/v1/use-cases/decision-models.score-rubric.json, or the MCP tool get_use_case with id decision-models.score-rubric. Other jobs in this category: /api/v1/niches?category=decision-models.
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.