Edge-friendly shape
Keep the model call focused on the decision and leave storage, identity, and actions at your boundary.
Decision model · Cloudflare
Make edge workflows decide quickly.
Clef Flash is the lighter Clef variant for applications that need structured decisions while keeping routing, safeguards, and side effects in code.
Use the exact model ID in the request. Credits follow the same Jev rule as the other decision models.
A decision boundary
cloudflare/clef-flashA small answer can unlock a large workflow.
State
A request matches the account, but the requested action needs an extra verification step.
Choice
Route to verification
Score
0.86 confidence
Noul
Reject if identity signals conflict
Use the answer as a signal; keep the permission check and action in your system.
Input
State + typed questions
Output
Choice · score · noul
Billing
Same as Jev
Endpoint
POST /v1/systemone
Why this model
A lighter path to structured decisions.
Use Clef Flash when an edge-facing workflow needs a crisp decision signal and a predictable handoff to application code.
Three decision primitives
Return a choice, score, or noul result that your router can handle without text extraction.
Clear fallback
Use confidence and explicit noul questions to send uncertain cases to verification or human review.
Where it fits
Choose the lighter Clef path for fast gates.
Clef Flash is useful when the decision is narrow, the valid actions are known, and response time matters to the workflow.
PatternUse it forGood boundary
Identity gate
Choose verify, continue, or reject
Keep security policy in code
Edge routing
Select the next lightweight path
Keep the request bounded
Fallback trigger
Detect ambiguity or missing evidence
Escalate before side effects
Call the model
Use the same API shape as Jev.
Select Clef Flash by model ID and keep the rest of the System One request unchanged.
- 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-flash.
Ask narrow questions that match the route, gate, or fallback you want to own.
For security-sensitive actions, require an independent permission check before execution.
Example request
curl -X POST https://thejevai.com/v1/systemone \
-H "Authorization: Bearer <API_KEY>" \
-H "Content-Type: application/json" \
-d '{
"model": "cloudflare/clef-flash",
"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 a typed gate close to the edge.
Use Clef Flash for decisions that benefit from a fast, explicit handoff.
Request verification
Choose whether a request needs a second signal before it reaches a protected action.
Edge cache routing
Select a safe cache or origin path while keeping cache writes and invalidation deterministic.
Abuse review
Flag ambiguous activity for review instead of silently allowing or blocking it.
FAQ
Keep the fast path bounded.
How do I select Clef Flash?
Set model to cloudflare/clef-flash in the POST /v1/systemone request, or choose Cloudflare Clef Flash in the Playground.
Does Clef Flash have a separate price?
No. It follows the same Jev-based credit rule for this API. Validate the actual latency and quality that your workflow needs.
Is Clef Flash a replacement for authorization?
No. It can recommend a route or flag a boundary, but authorization, identity checks, and side effects must remain in your application.
References
Connect the fast path to a clear control plane.
OpenRouter model page
Check current availability and provider details for Cloudflare Clef Flash.
Cloudflare Clef family
Use the full Clef page when you need the broader model context and hosting references.
Jev API documentation
Keep the request, response, and credit behavior aligned with the shared API.
Start with a bounded question
Give your edge workflow a safer next step.
Try Clef Flash with one narrow gate, observe the fallback rate, and expand only when the boundary is stable.