Loading the catalogue…
Loading the catalogue…
Cloudflare's open-weight 27B decision model that returns calibrated, structured probabilities over text, JSON, and image inputs instead of generated text.
Overview. Clef is a 27-billion-parameter decision model built by Cloudflare on a Qwen3.8-27B backbone paired with a custom joint schema head, released as open weights under Apache-2.0 on October 1, 2026. Instead of generating free-form text, Clef performs a single non-autoregressive pass over a defined set of options and returns calibrated, structured probabilities. It accepts text, JSON, and image inputs, with the open-weight repository also supporting video frames. Developers reach for it when an application needs a fast, schema-constrained decision rather than a conversational response.
Key strengths. Cloudflare trained Clef's routing head and low-rank adapters specifically for calibration, combining label-smoothed cross-entropy and Brier loss with a reinforcement-learning objective aimed at producing well-calibrated decisions rather than fluent prose. That focus is also its boundary: Clef has no free-form generative capability, making it unsuitable for code generation, writing, math, or agentic tool-loop tasks that depend on generated text. Its strength is narrow and deliberate — turning text, JSON, and image inputs into structured, probability-scored answers over a fixed option set.
When to use it. Use Clef when you need a calibrated classification or routing decision embedded directly in an application — for example scoring a fixed set of labeled outcomes from text, JSON, or an attached image — rather than a generated response. It's served through Workers AI, Cloudflare's edge Inference platform, making it a fit for latency-sensitive decision steps inside a larger pipeline. It is not the right choice for chat, content generation, or any task expecting free-form output.
Limitations. Clef produces no free-form text, streaming output, or reasoning traces, so it cannot substitute for a generative chat model. Cloudflare's own documentation specifies a 65,536-token context window for the hosted endpoint; the underlying backbone configuration declares a larger position capacity, but that has not been confirmed as a supported serving limit. No training-data cutoff date has been disclosed.
Sovereignty note. Clef is created and hosted by Cloudflare, a US-headquartered company; no creator-disclosed CLOUD Act exposure or training-on-input policy was found in the available documentation. Because Clef's weights are published openly under Apache-2.0, teams with data-residency requirements can self-host the model rather than relying solely on the hosted endpoint.
| Inference Provider | Sovereignty | Runs in | Price | Status | Pin |
|---|---|---|---|---|---|
| L0 | €0.22 per 1M input tokensFree per 1M output tokens | Online |
14 use cases classified by the curator. The note says why.
Standard text-in/text-out classification is within reach of a general-purpose model at this context size, though no capability flags or benchmarks confirm strength.
65,536-token context window covers single-document Q&A workloads of moderate length.
Text editing is a core LLM capability requiring no special tooling; context size is sufficient for document-level edits.
General text-generation task with no special capability requirements; context window is more than adequate.
64K context window is sufficient for entity extraction over typical documents; lacks confirmed structured-output tooling.
64K context comfortably covers typical meeting transcripts for summarisation tasks.
No tool-calling capability flagged and no code-specific benchmarks published, undermining agentic coding workflows that require iterative tool use.
No vision/OCR capability flagged; model profile indicates text-only processing.
No vision capability is flagged for this model, ruling out image-based Q&A.
No tool-calling or function-calling capability is flagged, which is a hard requirement for reliable tool orchestration.
Sourced numbers, not our own evaluations. Percentiles are against the decision models on Stav.
No benchmark source yet
curl https://api.stav.ai/v1/decisions \
-H "Authorization: Bearer $STAV_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "cloudflare/clef",
"state": {"tool": "delete_file", "path": "/etc/passwd"},
"questions": {"safe": {"type": "noul", "instructions": "Is this tool call safe to run?"}}}'→ X-Stav-Request-Id · X-Stav-Model · X-Stav-Provider → X-Stav-Sovereignty-Level — the rung the request was served at