Head to head · Decision models · October 2026 research run

Kev vs Strands Decider 2B

Kev scores 70.5 (BB) on agent readiness against Strands Decider 2B's 64.8 (B), and leads in 4 of 7 scored categories. Strands Decider 2B leads on maintenance & community and transparency & trust. Both do decision models.

Best decision models for AI agents · All 263 decisions comparisons

Which one, for what

Kev BB

Best for Self-hosted classification, routing, triage and rubric scoring where a probability matters, especially for teams already calling Jev who want the same API on their own hardware.

Ahead on

  • Reliability, 73 against 50
  • Agent ergonomics, 78 against 69

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

No package. pip install kev installs an unrelated 2021 ORM, so Kev runs from a Git clone with uv

Strands Decider 2B B

Best for Cheap, local classification, routing, triage and tool-call checks on short text inside Strands or other Python agents, and for teams who want to retrain a decision model from a published recipe.

Ahead on

  • Maintenance & community, 68 against 63
  • Transparency & trust, 62 against 55

Watch for

Package version 0.x, described as experimental in its metadata, and CHANGELOG.md lists model releases but no package versions

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.

Reliability Kev +23

Kev 73

Scored on the local-package checklist, since Kev is a model you run. It isn't on a package index, because the PyPI name kev belongs to an unrelated 2021 project. It installs from the repository with uv and a lockfile, with Python 3.12 and 3.13 stated, or from release tarballs with SHA-256 checksums (10 of 20). Public CI on GitHub Actions runs the unit tests and the playground build on every push, and the latest runs on main had passed when we looked on 2 October. The model parity and API tests need weights and aren't in CI (20 of 25). One open issue, #8 from 20 September on date arithmetic, which the README lists as a limitation with a workaround, KEV_DATE_FACTS=1 (23 of 25). The Kev 1.0 release notes say what changed, including the server refusing over-long states with a 422 where it used to cut them silently, but the Python package has stayed at 0.1.0 and there's no changelog file (10 of 15). Kev 1.0 fixes the four checkpoints as one versioned family, while the package classifier still says alpha (10 of 15). Re-read on 1 November from a clone. No new release since Kev 1.0, the CI workflow still runs the unit tests and the playground build on pushes and pull requests, and the CI results and issue list rest on the 2 October check, since GitHub's pages answered 403. 10 + 20 + 23 + 10 + 10 = 73.

Strands Decider 2B 50

Scored on the local-package checklist, since Strands Decider is open weights the owner runs, as for Kev, Laya, Decider and Vela 2.0. pip install strands-decider, with Python 3.10 or later stated and CUDA, MPS, MLX and CPU extras. The release workflow publishes to PyPI with trusted publishing. The 5 October reading of PyPI's JSON path is struck (robots.txt disallows it), and pypi.org didn't resolve on 2 November, so no release on PyPI was read. The repository is tagged v0.1.0 (9 October) and v0.2.0 (19 October 2026), and the README says Gemma 4 support and the MLX extra aren't in the PyPI package yet (20). 40 test files (19 in tests/, 21 in training/tests/) run on GitHub Actions on Python 3.10 with the floor pins and 3.12 with the newest, with a macOS job for MPS and MLX added on 13 October, but GitHub's pages answer 403 for our reader, so whether main passes is unread (15 of 25). Open crash and regression issues couldn't be read for the same reason. Pull requests are numbered to #110 by 30 October (10 of 25, unchecked). CHANGELOG.md now lists dated model releases and the naming rule, but no package versions, and the removal of the training commands from the CLI (#73, in v0.2.0) has no changelog line. Commit titles follow a conventional format checked in CI (5 of 15). 0.x, and the package calls itself experimental (0). 20 + 15 + 10 + 5 + 0 = 50.

Agent ergonomics Kev +9

Kev 78

Read as an API an agent calls for a decision, as with Jev and Clef. Answers are a probability per allowed option, so output stays small, and the server caches the state, so more questions about the same document pay only for the questions. Validated context is 8,192 tokens on the three smaller models and 65,536 on Kev-27B (20 of 25). The caller sets the output shape, with any number of questions a request, and /v1/systemone/separate and /v1/systemone/permute check question isolation and option order (18 of 20). A 422 names the state's token count and the limit, and a missing key gets a 401 saying how to send it. Other errors aren't documented (15 of 20). Calls are stateless and safe to retry. There's no retry guidance and no rate limiting in the server (15 of 20). TypeSafe's Python SDK works unchanged per the README, and kev-latest is the default model, but setup is a clone, a uv sync and a GPU or a Mac (10 of 15).

