kettei vs Vela 2.0

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.

Vela 2.0

One self-hosted call answers routing, prompt-attack, personal-data and unsupported-claim questions with probabilities and character offsets, under Apache-2.0 with SHA-256 manifests. The models are days old and carry no Hub version tags, and the three larger sizes keep 74 to 89 per cent of their Decision 2.0 bases on the Jev Decision Index by the authors' figures.

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

Vela 2.0

1. Pin a commit hash with revision= when loading from the Hub. The repositories have no tags and main has changed since launch
2. Send the served name in model, for example vllm-sr/Vela-2.0-4B. The bundled server answers 422 to any other name
3. Name span questions pii, halu or toxic, or set "head": "router", to get the trained router head. Other labels go to the broad head
4. Keep input under 16,384 tokens a sequence (8,192 on the 0.3B). The bundled server answers 413 when the questions alone don't fit
5. Set VELA2_API_KEY before binding the bundled server beyond 127.0.0.1, and keep the model runtime on a trusted network