kettei vs Jev

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.

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.

kettei

1. Send context and decisions to POST https://api.sqwish.ai/v1/decide with a bearer key. Leaving out model gets kettei-core, which reads text only
2. Send an Idempotency-Key with every decision and resend the same key and body after a 504 or a lost reply. Replays aren't charged
3. Branch on error.code and error.retryable, not the status. Wait for Retry-After on 429 and retryable 503s
4. Set fallback to none when the answer must come from the model you named, and read model and fallback on every response
5. Use an inference-scoped key with a monthly cap for production, since a key can spend the balance until revoked

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