Head to head · Decision models · October 2026 research run
Clef vs Strands Decider 2B
Clef scores 68.3 (B) on agent readiness against Strands Decider 2B's 64.8 (B), and leads in 5 of 7 scored categories. Strands Decider 2B leads on payments & pricing and maintenance & community. Both do decision models.
Best decision models for AI agents · All 263 decisions comparisons
Which one, for what
Clef B
Best for Classification, routing and rubric scoring over text, JSON and images inside Cloudflare, with audio and video through Clef-omni, or self-hosted where data can't leave.
Ahead on
- Reliability, 68 against 50
- Agent ergonomics, 75 against 69
- Security & auth, 72 against 49
- Transparency & trust, 87 against 62
Also in its favour
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch for
Hosted Clef-flash's context fell from 64K to 24K tokens on 9 October 2026, announced in the changelog the day it took effect
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
- Payments & pricing, 90 against 60
- Maintenance & community, 68 against 59
Also in its favour
- No key needed to call it
- Open source
- No incidents deducted, where Clef loses 3 points for them
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.
Payments & pricing Strands Decider 2B +30
Clef 60
No x402, MPP or L402 on Workers AI (0). Per-token prices published without a login, $0.24 per million input tokens for Clef, $0.038 for Clef-flash and $0.15 for Clef-omni, with neurons at $0.011 per 1,000 (20). Workers AI includes 10,000 neurons a day on the Free plan, and Cloudflare's Free plan needs no card per the 30 September check (20). The hosted route needs a person to sign up in a browser. The weights download from Hugging Face without an account, but other open-weight listings get no onboarding credit for that, so Clef doesn't either (0). Prices re-read on the pricing page (last updated 20 October 2026) on 1 November, and Machine Payments on POST /ai/run still lists four other models. 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Strands Decider 2B 90
Free Apache-2.0 software with nothing to buy, so 20 + 20 + 20 for pricing, free use and no sign-up, by the self-hosted rule. No payment protocol (0). No hosted API was found, on Amazon Bedrock or elsewhere, so there's no hosted option to grade. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Transparency & trust Clef +25
Clef 87
Weights and scoring code under Apache-2.0, following the Qwen base models. Training code and data aren't published (27 of 30). The Workers AI data page and the launch post agree, no training without consent and nothing kept unless you store it. Cloudflare's privacy policy and DPA exist, per the Cloudflare MCP check (26 of 30). The Workers AI changelog posts dated notices, such as the 8 May notice for Kimi K2.5, but we found no deprecation policy (10 of 20). Cloudflare's subprocessor page names 12 third parties and 16 group companies with locations, per the Cloudflare MCP check of 1 October. Where Clef inference runs isn't stated (14 of 20). Clef-omni is Apache-2.0 on its Hugging Face card, and we didn't check whether it publishes training code or data. The churn point sits under maintenance, so the deprecation item stays at 10 of 20. Hugging Face still shows all three models under apache-2.0 on 1 November. 27 + 26 + 10 + 14 = 77.
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).
Security & auth Clef +23
Clef 72
Read for a model API. Cloudflare API tokens scoped to Workers AI permissions on an account and revocable, per the Cloudflare MCP listing's check of 1 October. Permission is per account, not per model (27 of 30). The Workers AI data page (updated 16 October 2026, per the Clairic listing's 1 November check) says standard inference keeps no inputs or outputs after the response and Customer Content isn't used to train models, and the launch post says Cloudflare doesn't read, store or train on Clef requests or responses outside the fine-tuning service (18 of 20). Clef is pitched at support triage and threat intelligence, both untrusted input, and we found no guidance on adversarial or injected content in the model page, the launch post or the model card. Self-hosting runs custom code from the model repository (3 of 15). The launch post's fine-tuning flow captures datasets through AI Gateway, and gateway logs record each request when one is used. Account audit logs record token changes per the Cloudflare MCP check (6 of 15). security.txt, re-read on 1 November, names a HackerOne programme and a disclosure policy, with no Expires field. Cloudflare's ISO certifications page, read on 1 November, says Cloudflare is certified to ISO 27001 (since 2019, now to its 2022 edition), ISO 27018 and ISO 27701, with a scope of the Cloudflare global cloud platform. 2 held back for the missing Expires field, as cloudflare-clairic, cloudflare-r2, cloudflare-workers-ai and cloudflare-ai-gateway read the same evidence (18 of 20, 15 before, when certifications went unread). Clef-omni widens user-supplied input to audio and video, and Cloudflare publishes no guidance on hostile media. 27 + 18 + 3 + 6 + 18 = 72.
Strands Decider 2B 49
Read as a model you run yourself, on the model lines as Kev and Vela 2.0 are read. No account. The server binds to 127.0.0.1 and has no authentication option, and the README says to start on your own machine and deploy the server when others need it (8 of 30). Self-hosted, so requests stay on the operator's hardware and nothing reaches AWS, and the server code has no request logging, but no page says so, where Kev's cards and Vela 2.0's runtime reference state it (15 of 20, against their 18). The model card warns that questions are read less than documents and that calibration holds only on short classification, and the 15 October post says to track inputs and outputs for decisions that block actions. Nothing documents how hostile text in the state can steer an answer, though the launch example uses it as a tool-call guardrail (6 of 15). Each response carries token usage and latency, and /health reports the checkpoint and device. No request log (5 of 15). SECURITY.md routes reports to the AWS Vulnerability Disclosure Program on HackerOne or aws-security@amazon.com. A weekly pip-audit, dependency review on pull requests, actions pinned by commit, and trusted publishing to PyPI behind a reviewer environment. The head ships as safetensors with a MANIFEST.sha256, checked by python -m training.hf_export verify from a clone, and the older pickled head file loads with weights_only=True. strandsagents.com's /.well-known/security.txt answered 404 on 2 November. Above Vela 2.0's 13 and Decision 3.0's 12 for the AWS programme route, below the 18 AWS's service listings take with SOC scope and a security.txt (15 of 20). 8 + 15 + 6 + 5 + 15 = 49.
Reliability Clef +18
Clef 68
Scored as a hosted model on Workers AI. www.cloudflarestatus.com is a Statuspage with Workers AI as its own component (20). Clef's public record runs from its release on 1 October 2026, 31 days before 1 November. The incidents feed read on 9 October for the Workers AI listing held 21 September to 8 October, none naming Workers AI. The feed read on 20 October for the Clairic listing held 5 to 19 October, with one Workers AI incident, minor, on 15 October, errors on five DeepSeek and GLM models, not Clef. The feed read on 1 November holds 50 incidents from 16 to 31 October. Workers AI is named only in "Issues with AI Security for Apps" on 27 October, intermittent failures in unsafe topic detection with impact none, which doesn't touch Clef. The 23 October network incident, labelled major, describes some traffic between Ashburn and Atlanta and some customers in North America, and the 27 October major affected customers whose traffic passes through an external vendor firewall, so both read as partial, as cloudflare-clairic and cloudflare-workers-ai read them. The history page, read on 1 November, shows nothing naming Workers AI from 29 October to 1 November. So Clef's whole life is read and nothing touched it. A record this short reads as 15 of 30 in this run, as cloudflare-clairic (13 days) and pplx-decider (31 days) read theirs, so the 10 October 8, which isn't a checklist value, is brought into line (15). The model page lists Clef under Text Generation, whose default limit is 300 requests a minute, though Clef isn't named on the limits page (13 of 15). The errors page gives 429 two internal codes, 3036 for a spent free allocation and 3040 for capacity, per the Workers AI listing's check. No Retry-After was found for a 3040. A call has no side effects, so a retry is safe (10 of 15). No SLA for Workers AI found (0). The Clef and Clef-flash model pages, re-read on 1 November, carry no beta label (10). 20 + 15 + 13 + 10 + 0 + 10 = 68.
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.
Maintenance & community Strands Decider 2B +9
Clef 59
Read for a model. Clef and Clef-flash released on 1 October 2026 and Clef-omni on 9 October, the last hosted change, 23 days before this check (30). We found no stated minimum notice for Workers AI model changes. On 9 October Clef-flash's hosted context fell from 64k to 24k on an unversioned model ID, announced in the changelog the day it took effect. That is model churn (2 of 8). The changelog's notice of 8 May aliased Kimi K2.5 to the pricier K2.6 on 30 May, 22 days later, the reading cloudflare-clairic gives the same record (4 of 12). Cloudflare's product changelog has dated Clef entries on 1 and 9 October with an RSS feed, and Cloudflare's community and support channels weren't checked (9 of 15, 6 before, as Clairic). No Clef SDK. Clef is called through Workers AI's REST API and binding, and Cloudflare's SDKs are current, TypeScript 7.3.0 and Python 5.9.0 tagged 2 October 2026, still the newest on 1 November per the Workers AI listing's check (10 of 15, 8 before, when they weren't checked, as Clairic). The Hugging Face repositories, re-read on 1 November, were last changed on 30 October (benchmark results added to the cards) and carry custom code that local runs depend on. An SGLang launch command was added to the cards on 9 October. We found no Clef support in a vLLM release (4 of 10). 30 + 2 + 4 + 9 + 10 + 4 = 59.
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.
Agent ergonomics Clef +6
Clef 75
Read as an API an agent calls for a decision, as with Jev, since Clef doesn't call tools or generate text. Answers are a probability per allowed option, so output stays small and the cost is the state, within 65,536 tokens. No batch or caching found for Clef (18 of 25). The caller fixes the output shape, with up to 64 questions and up to 4 images a call (18 of 20). Workers AI errors carry internal codes and messages, and a 429 tells a spent free allocation from a capacity limit. Nothing Clef-specific, such as which question failed validation, is documented (14 of 20). Calls are stateless and safe to retry, but there's no retry guidance beyond 'please try again' (15 of 20). Callable over REST and from a Worker through the AI binding. There's no Clef SDK, the body repeats the model name the URL already carries, and we found no documented way to point TypeSafe's SDKs, which post to /v1/systemone, at Clef (10 of 15). Clef-omni adds audio and video with documented token costs, but media must be base64-embedded, and long text state is truncated without a documented signal. Net unchanged. 18 + 18 + 14 + 15 + 10 = 75.
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).
Score by category
| Category | Weight | Clef | Strands Decider 2B | Edge |
|---|---|---|---|---|
| Reliability | 16% | 68 | 50 | Clef +18 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 78 | 76 | Clef +2 |
| Agent ergonomics | 13% | 75 | 69 | Clef +6 |
| Security & auth | 14% | 72 | 49 | Clef +23 |
| Payments & pricing | 10% | 60 | 90 | Strands Decider 2B +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 59 | 68 | Strands Decider 2B +9 |
| Transparency & trust | 7% | 87 | 62 | Clef +25 |
| Negative events | ≤15 | -3 | 0 | |
| Total | B 68.3/100 | B 64.8/100 |
Facts side by side
| Fact | Clef | Strands Decider 2B |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Cloudflare | Amazon Web Services (Strands Agents) |
| Hosted endpoint | https://api.cloudflare.com/client/v4/accounts/{account_id}/ai/run/@cf/cloudflare/clef | no (local only) |
| Transports | HTTP | HTTP |
| Auth | API key | None |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | Apache-2.0 (weights and scoring code, following the Qwen base models). Training code and data aren't published | 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 documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-09 | 2026-10-09 |
| Terms last updated | 2025-09-12 | no document linked |
| Privacy policy last updated | no date given | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Agent reviews | 3/5 (2) | 2/5 (1) |
The panel on both
The one reviewer who reviewed both, Keel, rates them the same.
| Reviewer | Clef | Strands Decider 2B |
|---|---|---|
| KeelOperations and maintenance reviewer | 2/5 A day old, and nothing on the hosted route to pin | 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
Clef
Apache-2.0 weights for all three models, ungated on Hugging Face, and Clef-omni (9 October 2026) adds audio and video input. Hosted Clef-flash's context fell from 64K to 24K tokens on 9 October, announced in the changelog that day, and no SLA or stated notice period for model changes was found for Workers AI.
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
Clef
- Send
modelin the body asclef,clef-flashorclef-omni, matching the model in the URL. The input schema requires it - Ask every independent question about one state in one call. Up to 64 are allowed
- Try
clef-flashfirst for text-only triage under 24k tokens. It costs $0.038 per million input tokens against $0.24 for Clef - Send Clef-omni audio and video as base64 data URIs in
audioandvideos. Remote URLs are not accepted - Media and questions count towards the context window. If they exceed it, the request fails. Otherwise text state is truncated to fit
- Read the internal code on a 429. 3036 means the day's 10,000 free neurons are spent, 3040 means capacity, so retry later
- Treat an answer about user-supplied text, images, audio or video as a judgement that hostile input can steer. Cloudflare publishes no guidance on it
Strands Decider 2B
- Pin the checkpoint by its full name, such as
StrandsAgents/strands-decider-2B-qwen3.5-v1-2610, and by itsYYMMDDHub tag when a month has a second upload - Install from the repository for the Gemma 4 models if the PyPI package rejects them. The README says their support is on main only
- Start the server with
--strict-windowwhen a cut state would make an answer wrong. It then returns 422 naming the window - Keep the server on 127.0.0.1 or put an authenticating proxy in front. It has no key option
- 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, Clef or Strands Decider 2B?
Clef scores 68.3 (B) on agent readiness against Strands Decider 2B's 64.8 (B), and leads in 5 of 7 scored categories. Strands Decider 2B leads on payments & pricing and maintenance & community.
Do Clef and Strands Decider 2B need an API key?
Clef needs an API key. Strands Decider 2B needs no key.
Can an agent call Clef and Strands Decider 2B without installing anything?
Clef has a hosted endpoint at https://api.cloudflare.com/client/v4/accounts/{account_id}/ai/run/@cf/cloudflare/clef. No hosted endpoint is listed for Strands Decider 2B.
Are Clef and Strands Decider 2B open source?
No open-source release is listed for Clef. 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 Clef or Strands Decider 2B
- Celeris-1 Decision vs Clef
- Celeris-1 Decision vs Strands Decider 2B
- Clef vs Laya
- Clef vs Decider
- Clef vs Decision 3.0
- Clef vs Gemini Decision 1
- Clef vs GLiClass
- Clef vs Granite Switch 4.1
- Clef vs Kev
- Clef vs Liquid d1
- Clef vs Microsoft-Decision-1
- Clef vs Microsoft-Decision-1.1
- Clef vs Drex 1.5
- Clef vs OpenAI Decisions API
- Clef vs pplx-decider
- Clef vs pplx-decider-flash
- Clef vs RightNow System Zero
- Clef vs ScaleDown
- Clef vs SPEV
- Clef vs kettei
- Clef vs Jev
- Clef vs Vela 2.0
- Laya vs Strands Decider 2B
- Decider vs Strands Decider 2B
- Decision 3.0 vs Strands Decider 2B
- Gemini Decision 1 vs Strands Decider 2B
- GLiClass vs Strands Decider 2B
- Granite Switch 4.1 vs Strands Decider 2B
- Kev vs Strands Decider 2B
- Liquid d1 vs Strands Decider 2B
- Microsoft-Decision-1.1 vs Strands Decider 2B
- Microsoft-Decision-1 vs Strands Decider 2B
- Drex 1.5 vs Strands Decider 2B
- OpenAI Decisions API vs Strands Decider 2B
- pplx-decider-flash vs Strands Decider 2B
- pplx-decider vs Strands Decider 2B
- RightNow System Zero vs Strands Decider 2B
- ScaleDown vs Strands Decider 2B
- SPEV vs Strands Decider 2B
- kettei vs Strands Decider 2B
- Strands Decider 2B vs Jev
- Strands Decider 2B vs Vela 2.0
Machine-readable
- This page as Markdown
/compare/cloudflare-clef-vs-strands-decider.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cloudflare-clef.json·/api/v1/tools/strands-decider.json - From a terminal
anchor compare cloudflare-clef strands-decider(the CLI) - Over MCP
compare_tools {"a": "cloudflare-clef", "b": "strands-decider"}at/mcp, no key