TypeSafe
•
Jev 1.14
•
Released 
October 2026

TypeSafe
Jev 1.14

Typed yes/no, choice and score decisions with probabilities, built for routing and triage inside software instead of text generation.

Modality:
Text
model ID
typesafe/jev-1.14

Output Speed *

N/A
tok/s

Intelligence Index *

N/A
/ 100

Context Window *

262144
tokens

Input price

0.252
Anytoken

Output price

0
Anytoken
Jev 1.14: Typed Decisions With Confidence Scores, Not Generated Text Jev 1.14 is TypeSafe's System One decision model and the second Jev release. It does not write text. You send a state plus typed Noul, Choice, Score or Box questions and get typed answers with probabilities and confidence. This release adds experimental image input, Box bounding-box questions and an opt-in 262K-token context mode. TypeSafe expects the largest gain over Jev 1.13 in multilingual support. It fits routing, classification, triage and guardrail decisions inside applications. Add Jev 1.14 to your decision pipeline through AnyAPI.ai

Performance

Parallel typed answers replace a generate-and-parse loop

Jev 1.14 answers every question in a request in parallel and returns probabilities, so one call can yield routing, urgency and sentiment signals. For the Jev family, TypeSafe reports 70–500 ms end-to-end responses and 40–200x faster results than frontier LLMs. These figures come from workflows built by TypeSafe's own team, which it says may be biased, and are not specific to 1.14. In production, Jev suits high-frequency decision points where an LLM call would dominate latency. Validate speed and accuracy on your own labeled traffic.

Technical Specifications

What the model supports

Jev 1.14 accepts text, JSON or string-array state, plus PNG/JPEG images behind an opt-in header, and returns typed answers rather than prose. Default limits are 64K tokens per request and 32K per question. The long-context header raises both to 262K at the same per-token rate, but with lower speed and accuracy. Because the output is a typed decision, input size and question design are the practical constraints. Box questions work only on 1.14, not on 1.13.
Verified Specifications — 
Jev 1.14
*
Input modalities
Text
output modalities
Text
Context window
262144
 tokens
Maximum output tokens
235929
Reasoning
No
Knowledge cutoff
October 2026
Pricing (standard)
0.252
 AnyTokens in
 / 
0
 AnyTokens out

Comparison

Jev 1.14 or Jev 1.13: What Actually Changes?

Jev 1.13 is the direct predecessor and shares the same state-plus-typed-questions interface. TypeSafe describes 1.14 as small improvements across the board, with the largest expected gain in multilingual support. Box questions are exclusive to 1.14. Both models accept images behind the danger-zone header and both support the opt-in long-context mode. The input price is unchanged. The decision is whether the newer model's gains justify re-checking thresholds you tuned on 1.13.

Dimension
Jev 1.14
Jev 1.13
Context window *
262144
tokens
262144
tokens
Output speed *
N/A
tok/s
N/A
tok/s
Intelligence Index *
N/A
N/A
Input pricing
0.252
AnyToken
0.252
AnyToken
Output pricing
0
AnyToken
0
AnyToken
Knowledge cutoff *
October 2026
September 2026

Choose Jev 1.14 when your inputs include non-English text, when you want to test Box questions on images, or when you are starting a new integration. Choose Jev 1.13 when confidence thresholds are already tuned against it and you want results to stay stable. TypeSafe keeps 1.13 available and has promised 60 days' deprecation notice, against 30 days for 1.14. Pin a versioned ID rather than a moving alias either way.

Limitations & Trade-offs

Where Jev 1.14 falls short

1
No text generation. Jev 1.14 returns typed answers only, so it cannot draft replies, summarize, write code or explain its decision. Pydantic AI's integration docs note that a route needing a free-text field must escalate to a language model. Workloads that need prose, open-ended reasoning or rationales still need a generative LLM. Jev works best as the decision layer in front of or beside one, not as a replacement for it.
2
Experimental features carry reliability costs. Image input, Box questions and the 262K context mode are opt-in, and TypeSafe says they are not production-ready. TypeSafe warns that every model, Jev included, does worse on images than on text. Box always returns a box, even when the object is absent, so pair it with a Noul existence check. Long context is slower and less accurate than the default limits. Use these features for prototypes, not critical paths.
3
Thin public benchmark evidence. TypeSafe's release post shows internal intelligence charts that compare Jev only against open-weight models and gives no numeric score table. TypeSafe says the measurement is probably biased toward its own models and tells developers to favor their own evals. There is no verified independent benchmark for 1.14. Teams that need documented accuracy before adoption should build a labeled test set and compare Jev against their current LLM judge or classifier.
4
Non-standard API and parallel questions. Jev does not run on chat-completions endpoints, so chat SDK code needs a different request shape. Questions in one request are answered in parallel and cannot depend on each other. A decision that needs another answer first requires two sequential requests. Aliases such as jev-latest move when new releases ship, which can shift probability thresholds you have tuned. Pin the versioned ID if your thresholds are fixed.

