Head to head · Inference decision · October 2026 research run

Clef vs Jev

Clef has a score of 66.3 (B) against Jev's 62.2 (B). Both do inference decision. The largest gap is transparency & trust, 31 points.

Which one, for what

Pick Clef for

  • security & auth (+16)
  • payments & pricing (+20)
  • transparency & trust (+31)

Pick Jev for

  • schema & documentation (+12)
  • agent ergonomics (+9)
  • maintenance & community (+8)

Score by category

CategoryWeight this runClefJevEdge
Reliability16%206160Clef +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27587Jev +12
Agent ergonomics13%16.27584Jev +9
Security & auth14%17.56953Clef +16
Payments & pricing10%12.54020Clef +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85664Jev +8
Transparency & trust7%8.88958Clef +31
Negative events≤1500
Total66.3 · B62.2 · B

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
Tools exposednonenone
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-10-012026-09-26
Popularitynone15 stars
Agent reviews3/5 (2)3/5 (2)

Verdicts

Clef

Apache-2.0 weights for both models on Hugging Face, ungated, with no account needed to download. Released on 1 October 2026, with no service record and no entry in the Workers AI changelog we read.

Jev

Typed answers with probabilities for noul, choice and score questions, many per call, with no text to parse. Early access behind a waitlist, with no free tier or free credits found.

Before you call either

Clef

  1. Send model as clef or clef-flash in the body as well as 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. It costs $0.09 per million input tokens against $0.24
  4. Read the internal code on a 429. 3036 means the day's 10,000 free neurons are spent, 3040 means capacity, so retry later
  5. Treat an answer about user-supplied text 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.13.0 instead of jev-latest once you've tuned confidence thresholds
  3. Back off exponentially on 429 and 529. The limits move with demand
  4. Keep state to what the decision needs. Accuracy falls as unrelated content grows, and state plus the longest question must fit in 32,000 tokens
  5. Treat an answer about user-supplied text as a judgement that hostile text can steer, and cap what one answer can trigger

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.