Liquid d1 vs SPEV

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.

SPEV

SPEV answers typed questions over text, audio or an image in one call, with a public OpenAPI schema and Apache-2.0 weights on Hugging Face. It is a day old, has an 8,192-token context, no status page or changelog, and Sprag's terms let it train on API content unless the customer opts out by email.

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

SPEV

1. Send model: "spev" to POST https://api.sprag.ai/v1/decisions with a bearer key. /v1/systemone returns 410
2. Ask every question about one piece of evidence in one request. Answers come back in question order
3. Send audio as base64 in input_audio with format, not as a data URL, and at most one image across all messages
4. Keep evidence and questions under 8,192 tokens. Over the limit returns 400 model_limit_exceeded
5. Back off on 429 and 503 for Retry-After seconds. Limits are 60 requests a minute per organisation by default
6. Handle an answer of type refusal, which carries no probabilities