Best-Fit Workloads

Where this model earns its place

01

Routing and triage

‍
Jev 1.14 is positioned for routing, classification and other decision points where a fast, predictable answer matters more than prose. One request can return department, urgency and sentiment together, each with its own probability. It is the decision model behind AI/ML API's Jev Router, which uses it to pick the bucket a chat request belongs to. Use it for support triage, model routing and content tagging. Handle low-confidence cases with a human or an LLM.

02

Confidence-gated automation

‍
Every Jev answer carries probabilities and a confidence estimate, so code can decide when to act autonomously and when to ask for review. That suits approvals, moderation and agent guardrails where the cost of a wrong action is uneven. Pydantic AI's docs say a Jev-based guard belongs alongside deterministic checks. Injected text in the state can sway its answers, so test with adversarial inputs before removing human review.

03

Multilingual classification

‍
TypeSafe expects the largest gain of 1.14 over 1.13 in multilingual support, which makes this release the one to evaluate for non-English tickets, comments and moderation queues. TypeSafe has published no per-language numbers, so treat the gain as a direction to test. Run your own labeled sample in each target language before routing production traffic on 1.14 thresholds.

04

Image questions and element location

‍
With the images header, 1.14 can answer yes/no or choice questions about PNG or JPEG images, and Box questions return one normalized bounding box with a confidence. Candidate uses include screenshots, scanned forms and locating a field or button. TypeSafe flags this as experimental and recommends the simplest possible questions. Each Box answer is a single box, so several targets need one question each.

Pricing in anytokens via AnyAPI
Input
0.252
₳
Output
0
₳
Cache write
—
₳
Cache read
—
₳

Integration

Access Jev 1.14 via AnyAPI.ai

Access Jev 1.14 through AnyAPI.ai using a unified API built for multi-model AI applications. Integrate Jev 1.14 without maintaining a separate provider-specific connection, and keep the flexibility to test, switch, or combine models as your application requirements evolve.

01

One API integration

Access Jev 1.14 and other AI models through the same API workflow instead of maintaining separate integrations for every provider.

02

Easy model switching

Test Jev 1.14 against alternative models or switch models as your performance, capability, or cost requirements change without rebuilding your application around another provider API.

03

Flexible for production

Use Jev 1.14 from experimentation through production while keeping your AI stack flexible as workloads, traffic, and model requirements evolve.

04

Multi-model applications

Use Jev 1.14 for the workloads where it performs best and combine it with other models for tasks that require different capabilities, performance, or efficiency.

Frequently Asked Questions

Answers to common questions about integrating and using this AI model via AnyAPI.ai

Jev 1.14 is TypeSafe's System One decision model, released October 14, 2026. It does not generate text. You send a state and typed questions (Noul, Choice, Score or Box) and receive typed answers with probabilities and confidence. TypeSafe positions it for routing, classification and other decisions inside software, and it is not an OpenAI-style chat model.

By default, Jev 1.14 accepts 64K tokens per request and 32K tokens for the state plus one question. Sending the TypeSafe-Danger-Zone-Long-Context header raises both limits to 262K tokens at the same per-token rate. TypeSafe says long-context mode is slower and less accurate, so use it only when a request needs it.

Yes, as an experimental feature. Jev 1.14 accepts PNG or JPEG images when the request includes the TypeSafe-Danger-Zone-Images header, and Box questions return a bounding box for an object. Jev 1.13 also accepts images, but Box questions need 1.14. TypeSafe warns that image performance is worse than text and says these features are not recommended for production.

TypeSafe bills Jev 1.14 per input token only, and output tokens are free. It kept the same input price as Jev 1.13, and long-context requests cost the same per token. Because it returns typed decisions instead of prose, cost depends on state size. The AnyTokens pricing component on this page shows the AnyAPI.ai rate.

Jev 1.14 cannot return a value outside your defined schema, so malformed or invented fields do not occur. It can still pick the wrong option, because a valid type is not necessarily a correct decision. Use the returned probabilities and confidence for thresholds, send low-confidence cases to review, and measure accuracy on your own labeled data.

* Benchmark data source: Artificial Analysis artificialanalysis.ai