RightNow System Zero vs Jev

RightNow System Zero

A well-documented decision API with an OpenAPI file, idempotent retries, a detailed error catalogue, streaming over WebSocket and published per-unit prices with USD 5 of starting credit. Standard context is 38,000 tokens; the 64k, 128k and 1M bands are held and video is a preview. The latency and benchmark figures are RightNow's own, and several of its pages disagree.

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.

RightNow System Zero

1. Send audio only as inline 16,000 Hz WAV. The FLAC, MP3, OGG and MP4 audio named on the blog are refused with media_unsupported.
2. Keep state under 38,000 tokens. Long-context requests return 404 long_context_not_available, which never succeeds on retry.
3. Reuse the same Idempotency-Key and body on retries, and stop when error.retryable or x-should-retry is false.
4. Check every entry in answers even on HTTP 200, since one question can be refused while the others are answered.
5. Treat probabilities as uncalibrated while calibrated is false, and pin system-zero-2.0.0 when answers must not move with the alias.

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