Celeris-1 Decision vs Clef

Celeris-1 Decision

Typed probabilities, image inputs and optional explanations suit routing and classification inside an agent. Both System One and OpenAI Decisions request formats are documented. The service remains early access under its terms, activation can queue, and prepaid credit expires after 30 days. The published accuracy and latency figures are Celeris measurements, not Anchor Terminal tests.

Clef

Apache-2.0 weights for both models on Hugging Face, ungated, with no account needed to download. Released on 1 October 2026, with no service record and no entry in the Workers AI changelog we read.

Celeris-1 Decision

1. Use the decision model path and matching model field. This model has no chat, Responses or models endpoint.
2. Use at most 512 questions per request, or 64 with explanations. Both endpoints reject streaming.
3. Preserve x_celeris in a custom Jev SDK response model when reading explanations. The default response type drops it.
4. Retry 429 with Retry-After and backoff. Stop on 402 until workspace credit is replenished.
5. Read usage.input_tokens for cost, including images and request overhead. Track credit expiry separately from token consumption.

Clef

1. Send model as clef or clef-flash in the body as well as 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. It costs $0.09 per million input tokens against $0.24
4. Read the internal code on a 429. 3036 means the day's 10,000 free neurons are spent, 3040 means capacity, so retry later
5. Treat an answer about user-supplied text as a judgement that hostile input can steer. Cloudflare publishes no guidance on it