Model detail
jev-1.13.0
Jev is a structured decision model from TypeSafe, and the first of its System One models. System One models make fast, structured decisions for software, returning a typed choice rather than free-form text. It is suited for routing, classification, and other decision points inside an application where a fast, predictable answer matters more than generated prose. Learn more in TypeSafe's docs: https://docs.typesafe.ai/concepts/system-one
Model specs
- Context length
- –
- Max output
- –
- I/O modalities
- –
- Released
- 2026-09
02
API endpoints
One MixRoute gateway, OpenAI-compatible
-
Typesafe
/typesafe/v1/systemonePOST
03
Pricing
Flat rate, unit: /1M Tokens
Input
$0.0420 /1M Tokens
Completion
$0.0000 /1M Tokens
05
Selection summary
Quickly judge whether it fits your workload
What is this model good for?
Jev is a structured decision model from TypeSafe
Jev is a structured decision model from TypeSafe, and the first of its System One models. System One models make fast, structured decisions for software, returning a typed choice rather than free-form text.
What should you check before using it?
64,000 context tokens
jev-1.13.0 supports structured output. Released 2026-09-15.
Why use it through MixRoute?
jev-1.13.0 runs tools and structured output here
Tool calling and structured output run on that route as well. MixRoute serves jev-1.13.0 on the OpenAI-compatible endpoint /v1/chat/completions; point your existing client at https://api.mixroute.ai/v1 with the model ID jev-1.13.0 and re-run your integration tests.
07
Capabilities & compatibility
Unconfirmed capabilities stay "Unknown," no guesses
Structured output
jev-1.13.0 can produce JSON-formatted output on demand.
response_format: { type: "json_schema" } forces valid JSON output.
08
Token cost estimator
Live estimate from this page's pricing, not an actual bill
This model has no cache-read price; caching is not counted
One endpoint, a testable decision
Test this model and alternate routes with the same request format
Start from a real workload, then let quality, total cost, and failure conditions decide whether to send production traffic.