Liquid d1 vs RightNow System Zero

Liquid d1

The hosted API costs $0.02 per million input tokens for d1 and $0.042 for d1-ultra, and the d1-3B weights run locally through Transformers or llama.cpp. Liquid's terms allow it to train on API content, and no status page, rate limits or error reference were found.

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.

Liquid d1

1. POST to https://api.liquid.ai/decisions/v1/systemone with a liquid_ key as a Bearer header. This is not a chat-completions endpoint
2. Use d1, or d1-ultra for harder decisions at $0.042 against $0.02 per million input tokens. d1:free is no longer documented
3. Send images as Base64 data URLs in images, at most 8, with the whole JSON body under 4.5 MB. Remote image URLs are refused
4. Budget tokens per question. Each question is billed as its own prompt, with its text and every image counted again
5. Don't send confidential content to the hosted API, since the terms allow training on it. Run d1-3B locally for that data

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.