pplx-decider vs Jev

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.

Jev

Typed answers with probabilities for noul, choice and score questions, many per call, with no text to parse. Early access behind a waitlist, with no free tier or free credits found.

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.

Jev

1. Put every independent question about one state into a single call. They run in parallel and the state is billed once
2. Pin jev-1.13.0 instead of jev-latest once you've tuned confidence thresholds
3. Back off exponentially on 429 and 529. The limits move with demand
4. Keep state to what the decision needs. Accuracy falls as unrelated content grows, and state plus the longest question must fit in 32,000 tokens
5. Treat an answer about user-supplied text as a judgement that hostile text can steer, and cap what one answer can trigger