Clef or Clef-flash in front of a Sume agent: which tier to use

Cloudflare lists a median 38.8 ms for Clef-flash and 209.3 ms for Clef. Use the fast tier to gate runs and the larger one for the choices that cost real money.

5 min readSume
All posts

Use Clef-flash for high-volume, low-stakes gates, and Clef for decisions where a wrong answer starts expensive work. Cloudflare's launch post gives a median latency of 38.8 ms for Clef-flash and 209.3 ms for Clef. Price is not disclosed on the page that was read, so budget with your own measurements.

Pick by the cost of a wrong yes

A Sume Agent Completion takes far longer than either decision, so latency of the gate rarely matters against the run itself. What matters is how often the gate is wrong and what a wrong yes costs.

Tier choice in front of a Sume run (read 2026-10-05)
SituationTier to try firstWhy
Spam filter before any runClef-flashWrong answers are cheap
Start a run that makes videoClefA wrong yes costs generation spend
Route to one of a few FormatsClef-flash, then check ioThe Format read catches mismatches
Anything that moves moneyNeither aloneUse dry_run and a spend cap

Measure on your own data

Whatever the tier, the run still needs generation_spend_cap_usd. Measure both tiers on a labeled set of your own tickets, and compare how many wrong yeses each lets through, before you choose.

Check the docs before you ship

Sume's limits and field names change faster than blog posts do. Read the linked docs pages for the current request fields before you ship, and send a dry_run or a low spend cap on your first real call.

Sources

Related posts

More in Comparisons

All Comparisons posts

Written by Sume