jeff-adapter-code vs Cloudflare clef
jeff-adapter-code and Cloudflare clef have no measured difference in accuracy, calibration or cost in our data yet.
| Spec | jeff-adapter-code | Cloudflare clef |
|---|---|---|
| Provider | mstrasser | Cloudflare |
| Decision Index score | — | 53.1 |
| Calibration error (ECE) | — | 0.040 |
| Median latency (p50) | — | 102 ms |
| Cost per 1,000 decisions | — | — |
| Parameters | — | 28B |
| Open weights | Yes | Yes |
| 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 | Decoder LM with a decision readout |
| License | apache-2.0 | apache-2.0 |
FAQ
Is jeff-adapter-code or Cloudflare clef 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, jeff-adapter-code or Cloudflare clef?
No calibration difference between jeff-adapter-code and Cloudflare clef is recorded yet.
Is jeff-adapter-code or Cloudflare clef 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.