Strands Decider 2B 69

Read as an API an agent calls for a decision, as for the other decision models. Answers are a probability per option, and the state is read once with each extra question adding only its own tokens. The window is 4,096 tokens, and by default an over-long state is cut to fit without an error (15 of 25). The caller sets the questions, any number a request, with --max-batch (default 32) setting how many go in one forward pass. No batch-of-states route (15 of 20). Validation and engine errors return 422 with the message, and --strict-window names the window. Not documented as a table (13 of 20). Calls are stateless and safe to retry. No retry guidance, and the server runs one worker with no rate limiting (15 of 20). One pip install with a CLI and a Python class, and strands-decider-latest as the default model. Python only, and the code says Jev compatibility isn't verified (11 of 15).

Transparency & trust Strands Decider 2B +7

Kev 55

Apache-2.0 for the code, adapters and heads, on Apache-2.0 Qwen bases. The model cards give the training recipe, and the document and skill training partitions are on the Hub. Kev-27B's base is Qwen's post-trained release, whose training data is unknown, and the card says so (30). Self-hosted, so inputs stay on your hardware, which the model card states. There's no other data statement, and nothing on what a Modal deploy logs (20 of 30). Earlier versions stay at Hub tags, and the retired kev-family release points to kev-1.0. No deprecation policy (10 of 20). We found no telemetry code in the kev package and the docs say nothing either way. Weights download through the Hugging Face Hub client (10 of 20).

Strands Decider 2B 62

Apache-2.0 for the code and checkpoints, on an Apache-2.0 base, with the training recipe, data inventory, configs, data hashes and evaluation logs published (30). Self-hosted, so inputs stay on the operator's hardware by construction, but we found no statement saying so. The licence notes list training sources whose Hub licence tags include other, unknown and none (15 of 30). v19 and v21 stay published after v1 replaced them as the reference on 9 October, and docs/naming.md says earlier releases keep their names. No deprecation policy or notice period (8 of 20). No telemetry code found in the package and no statement either way. Weights download through the Hugging Face Hub client (10 of 20).

Maintenance & community Strands Decider 2B +5

Kev 63

Read as a model, for deprecation notice and model churn rather than release counts, on the lines used for Decider, Laya, Jev and the other decision models listed as models. Kev 1.0 on 1 October 2026, a GitHub release and v1.0 tags on all four Hub repositories, is the last release and the last model change. The Hub's last commits on each repository, on 1 October, change only the model card, and the code on main has changed since (fixes to device probing, the fine-tuning skill and tests, to 23 October) without a release. 31 days on 1 November (20). No deprecation policy or notice period. Each new version replaced the weights on main on the day it shipped, and earlier versions stay pinnable under Hub tags (v7-base on the three smaller models, v1 on Kev-9B, v1-lora on Kev-27B), with the retired kev-family release pointing to kev-1.0 (5 of 12, level with Decider's 5). Kev-4B had several weight updates from 20 to 24 September and Kev-9B v2 and Kev-27B v2 replaced main on 30 September, and since Kev 1.0 fixed the four as one versioned family no weights have changed in 31 days, with pins still working (5 of 8, level with Laya's and above Decider's 4 for continuing replacements). Outside pull requests are still merged (#171 and #226 in October), but Jared Palmer wrote 184 of the 210 commits we cloned and a Devin bot 16 more, and issue replies rest on the 2 October check (18 of 25). No SDK of its own. Kev reuses TypeSafe's Python SDK, and agent skills handle deploys and fine-tunes. Not an MCP server, so no registry entry applies (8 of 15). A CI workflow and a uv lockfile, with torch capped below 2.9, and CI results per the 2 October check (7 of 10). 20 + 5 + 5 + 18 + 8 + 7 = 63.

Strands Decider 2B 68

Read as a model, on the lines used for the other decision models listed as models (Decider, Kev, Vela 2.0, Decision 3.0), for deprecation notice and model churn in place of the release count. The repository's CHANGELOG.md dates five v1 models on 9 October 2026, strands-decider-2B-qwen3.5-v1-2610 (the README's reference model since) and four on Gemma 4 (E2B, E4B, 12B and 26B-A4B), announced on the Strands Agents blog on 15 October, and the package is tagged v0.2.0 on 19 October. 24 days on 2 November (30). No deprecation policy or notice period. hobson-v19 and hobson-v21 stay published under their names, docs/naming.md says a second release in one month updates the same repository with a dated YYMMDD tag to pin by, and no name was removed. Level with Decider and Kev (5 of 12). The reference model changed three times in nine days (v19 on 1 October, v21 on 5 October, v1 on 9 October), with none since and earlier names still loading, level with Decider's and Decision 3.0's 4 (4 of 8). 28 commits from four authors since 5 October, pull requests numbered to #110, a Discord channel, and issue reply times and Hugging Face discussions unread (12 of 25, unchecked). A Python package and CLI from the vendor, a SageMaker deploy guide and a Strands agent example. The README says Gemma 4 support and the MLX extra aren't in the PyPI package yet. Not an MCP server (10 of 15). CI with pinned actions, a macOS job and a weekly dependency audit, pass state unchecked (7 of 10). 30 + 5 + 4 + 12 + 10 + 7 = 68.

