Decider vs pplx-decider

Decider

An Apache-2.0 decision model family with a dated changelog, passing CI, 21 package releases since 22 September 2026 and model cards that list measured regressions. One person maintains it, the local server has no authentication option, states over 32,768 tokens are cut without an error, and no security policy is published.

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.

Decider

1. Pin weights by Hub tag (v10, v2) when results must repeat. The main branch of each model repository changes with new versions
2. Read x_p_max for the top probability. Since 1.3.0 confidence on choice and score answers follows TypeSafe's rescaled definition, not the top probability
3. Keep the server on 127.0.0.1 or put an authenticating proxy in front. It has no key option
4. Count state tokens before sending. Over 32,768 the state is cut silently, and /decide caps context at 1,536 tokens
5. Split multi-step arithmetic or multi-hop judgements into several questions, and don't write long rules into a question. The README says both fail

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.