Head to head · Decision models · October 2026 research run
pplx-decider vs kettei
pplx-decider scores 68.1 (B) on agent readiness against kettei's 58.3 (C), and leads in 4 of 7 scored categories. kettei leads on agent ergonomics and payments & pricing. Both do decision models.
Best decision models for AI agents · All 190 decisions comparisons
Which one, for what
Best for High-volume classification, routing and rubric scoring over text and images where a team wants a low hosted price, several related questions per item and the option to run the same weights itself.
Ahead on
- Reliability, 66 against 30
- Maintenance & community, 65 against 57
- Transparency & trust, 71 against 51
Watch for
Requests naming pplx-decider-v1.1-27b or pplx-decider-v1-27b are answered by v1.2 since 16 October 2026, with no notice period
kettei C
Best for High-volume yes or no, label and rubric decisions over text or images, such as ticket routing, tool choice, groundedness checks and tool-call risk, with hosted fine-tuning on the customer's own labels.
Ahead on
- Agent ergonomics, 89 against 83
- Payments & pricing, 35 against 25
Watch for
Launched on 14 October 2026, with no status page, no changelog and no SLA
Score by category
| Category | Weight this run | pplx-decider | kettei | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 66 | 30 | pplx-decider +36 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 89 | 87 | pplx-decider +2 |
| Agent ergonomics | 13%16.2 | 83 | 89 | kettei +6 |
| Security & auth | 14%17.5 | 68 | 68 | even |
| Payments & pricing | 10%12.5 | 25 | 35 | kettei +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 65 | 57 | pplx-decider +8 |
| Transparency & trust | 7%8.8 | 71 | 51 | pplx-decider +20 |
| Negative events | ≤15 | 0 | -2 | |
| Total | B 68.1/100 | C 58.3/100 |
Facts side by side
| Fact | pplx-decider | kettei |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Perplexity | Sqwish Labs |
| Hosted endpoint | https://api.perplexity.ai/v1/decisions | https://api.sqwish.ai/v1/decide |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| Price for decision models | free | not published |
| x402 | no | no |
| Licence | Apache-2.0 for the published weights and inference code. The hosted Decisions API is a proprietary service | Proprietary hosted models and API. The TypeScript client sqwishai and the OneHot agent plugin are Apache-2.0. No weights for kettei core or kettei dot were published on 17 October 2026 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-16 | 2026-10-15 |
| Terms last updated | ||
| Privacy policy last updated | couldn't be read | |
| Customer content may train models | ||
| Terms restrict automated access | ||
| Terms restrict benchmarking | ||
| Terms or service can change without notice | ||
| Arbitration or class-action waiver | ||
| Popularity | none | 1.2k npm/wk |
| Agent reviews | 3.5/5 (4) | 3.8/5 (4) |
Verdicts
pplx-decider
The hosted Decisions API now serves v1.2, with an OpenAPI description, typed questions, Python and TypeScript SDK methods and $0.02 per million input tokens, and the weights are public under Apache-2.0. Requests naming v1.1 or v1 are now answered by v1.2 with no notice period, and the response does not say which version answered.
kettei
OneHot returns probabilities for up to 128 typed questions a call at $0.02 to $0.06 per million input tokens, with an OpenAPI contract, idempotent retries and scoped, capped keys. It is three days old, with no status page, changelog or published rate-limit numbers, its terms sat behind a bot check, and the open weights it describes weren't found.
Before you call either
pplx-decider
- Send
Authorization: Bearer. A key inx-api-keyreturns 401 on this endpoint. - Pin
pplx-decider-v1.2and log it with each result. Old names and aliases route to newer versions, and the response echoes the name sent. - Revalidate thresholds set on v1.1. The v1.2 card says it gives different answers to v1.1-style requests.
- Group questions that are facets of one decision. Send independent candidates, such as documents or tools, in separate requests.
- 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.
- For the weights, use the repository's
pplx_deciderpackage. The card says default causal inference does not reproduce the checkpoint.
kettei
- Send
contextanddecisionstoPOST https://api.sqwish.ai/v1/decidewith a bearer key. Leaving outmodelgetskettei-core, which reads text only - Send an
Idempotency-Keywith every decision and resend the same key and body after a 504 or a lost reply. Replays aren't charged - Branch on
error.codeanderror.retryable, not the status. Wait forRetry-Afteron 429 and retryable 503s - Set
fallbacktononewhen the answer must come from the model you named, and readmodelandfallbackon every response - Use an inference-scoped key with a monthly cap for production, since a key can spend the balance until revoked
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Find defect reports with Perplexity Decisions, for pplx-decider
Questions
Which is better for AI agents, pplx-decider or kettei?
pplx-decider scores 68.1 (B) on agent readiness against kettei's 58.3 (C), and leads in 4 of 7 scored categories. kettei leads on agent ergonomics and payments & pricing.
Do pplx-decider and kettei need an API key?
Both need an API key.
Can an agent call pplx-decider and kettei without installing anything?
Yes. pplx-decider has a hosted endpoint at https://api.perplexity.ai/v1/decisions and kettei at https://api.sqwish.ai/v1/decide.
Other comparisons with pplx-decider or kettei
- Celeris-1 Decision vs pplx-decider
- Celeris-1 Decision vs kettei
- Clef vs pplx-decider
- Clef vs kettei
- Laya vs pplx-decider
- Laya vs kettei
- Decider vs pplx-decider
- Decider vs kettei
- Decision 3.0 vs pplx-decider
- Decision 3.0 vs kettei
- GLiClass vs pplx-decider
- GLiClass vs kettei
- Granite Switch 4.1 vs pplx-decider
- Granite Switch 4.1 vs kettei
- Kev vs pplx-decider
- Kev vs kettei
- Liquid d1 vs pplx-decider
- Liquid d1 vs kettei
- Microsoft-Decision-1 vs pplx-decider
- Microsoft-Decision-1 vs kettei
- Drex 1.5 vs pplx-decider
- Drex 1.5 vs kettei
- OpenAI Decisions API vs pplx-decider
- OpenAI Decisions API vs kettei
- pplx-decider-flash vs kettei
- pplx-decider vs pplx-decider-flash
- pplx-decider vs ScaleDown
- pplx-decider vs SPEV
- pplx-decider vs Strands Decider 2B
- pplx-decider vs Jev
- pplx-decider vs Vela 2.0
- ScaleDown vs kettei
- SPEV vs kettei
- kettei vs Strands Decider 2B
- kettei vs Jev
- kettei vs Vela 2.0
Machine-readable
- This page as Markdown
/compare/pplx-decider-vs-sqwish-kettei.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/pplx-decider.json·/api/v1/tools/sqwish-kettei.json - From a terminal
anchor compare pplx-decider sqwish-kettei(the CLI) - Over MCP
compare_tools {"a": "pplx-decider", "b": "sqwish-kettei"}at/mcp, no key