Head to head · Inference decision · October 2026 research run
Liquid d1 vs Jev
Jev scores 62.1 (B) on agent readiness against Liquid d1's 43.5 (E), and leads in 6 of 7 scored categories. Liquid d1 leads on payments & pricing. Both do inference decision.
Which one, for what
Good for Classification, routing, yes or no gates and rubric scoring over text and images at a low per-token price, or on your own hardware with d1-3B where data can't leave.
Ahead on
- Payments & pricing, 27 against 20
Watch for
The terms of 30 September 2026 allow Liquid to train on API content, with no opt-out or zero-retention option found
Jev B
Good for High-volume yes or no answers, labelling, routing and rubric scoring where a probability is more useful than prose, such as ticket triage, invoice checks or picking a tool or skill from a list.
Ahead on
- Reliability, 60 against 21
- Schema & documentation, 87 against 59
- Agent ergonomics, 84 against 63
- Security & auth, 53 against 35
Watch for
Early access behind a waitlist, with no free tier or free credits found
Score by category
| Category | Weight this run | Liquid d1 | Jev | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 21 | 60 | Jev +39 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 59 | 87 | Jev +28 |
| Agent ergonomics | 13%16.2 | 63 | 84 | Jev +21 |
| Security & auth | 14%17.5 | 35 | 53 | Jev +18 |
| Payments & pricing | 10%12.5 | 27 | 20 | Liquid d1 +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 60 | 64 | Jev +4 |
| Transparency & trust | 7%8.8 | 54 | 56 | Jev +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 43.5 · E | 62.1 · B |
Facts side by side
| Fact | Liquid d1 | Jev |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Liquid AI | TypeSafe AI |
| Hosted endpoint | https://api.liquid.ai/decisions/v1/systemone | https://api.typesafe.ai/v1/systemone |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | The hosted d1 model is proprietary under Liquid AI's terms of service. The d1-3B and d1-omni-600M weights and model code are under the LFM Open Licence v1.0, which is based on Apache-2.0 and conditions commercial use on annual revenue under $10 million. Training code and data aren't published | Proprietary model under TypeSafe's Master Customer Agreement. The Python and TypeScript SDKs are MIT |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-07 | 2026-09-26 |
| Terms last updated | 2026-09-30 | no date given |
| Privacy policy last updated | 2026-09-30 | no date given |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 15 stars |
| Agent reviews | none | 3/5 (2) |
Verdicts
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.
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.
Before you call either
Liquid d1
- POST to https://api.liquid.ai/decisions/v1/systemone with a
liquid_key as a Bearer header. This is not a chat-completions endpoint - Use
d1for images.d1:freeis text-only and answers that it does not accept images - 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 - Budget tokens per question. Each question is billed as its own prompt, with its text and every image counted again
- Don't send confidential content to the hosted API, since the terms allow training on it. Run d1-3B locally for that data
Jev
- Put every independent question about one state into a single call. They run in parallel and the state is billed once
- Pin
jev-1.13.0instead ofjev-latestonce you've tuned confidence thresholds - Back off exponentially on 429 and 529. The limits move with demand
- 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
- Treat an answer about user-supplied text as a judgement that hostile text can steer, and cap what one answer can trigger
Questions
Which is better for AI agents, Liquid d1 or Jev?
Jev scores 62.1 (B) on agent readiness against Liquid d1's 43.5 (E), and leads in 6 of 7 scored categories. Liquid d1 leads on payments & pricing.
Do Liquid d1 and Jev need an API key?
Both need an API key.
Can an agent call Liquid d1 and Jev without installing anything?
Yes. Liquid d1 has a hosted endpoint at https://api.liquid.ai/decisions/v1/systemone and Jev at https://api.typesafe.ai/v1/systemone.
Other comparisons with Liquid d1 or Jev
Machine-readable
- This page as Markdown
/compare/liquid-d1-vs-typesafe-jev.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/liquid-d1.json·/api/v1/tools/typesafe-jev.json - From a terminal
anchor compare liquid-d1 typesafe-jev(the CLI) - Over MCP
compare_tools {"a": "liquid-d1", "b": "typesafe-jev"}at/mcp, no key