Decision model · Cloudflare

Open structured decisions for real systems.

Cloudflare Clef turns state and typed questions into machine-readable decisions. Use it for routing, evaluation, and agent boundaries without asking your application to parse prose.

Use the exact model ID in the request. Credits follow the same Jev rule as the other decision models.

A decision boundary

cloudflare/clef

One state. Three decision primitives.

State

A support request is urgent, but the account history is incomplete.

Choice

Route to priority support

Score

0.82 urgency

Noul

Hold if account identity is unclear

Structured output keeps your agent observable and your actions controlled.

Input

State + typed questions

Output

Choice · score · noul

Billing

Same as Jev

Endpoint

POST /v1/systemone

Why this model

A shared language for bounded judgment.

Clef is useful when a production system needs a decision signal that is typed, reviewable, and easy to pass between components.

Choice for routing

Select one approved option for queues, tools, policies, or the next workflow step.

Score for ranking

Return a bounded value when your application needs a threshold, priority, or evaluation signal.

Noul for boundaries

Ask a crisp yes/no-style question and keep uncertain cases visible instead of hiding them in prose.

Clef family

Choose the Clef shape that matches the workflow.

Use full Clef for broader decision context and Clef Flash when a narrower, faster boundary is the better fit.

Cloudflare Clef

General structured decisions

Routing, evaluation, and agent control

Cloudflare Clef Flash

Narrow, fast decision gates

Edge-facing routes and fallbacks

Jev API contract

One request shape across models

Compare models without rewiring clients

Call the model

Make the decision boundary part of your API.

Cloudflare Clef uses the same Jev System One request shape in this Playground and API. Keep the model call on your server and own the action after it.

  • Set model to the exact model ID shown below.
  • Send the current state as a compact string or JSON-serializable value.
  • Ask one or more typed questions and handle the returned answer in application code.
The model ID is cloudflare/clef.
Use choice, score, and noul questions together when a workflow needs route, confidence, and safety signals.
For self-hosting and model-specific execution details, consult Cloudflare's model references in addition to this API guide.
Example request
curl -X POST https://thejevai.com/v1/systemone \
  -H "Authorization: Bearer <API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "cloudflare/clef",
    "state": "A customer request needs a safe next step.",
    "questions": {
      "route": {
        "type": "choice",
        "instructions": "Choose the correct next step.",
        "criteria": {
          "continue": "Continue the approved workflow",
          "review": "Send the case for human review"
        }
      }
    }
  }'

Keep the API key on your server. The Playground uses the same request shape through your signed-in session.

Build with it

Put structured judgment where agents need it.

Use Clef between context gathering and execution so every important branch has a visible reason and fallback.

Agent tool guard

Choose whether a requested tool path is allowed, needs review, or should stop.

Support priority

Score urgency and route the case without coupling classification to the final customer action.

Quality evaluation

Turn a rubric into a stable score or noul signal for regression and review workflows.

FAQ

Ship the signal, keep the control.

How do I select Cloudflare Clef?

Set model to cloudflare/clef in the POST /v1/systemone request, or choose Cloudflare Clef in the Playground.

How does Clef compare with Clef Flash?

This page is for the broader Clef model. Use Clef Flash when the decision is narrower and a lighter, faster boundary is a better fit.

Can I self-host Clef?

The model family has open-weight and provider-specific references. Use the linked model sources for release and hosting details, and use this page for the Jev API request contract.

References

Use the right source for each layer.

OpenRouter model page

Check the current hosted model listing and provider availability.

Cloudflare model references

Review official model, Workers AI, and self-hosting context when you need provider-specific details.

Jev API documentation

Use the shared API shape, response fields, authentication, and credit behavior.

View model on OpenRouter

Start with a bounded question

Give your agent a decision boundary it can respect.

Try Cloudflare Clef with a small workflow, inspect the typed result, and keep every side effect behind your own control plane.