Celeris-1 Decision vs Granite Switch 4.1

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.

Granite Switch 4.1

One self-hosted Apache 2.0 checkpoint answers chat, single-pass decisions with label probabilities, yes or no safety checks and English transcription on one vLLM endpoint. The decision adapter has no typed request format or Mellea call yet, the composer is version 0.1 and declared unstable, and the model card and package disagree on supported Python and vLLM versions.

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.

Granite Switch 4.1

1. Pass chat_template_kwargs: {"adapter_name": "decision"} or "guardian-core". Without it the request is ordinary chat on the base model
2. For a decision, send the state and the ### DECISION question as two user turns, request logprob_token_ids for the option labels, and set max_completion_tokens to 1
3. Use single-token option labels. Split more than 128 labels into chunks with the identical prompt and apply one softmax over all returned logprobs
4. Parse guardian-core answers as JSON, {"score": "yes"} or {"score": "no"}, where yes means the criterion is met
5. Add authentication before exposing the vLLM server. Neither vLLM nor the checkpoint requires a key by default