We use cookies. Cookies and browser storage keep you signed in and remember your preferences. With your permission we also measure how the site is used. You can any time. See our cookie policy.

New here? See how it works A 1-minute tour of the playground, models and your API key.

d1 vs Jev 1.14: API price, context & features · api14

LiquidAI: d1 vs TypeSafe: Jev 1.14

A side-by-side comparison of LiquidAI: d1 ($0.07 / 1M tokens) and TypeSafe: Jev 1.14 ($0.15 / 1M tokens) using current USD prices and capabilities from the api14 catalog. Both run through the same OpenAI-compatible API.

Specifications

	LiquidAI: d1	TypeSafe: Jev 1.14
Provider	LiquidAI	TypeSafe
Input	$0.07 / 1M tokens	$0.15 / 1M tokens
Cache read	$0.07 / 1M tokens	-
Context window	65,536	262,144
Max output	58,982	235,929
Input	text, image	text, image
Output	decisions	decisions
Tool calling
Structured output
Reasoning control
Added	Oct 1, 2026	Oct 14, 2026

Key differences

LiquidAI: d1 is 52% cheaper on input tokens.
TypeSafe: Jev 1.14 reads 4.0× more context (262,144 tokens).
A request with 1,000 input and 500 output tokens costs $0.000070 with LiquidAI: d1 and $0.000147 with TypeSafe: Jev 1.14.

In depth

LiquidAI: d1 is a decisions model from LiquidAI, released on 1 October 2026. TypeSafe: Jev 1.14 is a decisions model from TypeSafe, released on 14 October 2026. Both sit in the same category, so neither is a general chat model in the usual sense; you call them when you want a decision returned rather than a paragraph of prose. The two providers are different companies, and the model ids you will use on api14 reflect that: liquid/d1 and typesafe/jev-1.14.

The clearest difference between them is context. TypeSafe: Jev 1.14 accepts up to 262144 tokens, four times the 65536 tokens that LiquidAI: d1 accepts. Both take text and image as input, and both return decisions as output, so modality is not a deciding factor here. Neither model lists supported parameters, and the qualitative notes do not mark either one as uniquely offering tools, structured output or reasoning, so on those axes there is nothing to separate them. On price, LiquidAI: d1 is the cheaper of the two on input; output pricing is about the same for both, so the input side is where the cost difference shows up.

For most tasks, pick based on how much material the model has to read before it decides. If your inputs are short or moderate (a single document, a screenshot plus a question, a compact set of options), LiquidAI: d1 is the sensible default, since it is cheaper on input and its 65536 token window is more than enough. If you are feeding long transcripts, large codebases, multi document bundles or long image heavy reports, TypeSafe: Jev 1.14 is the better fit because its 262144 token window lets you keep everything in one call instead of chunking and stitching decisions together yourself. Chunking a decision task tends to cost you accuracy, so the larger window is worth paying for when the input genuinely needs it.

Calling either model through api14 works the same way, because the API is OpenAI compatible. You point your client at the api14 base URL, send your request to the chat completions endpoint, and set the model field to the id you want. Switching between the two is a one line change: use liquid/d1 for LiquidAI: d1, or typesafe/jev-1.14 for TypeSafe: Jev 1.14. Your message structure, image parts and response handling stay identical, so you can build one code path and route between the models with a variable. The live price table on this page shows current rates for both.

There is one case where the cheaper model still wins even with a long input: if the extra tokens are mostly redundant context that you could trim without losing the decision relevant facts, LiquidAI: d1 keeps your input cost lower and its window may still be sufficient. Otherwise, when the length is real and unavoidable, TypeSafe: Jev 1.14 is the pick.

Switch with one string

Both models use the same endpoint and request shape. Change the model value from "liquid/d1" to "typesafe/jev-1.14" and prompts, streaming and tools keep working.

LiquidAI: d1 details & playground →TypeSafe: Jev 1.14 details & playground →

import OpenAI from "openai";

const client = new OpenAI({
  baseURL: "https://api14.com/api/v1",
  apiKey: process.env.API14_API_KEY,
});

const result = await client.post("/decisions", { body: {
  "model": "typesafe/jev-1.14",
  "state": "Customer: I was charged twice for my order and want my money back.",
  "questions": {
    "team": {
      "type": "choice",
      "instructions": "Which team should handle this message?",
      "criteria": {
        "billing": "Payments, refunds, invoices",
        "support": "Product questions and bugs",
        "sales": "Pricing and new purchases"
      }
    },
    "urgent": {
      "type": "noul",
      "instructions": "Does this need a reply today?",
      "criteria": {
        "true": "Money, outage or legal risk",
        "false": "Can wait"
      }
    }
  }
} });
console.log(result.answers);

LiquidAI: d1 vs TypeSafe: Jev 1.14

Specifications

Key differences

In depth

Switch with one string

More comparisons