Get an audit

Head to head · Decision models · October 2026 research run

Decider vs Decision 3.0

Decider scores 69.5 (B) on agent readiness against Decision 3.0's 63.1 (B), and leads in 5 of 7 scored categories. Decision 3.0 leads on security & auth. Both do decision models.

Best decision models for AI agents · All 105 decisions comparisons

DeciderMark Marosi (Mapika) · Model API B69.5/100#183 of 965 Decision 3.0vLLM Semantic Router Team · Model API B63.1/100#413 of 965

Which one, for what

Decider B

Best for Local classification, routing, triage and checks where a team wants open weights in several sizes and a Jev-shaped route.

Ahead on

  • Reliability, 90 against 58
  • Schema & documentation, 78 against 70
  • Agent ergonomics, 80 against 72
  • Maintenance & community, 87 against 82

Watch for

The local server has no authentication option. It binds to 127.0.0.1 since 1.7.1

Decision 3.0 B

Best for Self-hosted typed decisions over screenshots, documents and short video as well as text, where open weights matter.

Ahead on

  • Security & auth, 56 against 38

Watch for

Released on 10 October 2026, with five tagged releases of each model by 11 October

Score by category

CategoryWeight this runDeciderDecision 3.0Edge
Reliability16%209058Decider +32
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27870Decider +8
Agent ergonomics13%16.28072Decider +8
Security & auth14%17.53856Decision 3.0 +18
Payments & pricing10%12.56060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88782Decider +5
Transparency & trust7%8.84645Decider +1
Negative events≤1500
TotalB 69.5/100B 63.1/100

Facts side by side

FactDeciderDecision 3.0
KindModel APIModel API
VendorMark Marosi (Mapika)vLLM Semantic Router Team
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0 (code and weights)Apache-2.0 for the weights and the bundled runtime, built on Apache-2.0 Qwen3.5 and Qwen3.8 bases
Read-only variant documentednono
llms.txtnono
Last release2026-10-072026-10-11
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Popularity1.1k stars, 2.7k PyPI/wknone

Verdicts

Decider

An Apache-2.0 decision model family with a dated changelog, passing CI, 21 package releases since 22 September 2026 and model cards that list measured regressions. One person maintains it, the local server has no authentication option, states over 32,768 tokens are cut without an error, and no security policy is published.

Decision 3.0

Open Apache-2.0 decision models that read images and video as well as text and answer several typed questions in one call, with a probability per option and tagged Hub releases. They are two days old, need a GPU and trust_remote_code, drop Vela's set and span types, and publish no calibration figures.

Before you call either

Decider

  1. Pin weights by Hub tag (v10, v2) when results must repeat. The main branch of each model repository changes with new versions
  2. Read x_p_max for the top probability. Since 1.3.0 confidence on choice and score answers follows TypeSafe's rescaled definition, not the top probability
  3. Keep the server on 127.0.0.1 or put an authenticating proxy in front. It has no key option
  4. Count state tokens before sending. Over 32,768 the state is cut silently, and /decide caps context at 1,536 tokens
  5. Split multi-step arithmetic or multi-hop judgements into several questions, and don't write long rules into a question. The README says both fail

Decision 3.0

  1. Pin a tag or commit with revision= when loading from the Hub. Each model had five tagged releases on 10 and 11 October
  2. Send images and videos to d3_server.py as base64 data URLs only. The server refuses paths and http URLs with 422
  3. Set DECISION_API_KEY before binding the bundled server beyond 127.0.0.1. It is open otherwise
  4. Turn on permutation_average=True when routing must not depend on option order. It is off by default
  5. Expect one request at a time from the bundled server. Use the router's model runtime for queued serving

Questions

Which is better for AI agents, Decider or Decision 3.0?

Decider scores 69.5 (B) on agent readiness against Decision 3.0's 63.1 (B), and leads in 5 of 7 scored categories. Decision 3.0 leads on security & auth.

Do Decider and Decision 3.0 need an API key?

Neither needs a key.

Can an agent call Decider and Decision 3.0 without installing anything?

No hosted endpoint is listed for Decider. No hosted endpoint is listed for Decision 3.0.

Are Decider and Decision 3.0 open source?

Yes. Decider is open source (Apache-2.0 (code and weights)). Decision 3.0 is open source (Apache-2.0 for the weights and the bundled runtime, built on Apache-2.0 Qwen3.5 and Qwen3.8 bases).

Other comparisons with Decider or Decision 3.0

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.

Get an auditSee a sample report