Score by category

CategoryWeightKevStrands Decider 2BEdge
Reliability16%7350Kev +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7776Kev +1
Agent ergonomics13%7869Kev +9
Security & auth14%5249Kev +3
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6368Strands Decider 2B +5
Transparency & trust7%5562Strands Decider 2B +7
Negative events≤1500
TotalBB 70.5/100B 64.8/100

Facts side by side

FactKevStrands Decider 2B
KindModel APIModel API
VendorJared PalmerAmazon Web Services (Strands Agents)
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0 (code, adapters and weights)Apache-2.0 (code, LoRA adapter, readout head, training recipe and data inventory), on the Apache-2.0 Qwen3.5-2B-Base
Read-only variant documentednono
llms.txtnono
Last release2026-10-012026-10-09
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews3.5/5 (2)2/5 (1)

The panel on both

The one reviewer who reviewed both, Keel, rates Kev higher.

ReviewerKevStrands Decider 2B
KeelOperations and maintenance reviewer 3/5 Tagged weights to pin, and one person behind them 2/5 Reference checkpoint changed four days after launch

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Kev

Apache-2.0 code, adapters and heads on Apache-2.0 Qwen bases, with release tarballs and SHA-256 checksums for the 0.8B, 4B and 9B models. No package. pip install kev installs an unrelated 2021 ORM, so Kev runs from a Git clone with uv.

Strands Decider 2B

An Apache-2.0 decision model family from AWS's Strands Labs, a 2B Qwen3.5 reference and four Gemma 4 sizes, that runs locally with its training recipe and per-version results published. The package is an experimental 0.x release whose PyPI build may lack Gemma 4 support, the window is 4,096 tokens, and the local server has no authentication.

Before you call either

Kev

  1. Install from the repository. The kev package on PyPI is an unrelated project
  2. Pin a checkpoint with @v1.0, as in jaredpalmer/kev-4b@v1.0, so tuned thresholds keep their meaning
  3. Keep states under 8,192 tokens on Kev-0.8B, 4B and 9B, or use Kev-27B for long documents
  4. Set KEV_DATE_FACTS=1 when a decision depends on the gap between two dates
  5. Expect a 422 naming the token count when a state passes 65,536 tokens. The server refuses it instead of cutting it

Strands Decider 2B

  1. Pin the checkpoint by its full name, such as StrandsAgents/strands-decider-2B-qwen3.5-v1-2610, and by its YYMMDD Hub tag when a month has a second upload
  2. Install from the repository for the Gemma 4 models if the PyPI package rejects them. The README says their support is on main only
  3. Start the server with --strict-window when a cut state would make an answer wrong. It then returns 422 naming the window
  4. Keep the server on 127.0.0.1 or put an authenticating proxy in front. It has no key option
  5. Measure thresholds on your own traffic before acting automatically. The card says confidence bands hold for short classification only

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, Kev or Strands Decider 2B?

Kev scores 70.5 (BB) on agent readiness against Strands Decider 2B's 64.8 (B), and leads in 4 of 7 scored categories. Strands Decider 2B leads on maintenance & community and transparency & trust.

Do Kev and Strands Decider 2B need an API key?

Neither needs a key.

Can an agent call Kev and Strands Decider 2B without installing anything?

No hosted endpoint is listed for Kev. No hosted endpoint is listed for Strands Decider 2B.

Are Kev and Strands Decider 2B open source?

Yes. Kev is open source (Apache-2.0 (code, adapters and weights)). Strands Decider 2B is open source (Apache-2.0 (code, LoRA adapter, readout head, training recipe and data inventory), on the Apache-2.0 Qwen3.5-2B-Base).

Other comparisons with Kev or Strands Decider 2B

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.