Celeris-1 Decision vs pplx-decider-flash

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-flash

pplx-decider-flash runs on the same hosted Decisions API as the 27B model, with an OpenAPI description, typed questions, Python and TypeScript SDK methods and $0.01 per million input tokens, and its weights are public under Apache-2.0. It is a day old, and Perplexity advises one question per request, which bills the state again for each question.

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-flash

1. Send Authorization: Bearer with model set to pplx-decider-flash-v1.2. A key in x-api-key returns 401.
2. Send one question per request by default. Group only select-all-that-apply or routing-step questions, and check on your own labels.
3. Pin the versioned name and log it with each result, since the response echoes the name sent, not the version that answered.
4. Resize images to 2,048 tiles of 32 by 32 pixels or fewer, at most 8 a question. Larger images end in a 504 after about a minute.
5. Compare it with pplx-decider-v1.2 on a labelled sample at your thresholds before choosing it.