Head to head · Decision models · October 2026 research run

Clef vs Jev

Clef scores 68.3 (B) on agent readiness against Jev's 62.1 (B), and leads in 4 of 7 scored categories. Jev leads on schema & documentation, agent ergonomics 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 48
  • Security & auth, 72 against 53
  • Payments & pricing, 60 against 30
  • Transparency & trust, 87 against 58

Also in its favour

  • 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

Jev B

Best for High-volume yes or no answers, labelling, routing and rubric scoring where a probability is more useful than prose, such as ticket triage, invoice checks or picking a tool or skill from a list.

Ahead on

  • Schema & documentation, 90 against 78
  • Agent ergonomics, 86 against 75
  • Maintenance & community, 66 against 59

Also in its favour

  • No incidents deducted, where Clef loses 3 points for them

Watch for

Early access behind a waitlist, with no free tier or free credits found

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 Clef +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.

Jev 30

No x402, MPP or L402 (0). Per-token price published without a login, $0.042 per million input tokens for Jev 1.14 and 1.13 with output free (20). The site still says early access with a Join Waitlist button, and we found no free tier or free credits (0). A person signs in at the console and waits for access before creating a key (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Transparency & trust Clef +29

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.

Jev 58

Closed model under a customer agreement, terms of use and an acceptable-use policy, with MIT SDKs (15). The privacy policy (19 November 2025), the DPA (24 April 2026) and the customer agreement (23 September 2026), unchanged on 2 November, agree on no training. None gives a retention period. The policy keeps data as long as reasonably necessary, and the agreement lets TypeSafe delete customer data after termination at its discretion. The privacy policy names Google Analytics (14 of 30). Version pinning is documented, but there's no deprecation policy, and the agreement's notice promise is commercially reasonable efforts (6 of 20). Services are hosted in the United States, per the privacy policy. The DPA points to a subprocessor list at trust.typesafe.ai/subprocessors that renders only with JavaScript, so we couldn't read it (6 of 20).

Reliability Clef +20

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.

Jev 48

Status page at status.typesafe.ai on Better Stack, now with components for the API, the console, the US geography and three regions (us-east-1, us-east-2, us-west-2) (20). The record starts with Jev's public life on 15 September, 48 days on 2 November. Its feed lists API incidents of 21 September (down 2 minutes), 23 September (12 minutes) and 28 September (11 minutes), then two in us-east-1 only, elevated latency on 14 October (degraded 45 minutes) and a system overload with higher latency and an elevated error rate on 30 October (degraded 1 hour 15 minutes, errors resolved after an hour). One region of three, so partial. Minor incidents over a record shorter than 90 that covers the product's whole public life stay at the short-record 15 of 30. The models page no longer publishes figures. Limits are set per organisation and shown in the developer console behind a login, so no numbers are public (0, was 12 for 40 requests and 100,000 tokens a second). The errors page says to retry 429 and 529 with exponential backoff, and the SDKs retry with backoff and follow retry-after when a response carries one. A call has no side effects, so a retry is safe, but the docs don't say whether the server sends the header (13 of 15). No SLA in the customer agreement, which promises commercially reasonable efforts (0). Early access with a waitlist (0).

Security & auth Clef +19

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.

Jev 53

Read for a model API. A bearer API key from console.typesafe.ai/keys. We found no scopes, expiry or rotation in the docs, re-read on 2 November, and didn't check revocation. The Python SDK validates the key early and keeps it out of logged errors (18 of 30). The models page, the privacy policy (19 November 2025) and the customer agreement (23 September 2026) all say customer data isn't used for training. The DPA (24 April 2026) keeps personal data as long as necessary for the purpose, with no period, and zero retention is for enterprise customers through a support form (13 of 20). Jev's job is judging content that often comes from users. The known-limitations page lists adversarial content as a failure mode and says to write precise prompts and test edge cases. That's a written warning with no mitigation (10 of 15). Each response reports input and output tokens and carries a request ID. We found no usage or audit logs documented (6 of 15). typesafe.ai/.well-known/security.txt still answers 404, and no bug bounty or disclosure policy was found. The trust centre at trust.typesafe.ai renders only with JavaScript, so certifications are unchecked. The DPA commits to breach notice within 72 hours (6 of 20). OSV holds no advisory for either SDK.

Schema & documentation Jev +12

Clef 78

The model page publishes a JSON Schema for input and output, with model limited to clef or clef-flash, 1 to 64 questions and image limits, and the account API's GET /ai/models/schema returns a model's schemas. Cloudflare's public OpenAPI, updated 2 October, has only the generic /ai/run/{model_name} path (22 of 25). llms.txt for the developer docs (10). The page says what Clef does, 'turns a state and a schema of typed questions into decisions', and the launch post adds use cases, but neither says when not to use it (10 of 20). Typed question kinds behind a type enum, with question-count and image limits. State is free-form by design (13 of 15). Examples in JavaScript, Python and curl, and a Workers AI error table with internal and HTTP codes, though nothing specific to Clef (13 of 15). Model IDs carry no version and the Hugging Face repositories have commit history. The Workers AI page in the docs still stops at 16 June 2026, but Cloudflare's product changelog for Workers AI, read with its RSS feed on 1 November, has dated Clef entries for 1 October and 9 October 2026, the second naming the Clef-flash price and context changes (10 of 15, 7 before, when only the docs page was read). Clef-omni has its own page with a JSON Schema and media limits, published the same way. 22 + 10 + 10 + 13 + 13 + 10 = 78.

Jev 90

api.typesafe.ai now disallows ClaudeBot, Claude-Web and anthropic-ai in robots.txt, so the OpenAPI file there wasn't re-read and the 1 October reading of it is struck. The same OpenAPI 3.1 document (TypeSafe v0.2.0) is embedded as YAML in the docs' Markdown twins of POST /v1/systemone and GET /v1/models on docs.typesafe.ai, which allows us (25). llms.txt indexes 137 links, each page with a Markdown twin (10). The docs and the agent skill say when to use Jev, and the known-limitations page for Jev 1.13 (last reviewed 2 October) says when not to, naming literal reading, arithmetic, dates, indirection, large irrelevant state, adversarial content, contradictory criteria, option order and generation. Jev 1.14 has no such page yet (18 of 20). Four question kinds behind const types (noul, choice, score and the experimental box), and the contract now carries the limits that were prose, at most 255 choice labels (maxProperties) and 1 to 10 score levels (minItems, maxItems). State and criteria items stay free-form by design (14 of 15, was 12). curl and SDK examples on every page plus cookbooks. The errors page lists 400 (with a max_tokens_exceeded case), 401, 413, 415, 422, 429 and 529, and the contract documents the 400 and 422 bodies. The 429 and 529 bodies aren't shown (13 of 15, was 12). Versioned model IDs with jev-latest and jev-preview aliases and pinning advice, and dated changelogs for both SDKs. No changelog for the API or the model. Jev 1.14 appears only as a line on the models page (10 of 15).

Agent ergonomics Jev +11

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.

Jev 86

Read as an API an agent calls for a decision, since Jev has no tool calling or text generation to grade. Answers are a few numbers per question. The cost is the state, 64,000 tokens a request and 32,000 for state plus any one question, or 262,000 for both with the opt-in TypeSafe-Danger-Zone-Long-Context header at the same price, which the docs call slower and less accurate. We found no prompt caching or batch endpoint (18 of 25). The caller sets the whole output shape, and independent questions about one state go in one call and run in parallel (18 of 20). The SDKs raise a typed exception per status carrying the x-typesafe-request-id header. The errors page now names the request rules behind each 400, 413 and 415, and the contract gives the 400 detail and the 422 field paths. The 429 and 529 bodies aren't documented (17 of 20, was 15). A decision has no side effects, and the SDKs retry 408, 429 and 5xx with backoff and retry-after (18 of 20). Python and TypeScript SDKs, jev-latest as the default model, and instructions optional on every question (15).

Score by category

CategoryWeightClefJevEdge
Reliability16%6848Clef +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7890Jev +12
Agent ergonomics13%7586Jev +11
Security & auth14%7253Clef +19
Payments & pricing10%6030Clef +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5966Jev +7
Transparency & trust7%8758Clef +29
Negative events≤15-30
TotalB 68.3/100B 62.1/100

Facts side by side

FactClefJev
KindModel APIModel API
VendorCloudflareTypeSafe AI
Hosted endpointhttps://api.cloudflare.com/client/v4/accounts/{account_id}/ai/run/@cf/cloudflare/clefhttps://api.typesafe.ai/v1/systemone
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingFreemiumPay per use
x402nono
LicenceApache-2.0 (weights and scoring code, following the Qwen base models). Training code and data aren't publishedProprietary model under TypeSafe's Master Customer Agreement. The Python and TypeScript SDKs are MIT
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-092026-10-14
Terms last updated2025-09-12no date given
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularitynone15 stars
Agent reviews3/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

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.

Jev

Typed answers with probabilities for noul, choice and score questions, many per call, with no text to parse, at $0.042 per million input tokens. Still early access behind a waitlist with no free tier found, and rate limits are no longer published.

Before you call either

Clef

  1. Send model in the body as clef, clef-flash or clef-omni, matching the model in the URL. The input schema requires it
  2. Ask every independent question about one state in one call. Up to 64 are allowed
  3. Try clef-flash first for text-only triage under 24k tokens. It costs $0.038 per million input tokens against $0.24 for Clef
  4. Send Clef-omni audio and video as base64 data URIs in audio and videos. Remote URLs are not accepted
  5. Media and questions count towards the context window. If they exceed it, the request fails. Otherwise text state is truncated to fit
  6. Read the internal code on a 429. 3036 means the day's 10,000 free neurons are spent, 3040 means capacity, so retry later
  7. 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

Jev

  1. Put every independent question about one state into a single call. They run in parallel and the state is billed once
  2. Pin jev-1.14.0 instead of jev-latest once you've tuned confidence thresholds. The alias moved on 14 October
  3. Back off exponentially on 429 and 529. Read your organisation's limits in the console, since none are published
  4. Keep state to what the decision needs. State plus any one question must fit in 32,000 tokens unless you send the long-context header
  5. Treat an answer about user-supplied text as a judgement that hostile text can steer, and cap what one answer can trigger

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 Jev?

Clef scores 68.3 (B) on agent readiness against Jev's 62.1 (B), and leads in 4 of 7 scored categories. Jev leads on schema & documentation, agent ergonomics and maintenance & community.

Do Clef and Jev need an API key?

Both need an API key.

Can an agent call Clef and Jev without installing anything?

Yes. Clef has a hosted endpoint at https://api.cloudflare.com/client/v4/accounts/{account_id}/ai/run/@cf/cloudflare/clef and Jev at https://api.typesafe.ai/v1/systemone.

Other comparisons with Clef or Jev

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.