Summary: Liquid AI's d1.2 and d1.2-ultra are "decision models": instead of writing an answer, they return probabilities for questions you define, such as "is this a complaint?", "which team should take this ticket?" or "what is the total on this invoice?". They bill input tokens only (d1.2 is $0.02 per million, d1.2-ultra $0.042), and output is free. This tutorial walks through a support-ticket router and an invoice reader built from the official docs, plus the cost math and the gotchas we found.
What a decision model is, and when it beats an LLM
A lot of "AI features" in real products are not writing tasks. They are bounded decisions: tag a message, pick a queue, rate urgency, pull a date out of a form, flag personal data. The usual approach is to prompt a chat model, ask it to reply in JSON, then parse and validate the text and hope the format holds. Liquid's decision models skip the text step. You send a state (the input: a message, a JSON object, an image or an audio clip) and a set of named questions, and the API returns typed answers with calibrated probabilities. The docs say the model answers all questions of a call at once, with zero generated tokens, which is why the response always reports output_tokens: 0.
That makes d1.2 a good fit when the set of possible answers is known in advance. It is a poor fit when you need free-form text: a reply draft, a summary, an explanation. For those you still want a generative model.
The question types you can ask
The decisions guide lists these types. The first three are the classic ones; the rest are new in d1.2 and d1.2-ultra (older d1 models return a 422 error on them).
- Noul: one probability that the answer is yes. Use it for yes/no gates and moderation flags.
- Choice: the most likely option, a confidence value and the full distribution. Use it for routing.
- Score: a position on an ordered rubric you write (for example four urgency levels), with the distribution.
- Choice with
multiple: true: every option that applies, each with its own probability (they do not sum to 1). - Text, Number, Date: read one value from the input, with the exact characters and their position, or "not found".
- Number with
range: an estimate plus a 10th-90th percentile interval, for counts. - Spans: every passage of a kind, such as each piece of personal data, for redaction.
- Box / Boxes: a rectangle around one object, or around every instance with a count; the request must contain exactly one image.
Step 1: Get a key and pick a client
- Create an organization in the Liquid console (console.liquid.ai) and generate a key under Dashboard > API Keys. Keys start with
liquid_. Liquid's pricing page says every new organization starts with $2 in free credit. - Store it as an environment variable,
LIQUID_API_KEY, and keep it out of prompts and source files. - Decide how you will call it. The endpoint is
POST https://api.liquid.ai/decisions/v1/systemoneand it implements TypeSafe's System One API, so the TypeSafe SDKs work (pip install typesafe-sdkornpm install @typesafe-ai/sdk) with the base URLhttps://api.liquid.ai/decisions.
Important: the docs state the SDKs can only read Noul, Choice and Score answers right now. They drop the new typed answers from the response, and a multiple-choice question makes the call fail. For invoice reading, spans, boxes, images or audio, call the endpoint over plain HTTP (for example Python requests). In TypeScript the docs also set compression: false, because the API does not accept zstd-compressed request bodies.
Step 2: Build a support-ticket router in one request
The docs' "Combining Question Types" example is the most practical starting point. One ticket goes in as a JSON string (message plus account fields such as plan and ARR), with three questions:
is_bug(Noul): is this a software bug rather than a usage question or account issue?team(Choice): billing, engineering, frontend or account, each with a one-line description.urgency(Score): Low / Medium / High, with SLA wording inside each level.
In Liquid's published response for a checkout crash blocking a $4,200 order, is_bug came back at 0.974, team picked engineering at 0.75 with frontend at 0.22 (confidence 0.66), and urgency scored 1.954 on the 0-2 scale. Those are the vendor's example numbers, not our test. The useful pattern is what you do with them in code:
- Treat
is_bug > 0.7as a bug. - Escalate when it is a bug and urgency is above 1.5; prioritize when urgency is above 1.0; otherwise queue normally.
- When the team confidence drops below 0.5, log the runner-up option from
probabilitiesand send the ticket to a human.
That last step is the real advantage over a parsed LLM reply. You get a number you can set a threshold on, instead of a label that sounds equally sure every time. Liquid's launch post reports calibration error of 0.8 points for d1.2-ultra and 1.2 for d1.2 across 13 benchmarks; that is a vendor claim, so check it on your own labeled tickets before you trust the thresholds.
Writing better criteria
- Describe each Choice option by what belongs in it ("Charges, invoices, refunds, payment methods"), not just a one-word name.
- Put the business rule inside Score levels ("handle within 4 hours"), so the scale means something to your team.
- Pass structured context as JSON in the state. The ticket example includes the customer's plan and ARR, which the urgency question can weigh.
Step 3: Read values from an invoice
For extraction, use text, number and date questions over HTTP. The official example sends a four-line invoice and asks for payee, total, due date and VAT. The invoice does not show VAT, and the documented answer for vat is null with found: 0 rather than a guessed figure. Each found value also comes back with the original text and a span (character positions), so you can highlight where it was read from in a review screen.
Two behaviors to plan for:
- Values are read, not converted. "1 234,50 EUR" returns 1234.5 with unit EUR; currency conversion is your job.
- Dates follow the document. If the invoice says "03/04/2026 (day/month/year)", the answer is 2026-04-03. If your documents are ambiguous about date order, say so in the state.
For scanned invoices, send the image in the top-level images array as a base64 data URL. Liquid says an image costs 1.5 tokens per 32x32-pixel patch at the text rate, so a 1024x1024 scan is 1,536 tokens.
Step 4: Choose d1.2 or d1.2-ultra
Both use the same endpoint, request format and question types, and both accept text, images and audio with a 65,536-token input limit per question. Switching is one field: "model": "d1.2-ultra". Start on d1.2 and move a specific question to ultra only if your own labeled sample shows it misses. In Liquid's internal tests on the new tasks the gap is small (for example 98% vs 96% on reading receipt values, 93% vs 88% recall on finding personal data), and d1.2 even scored higher on picking every object in a photo (90% vs 87%).
Pricing and alternatives compared
All prices below are from Liquid's own docs and pricing page, checked on the date at the bottom of this post. The generative row is included as the "just use a small LLM" baseline from the same vendor.
| Model | Input / 1M tokens | Output / 1M tokens | Inputs | Best for |
|---|---|---|---|---|
| d1.2 | $0.02 | $0 (no output) | Text, images, audio | Default for routing, gates, extraction |
| d1.2-ultra | $0.042 | $0 (no output) | Text, images, audio | Harder decisions where d1.2 misses |
| d1.1 / d1-ultra (deprecated) | $0.02 / $0.042 | $0 | No audio, no typed answers | Migrate: change model only |
| LFM3-1.7B (generative) | $0.08 | $0.20 | Text | When you need written text back |
To make that concrete, we did the math for two jobs (see our cost table at the end of this post). Assuming roughly 600 billed tokens per ticket (our assumption, not a measurement), 100,000 tickets would cost about $1.20 on d1.2 and $2.52 on d1.2-ultra. For 10,000 scanned 1024x1024 invoices at about 1,836 tokens each, it is roughly $0.37 and $0.77. The $2 starter credit covers 100 million input tokens on d1.2. Note the per-request rule: the state, images and audio are billed once, and each extra question adds only its own tokens, so asking five questions in one call is much cheaper than five calls.
Editor's note
Good for: teams already paying a chat model to classify, route, score or pull fields out of text and scans, and anyone who wants a probability to set a review threshold on.
Not for: anything that needs a written reply, a summary or open-ended reasoning in the output.
Gotchas we found in the docs:
- SDK silently drops typed answers. If
totalorpiiis missing from your result, you are probably using the TypeSafe SDK; switch that call to plain HTTP. - 422 errors: sending a typed question to d1, d1.1 or d1-ultra returns 422. Validation errors also return 422, so check the model name first.
- Box or boxes questions need exactly one image in the request.
spansandboxesread up to 16 items by default. Ifat_leastis true, there may be more; raisemax(up to 64). Each spans or boxes question costs about 250 to 415 tokens at the default, more asmaxgrows.- Limits: up to 128 questions and 4.5 MB per request, 250,000 bytes of text per question. Korean, Japanese and Chinese text can hit the byte limit before the token limit.
- Not on OpenRouter or Vercel yet for d1.2: the launch post says "coming soon", and the pricing page currently lists only Liquid for d1.2 and d1.2-ultra.
FAQ
Q: Does d1.2 ever generate text?
A: No. It returns probabilities, chosen options, scores and values read from the input (with their positions). Output tokens are always zero, which is why output is free.
Q: Can I keep my old d1 code?
A: Yes for Noul, Choice and Score. The docs say the request and response format is unchanged; change model from d1 or d1.1 to d1.2, or from d1-ultra to d1.2-ultra. The old models are deprecated and cannot do the new tasks or audio.
Q: Is there a free tier?
A: There is no ongoing free plan for the hosted API listed on the pricing page, but every new organization starts with $2 in credit. Liquid's separate open-weight decision models can be run on your own hardware under the LFM license, which is free below $10M annual revenue.
Related on lightmind24
- When a Small Decider Beats a Frontier LLM: Strands Decider
- Inkling 2 Small: Run It Locally or via API, Which Route Fits
- OpenRouter Pricing: Free Models, 5.5% Fee and BYOK
If your "AI feature" is really a multiple-choice question, try answering it with a decision model before you pay a chat model to write JSON.
Images: screenshots of Liquid AI's d1 docs, decisions guide, d1.2 launch post and pricing page, plus our own cost table; see the official screenshots at the end of this post.
lightmind24 is an independent review site, not affiliated with Liquid AI.
Last verified: 2026-11-18
Sources:
Liquid AI Docs: d1.2
Liquid AI Docs: Decisions guide
Liquid AI blog: d1.2 launch (Nov 16, 2026)
Liquid AI pricing
댓글
댓글 쓰기