Decision Tier

Evidence Checked October 12, 2026

Landscape, October 2026

Decision models went from one vendor to a crowded field in about a month. Here's what changed since our benchmark runs in early October: the Claude lineup, OpenAI's Decisions API, and the open-weight models that, by their own published numbers, may no longer be mid.

Provenance. Our own measurements are on Four ways compared. Everything on this page comes from vendor documentation, release notes, public leaderboards and press as of October 12, 2026, and we haven't reproduced it. Vendor benchmark claims are marked as claims. The field changes daily.

The Claude lineup

Three new Claude models shipped in the last four weeks. All have a 1M-token context window and up to 128K output tokens.

ModelIDReleasedInput / output per M tokensRole in a cascade
Claude Fable 5.1claude-fable-5-1Sept 1, 2026$10 / $50The hardest escalations: long-horizon audits, novel failures
Claude Opus 5.5claude-opus-5-5Sept 22, 2026$4 / $20The default LLM tier: inspect, decide, fix the cause below. Cheaper than Opus 5 ($5 / $25)
Claude Sonnet 5.5claude-sonnet-5-5Sept 28, 2026$2 / $10A cheaper LLM tier for routine escalations and plan audits
Claude Haiku 5.5claude-haiku-5-5Oct 7, 2026$0.10 / $0.50 (≤100K-token prompts)A judgment tier, or the watch-band reviewer. Anthropic positions it for classification, extraction and routing

Jev: unchanged

OpenAI: Decisions API and Luna

Open weights: have they gotten better?

By the published numbers, yes, noticeably. In our early-October runs, the open options (APUS-OpenJev-4B, Strands Decider 2B) sat clearly below Jev. Since then:

ModelReleasedWhat's newReported result
Strands Decider, Gemma 4 family (E2B, E4B, 12B, 26B-A4B)Oct 9Apache-2.0; also a new 2B reference model. Gemma 4 support is on GitHub main, not yet on PyPIJevBench public: 180, 187, 200, 207 / 231 (Jev: 200). Median latency 102–245 ms on an H100
APUS-OpenJev-v1 9B and 35B-A3B~Sept 23New sizes beside the 4B we tested; GGUF and MLX 4-/8-bitNot yet on our harnesses
Cloudflare Clef (27B) and Clef-flash (9B)Oct 1Apache-2.0; text, JSON, images and video in; also hosted on Workers AIVendor claims wins over Jev on several tasks (not independently replicated)
H2O-Lightning-4Bv1.2.3, Oct 10Apache-2.0, Qwen3.5-4B base, takes imagesVendor claims JevBench v1.6.1 composite 72.5 against Jev's 71.5
Liquid AI d1-3B, d1-omni-600MOct 7Text and images (omni: audio, experimental)Vendor claims 8 ms on an RTX 4090; made for edge devices

What it takes to run them

The models that beat Jev on JevBench are big. Before you plan on "free," check what the hardware costs. A model's weights take roughly parameters × bytes per parameter: 2 bytes at BF16, 1 at 8-bit, 0.5 at 4-bit. Then add a few GB for the KV cache and the runtime. These are rule-of-thumb estimates, not measurements:

Model class4-bit8-bitBF16Realistic hardware
2B–4B (Decider 2B, APUS 4B, H2O-Lightning-4B, Gemma 4 E2B/E4B)1–2 GB2–4 GB4–9 GBAny recent laptop
9B–12B (APUS 9B, Decider 12B)5–7 GB9–13 GB18–24 GBA 16–24 GB laptop if quantized; BF16 wants a 24–32 GB GPU
26B-A4B mixture-of-experts (Decider 26B)~14 GB~27 GB~52 GBAll 26B must sit in memory even though only ~4B work per token, so it's fast once it fits. A 24 GB GPU at 4-bit; a 48 GB+ machine at 8-bit; an 80 GB GPU at BF16 (Strands' latency figures are from an H100)
31B dense (the top of the Capability board)~17 GB~33 GB~62 GBEvery parameter works on every token, so it's several times slower per request than a 4B. A 24 GB GPU or a 32 GB+ Mac squeezes 4-bit; a 48 GB card (L40S, A6000) or a 64 GB Mac for 8-bit; an 80 GB H100 for BF16
35B-A3B mixture-of-experts (APUS 35B)~19 GB~37 GB~70 GBLike the 26B, but larger: a 32 GB+ machine at 4-bit

The JevBench Capability board

JevBench v1.6.1's live board (October 12) lists Jev 1.13.0 as the unranked reference at Capability 77.1 (Calibration 90.6). The top open models:

RankModelSizeCapability
1Quyet-1.0-Large31B81.7
2decisio v0.8.0 (Gemma 4 31B)31B79.6
3deck-31B31B77.6
4René-1 31B FP831B76.0
5H2O-Lightning-4B v1.14B75.0
—Jev 1.13.0 (reference)—77.1

Source: benchmarkheaven.com/jev-models; harness at github.com/fstandhartinger/jevbench.

How to read this

JevBench is a public benchmark, and public sets leak into training. Our own lesson was that benchmark wins didn't predict mail wins: the 2B decider tied Jev on several JevBench families and still trailed it badly as a sorter feature source. A 31B model is also not a laptop model: see what it takes to run them. The honest next step is to run the Gemma 4 Decider 12B/26B and APUS 9B through the same wine, mail and page harnesses. The Decision Skeleton makes that a one-module job: swap the backend, re-run the eval.

Other entrants and the emerging standard

What this changes in our advice

  1. Write against the /v1/systemone shape and keep backends swappable. The cost of switching is now an eval run, not a rewrite.
  2. Re-test open weights before calling them mid. If a 12B–26B open model matches Jev on your data, privacy and zero marginal cost become free wins.
  3. Haiku 5.5 changed the "small LLM" math. At $0.10 / $0.50, the price gap to decision models is now 5–7×, not 50×. Repeatability, latency and calibration, not price, are the reasons to prefer a decision model.
  4. Pin what you can. More vendors means more silent model updates. Thresholds belong to a (model, runtime, rubric) triple.