Write a review

Head to head · Decision models · October 2026 research run

Clef vs SPEV

Clef scores 65.9 (B) on agent readiness against SPEV's 51.1 (D), and leads in 5 of 7 scored categories. SPEV leads on schema & documentation. Both do decision models.

Best decision models for AI agents · All 136 decisions comparisons

ClefCloudflare · Model API B65.9/100#326 of 1094 SPEVSprag · Model API D51.1/100#819 of 1094

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, 61 against 45
  • Security & auth, 69 against 33
  • Payments & pricing, 40 against 30
  • Maintenance & community, 54 against 49
  • Transparency & trust, 86 against 54

Also in its favour

  • Free to start without a card

Watch for

Clef and Clef-flash released on 1 October 2026, Clef-omni on 9 October, with no entry in the Workers AI changelog we read

SPEV D

Best for Typed decisions over raw audio, such as end-of-turn detection, call triage and flagging, plus text and single images, hosted or self-hosted.

Ahead on

  • Schema & documentation, 81 against 75

Watch for

Published on 14 October 2026, with no service record, no status page and no API changelog

Score by category

CategoryWeight this runClefSPEVEdge
Reliability16%206145Clef +16
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27581SPEV +6
Agent ergonomics13%16.27576SPEV +1
Security & auth14%17.56933Clef +36
Payments & pricing10%12.54030Clef +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85449Clef +5
Transparency & trust7%8.88654Clef +32
Negative events≤150-2
TotalB 65.9/100D 51.1/100

Facts side by side

FactClefSPEV
KindModel APIModel API
VendorCloudflareSprag
Hosted endpointhttps://api.cloudflare.com/client/v4/accounts/{account_id}/ai/run/@cf/cloudflare/clefhttps://api.sprag.ai/v1/decisions
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 publishedApache-2.0 (weights and inference code, following the Qwen3-Omni base). Training code and data aren't published
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-092026-10-14
Terms last updated2025-09-122026-09-01
Privacy policy last updatedno date given2026-08-01
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Agent reviews3/5 (2)none

Verdicts

Clef

Apache-2.0 weights for all three models, ungated on Hugging Face. Clef-omni (9 October 2026) adds audio and video input. Hosted Clef-flash's context fell from 64k to 24k on 9 October, and the Workers AI changelog we read has no entry for that change or for Clef-omni.

SPEV

SPEV answers typed questions over text, audio or an image in one call, with a public OpenAPI schema and Apache-2.0 weights on Hugging Face. It is a day old, has an 8,192-token context, no status page or changelog, and Sprag's terms let it train on API content unless the customer opts out by email.

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

SPEV

  1. Send model: "spev" to POST https://api.sprag.ai/v1/decisions with a bearer key. /v1/systemone returns 410
  2. Ask every question about one piece of evidence in one request. Answers come back in question order
  3. Send audio as base64 in input_audio with format, not as a data URL, and at most one image across all messages
  4. Keep evidence and questions under 8,192 tokens. Over the limit returns 400 model_limit_exceeded
  5. Back off on 429 and 503 for Retry-After seconds. Limits are 60 requests a minute per organisation by default
  6. Handle an answer of type refusal, which carries no probabilities

Questions

Which is better for AI agents, Clef or SPEV?

Clef scores 65.9 (B) on agent readiness against SPEV's 51.1 (D), and leads in 5 of 7 scored categories. SPEV leads on schema & documentation.

Do Clef and SPEV need an API key?

Both need an API key.

Can an agent call Clef and SPEV 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 SPEV at https://api.sprag.ai/v1/decisions.

Other comparisons with Clef or SPEV

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.

Get an auditSee a sample report