Celeris-1 Decision vs pplx-decider

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.

pplx-decider

The hosted Decisions API has an OpenAPI description, typed questions, documented limits and a published price of $0.02 per million input tokens, and the v1.1 weights are public under Apache-2.0. The API is days old, the official Python SDK has no method for it, and the governing terms and privacy notice could not be read on 9 October 2026.

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.

pplx-decider

1. Send Authorization: Bearer. A key in x-api-key returns 401 on this endpoint.
2. Set model on every request. A missing or unknown model returns 400, and the guide shows a -latest name rejected.
3. Resize images to 2,048 tiles of 32 by 32 pixels or fewer before sending. Larger images end in a 504 after about a minute.
4. Check the HTTP status before parsing an error. 404 and 405 have empty bodies, 504 can be HTML, and error.code changes type.
5. For the weights, use the repository's autojev code. The card says default causal inference does not reproduce the evaluated setup.