Celeris-1 Decision vs Liquid d1

Celeris-1 Decision

Typed probabilities, image inputs and optional explanations suit routing and classification inside an agent. Both System One and OpenAI Decisions request formats are documented. The service remains early access under its terms, activation can queue, and prepaid credit expires after 30 days. The published accuracy and latency figures are Celeris measurements, not Anchor Terminal tests.

Liquid d1

The hosted API costs $0.04 per million input tokens and takes TypeSafe's System One request, 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. The family launched between 22 September and 7 October 2026.

Celeris-1 Decision

1. Use the decision model path and matching model field. This model has no chat, Responses or models endpoint.
2. Use at most 512 questions per request, or 64 with explanations. Both endpoints reject streaming.
3. Preserve x_celeris in a custom Jev SDK response model when reading explanations. The default response type drops it.
4. Retry 429 with Retry-After and backoff. Stop on 402 until workspace credit is replenished.
5. Read usage.input_tokens for cost, including images and request overhead. Track credit expiry separately from token consumption.

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 for images. d1:free is text-only and answers that it does not accept images
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