Every TypeSafe model behind one OpenAI-compatible endpoint. You pay TypeSafe's published token rate — OrcaRouter adds $0. Below: live input, output and cached-input pricing per million tokens, context and output limits, measured latency, and the code to call any of them without changing your SDK.
| Model | Input per million tokens | Output per million tokens | Cached in per million tokens | Context | Max out | Quality | Try |
|---|---|---|---|---|---|---|---|
| Jev 1.13 | $0.042 | — | — | 65K | — | 5 | |
| typesafe/jev-1.14 | $0.042 | $0.042 | — | — | — | — | Try |
Estimate based on list price
Estimating cost for typesafe/jev-1.14: $0.420 per month
Estimates use the provider's published rates. OrcaRouter adds $0 markup, so this is what you would pay calling them directly.
Exactly the same as calling TypeSafe directly. typesafe/jev-1.14 is $0.042 per million input tokens and $0.042 per million output tokens; the cheapest TypeSafe model here is Jev 1.13 at $0.042 per million input. OrcaRouter adds $0 markup — you are billed the provider's published rate.
Yes. Add your own TypeSafe key in the console and OrcaRouter routes through it, so usage bills to your account with the provider while you keep the unified endpoint, logging, spend controls and automatic failover.
No. Point base_url at https://api.orcarouter.ai/v1, keep the OpenAI-compatible client you already use, and reference the model as typesafe/<model>. Nothing else in your code changes.
Jev 1.13, at 65K tokens. The full context and max-output limits for every TypeSafe model are in the pricing table above.
Every model page carries side-by-side comparisons against the closest models from other providers on price, context, latency and benchmarks. Because OrcaRouter adds no markup, the prices you are comparing are the providers' own.