TypeSafe Models

2 modelsGeneral models from $0.0462/M inputUp to 64K contextOfficial site ↗

Usage

Last 7 days · 2026-09-18 to 2026-09-24

Tokens

5.2B

Requests

344K

Models in use

2 of 2

Tokens per day, stacked by model

0850M1.7B09-182026-09-18 — 3,286,210 tokens jev-latest: 3,172,305 jev-1.13: 113,9052026-09-19 — 28,004,685 tokens jev-latest: 20,072,910 jev-1.13: 7,931,7752026-09-20 — 334,078,860 tokens jev-latest: 301,534,175 jev-1.13: 32,544,6852026-09-21 — 1,124,445,330 tokens jev-1.13: 1,112,296,350 jev-latest: 12,148,9802026-09-22 — 638,614,630 tokens jev-1.13: 626,035,855 jev-latest: 12,578,7752026-09-23 — 1,348,670,650 tokens jev-latest: 702,802,680 jev-1.13: 645,867,9702026-09-24 — 1,699,090,665 tokens jev-1.13: 1,626,624,275 jev-latest: 72,466,390
  • jev-1.13
  • jev-latest

Which models that traffic went to

  1. Jev 1.1378.3%4.1B
  2. Jev21.7%1.1B

Share of 5.2B tokens.

The two views disagree on purpose: a model can take a large share of the calls and a small share of the tokens — many short requests — or the reverse. Which one matters depends on whether your cost is driven by call volume or by prompt length. Measured on AIHubMix over the last 7 days, counting the 2 model IDs listed on this page; traffic routed through upstream-specific IDs that are not in the public catalog is not included.

All 2 TypeSafe Models

Open in model list
TypeSafe models on AIHubMix with input and output modalities, context length, maximum output, price per million tokens including cache read and cache write rates, and measured throughput and latency.
Modalities
jev-1.13Takes text. Output modality not published.64K$0.0462$0.0462/M
jev-latestTakes text. Output modality not published.64K$0.0462$0.0462/M

Prices are USD per million tokens; cache read and cache write are the rates for prompt-cache hits and for writing a prompt into the cache. Throughput and latency are measured on AIHubMix — the same figures the model detail page shows — not vendor claims. A dash means the catalog does not publish that field for that model, which is not the same as the model not supporting it.

TypeSafe on AIHubMix

Which TypeSafe model should I start with?

jev-1.13 at $0.0462/M input — the cheapest entry here that declares a token price, and it carries a 64K context. Move up to jev-latest when answer quality matters more than cost.

Why are there several entries for the same model?

Because each row is a route you can call, not a model release. Some IDs name an upstream (azure-, alicloud-, cc-), and some differ only in capitalisation, kept so older integrations keep working.

The catalog does not carry a field saying which of those a given row is, so this page does not sort them into buckets it would have to invent. Every row shows that route’s own price, context and speed — compare those directly, and open a model to see the upstreams that serve it.

Do I need a separate TypeSafe account?

No. One AIHubMix key covers every model on this page, and switching between them is a change to the model string — billing, rate limits, and logs stay in one place.

Start calling TypeSafe in one line

One key, one endpoint, 908 models across 41 model authors.