Cloudflare clef-flash vs Mercury Decide
Cloudflare clef-flash and Mercury Decide have no measured difference in accuracy, calibration or cost in our data yet.
| Spec | Cloudflare clef-flash | Mercury Decide |
|---|---|---|
| Provider | Cloudflare | Inception |
| Decision Index score | 47.6 | — |
| Calibration error (ECE) | 0.025 | — |
| Median latency (p50) | 53 ms | — |
| Cost per 1,000 decisions | — | $0.0040 |
| Parameters | 10B | — |
| Open weights | Yes | No |
| Question types | Choice (one of N options), Score (ordered rubric), Yes / no | Choice (one of N options), Score (ordered rubric), Yes / no |
| Mechanism | Decoder LM with a decision readout | Hosted API |
| License | apache-2.0 | proprietary |
FAQ
Is Cloudflare clef-flash or Mercury Decide more accurate?
At least one of the two has no Jev Decision Index score yet, so their accuracy cannot be compared here.
Which is better calibrated, Cloudflare clef-flash or Mercury Decide?
No calibration difference between Cloudflare clef-flash and Mercury Decide is recorded yet.
Is Cloudflare clef-flash or Mercury Decide cheaper per 1,000 decisions?
A hosted price is not recorded for both models; open-weight models cost the compute you run them on.
Cost per 1,000 decisions assumes 200 input tokens per decision. Pricing is indicative — confirm with the provider before production use. Highlighted values indicate the better figure for that row.