Celeris-1 Decision vs OpenAI Decisions API

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.

OpenAI Decisions API

Typed predicate, choice and score answers with probabilities, up to 200 questions a call, at $0.10 per million input tokens with no output charge. It is a public beta released on 6 October 2026, with one model alias, no dated snapshot, no Batch route and no SLA found.

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.

OpenAI Decisions API

1. Put independent questions about one input in a single questions array. Send a separate request when a question depends on an earlier answer
2. Check each answer's type before reading it. A question can come back as refusal while the others in the same request are answered
3. Encode images as base64 data URLs. Hosted URLs and file_id inputs are rejected
4. Give a choice question a fallback value such as other, and set thresholds from your own labelled examples
5. Use Python SDK 3.26.0 or JavaScript 7.30.0 or later, and follow Retry-After on 429 and 503