Tool / product
TypeSafe Jev Pricing Explained: Token Costs and Workload Calculator
Understand TypeSafe Jev pricing: $0.042 per million input tokens, unmetered output, context limits, and an interactive calculator to estimate workload costs.
TypeSafe Jev is billed strictly on input tokens at $0.042 per million tokens ($42 per billion tokens), while output decisions are unmetered and completely free ($0.00). Because Jev evaluates application state and outputs structured mathematical primitives (Choice, Score, Noul) in a single forward pass, it skips autoregressive token generation entirely. For a production workload evaluating 100,000 customer tickets (averaging 350 input tokens each), total monthly inference cost is approximately $1.47.
Interactive Jev Workload Calculator
Use the calculator below to model monthly inference costs for your application workload. Adjust the average input tokens per request (state payload plus question criteria) and total evaluation volume:
Calculate Your Jev Workload Cost
Billed strictly at $0.042 per million input tokens ($42 per billion). Output tokens are unmetered ($0.00).
LLM comparisons assume prompt + 30 output tokens of structured JSON extraction. Equal token counts do not imply equal task quality; generative LLMs stream prose/JSON text while Jev evaluates structured decision heads directly.
* Estimate based on TypeSafe's published early-access rate of $0.042/M input tokens. Output pricing is $0.00 (unmetered output tokens). Excludes network transit costs.
Pricing Structure Breakdown
Unlike chat models where developers pay both input token fees and high completion token fees, Jev uses an asymmetric zero-output pricing model:
| Billing Metric | Rate | Notes |
|---|---|---|
| Input Tokens | $0.042 / 1M tokens | Billed on the combined length of the state payload and all question definitions ($42 per billion tokens). |
| Output Tokens | $0.00 (Free / unmetered) | Classifications, rubric scores, and probability values incur no generation billing. |
| Context Limit | 64,000 tokens | Total request budget (combined state payload plus longest question capped at 32,000 tokens). |
| Fine-Tuning | Not currently offered | Jev relies on prompt criteria and in-context state calibration. |
| Minimum Spend | None documented | Usage-based early-access billing via console.typesafe.ai. |
Cost Scenarios Across Common Workloads
To illustrate how the $0.042/M input rate translates into real operating costs, consider four common production scenarios:
1. Inbound Customer Support Triage
- Volume: 50,000 tickets/month
- Payload: 400 tokens (customer email + routing rubric)
- Total Tokens: 20,000,000 tokens
- Monthly Cost: $0.84
2. High-Frequency Real-Time Content Moderation
- Volume: 2,000,000 user comments/month
- Payload: 150 tokens (user submission + policy guidelines)
- Total Tokens: 300,000,000 tokens
- Monthly Cost: $12.60
3. Agent Tool Call Guardrails
- Volume: 500,000 tool executions/month
- Payload: 600 tokens (planned tool command + execution history + security criteria)
- Total Tokens: 300,000,000 tokens
- Monthly Cost: $12.60
4. Continuous Control Loop / Game Automation
- Volume: 10 requests/second continuous (25.9M requests/month)
- Payload: 250 tokens (game frame telemetry + valid action space)
- Total Tokens: 6.48 billion tokens
- Monthly Cost: $272.16
Architectural Cost Framing: Decision Evaluators vs. Generative Models
When evaluating whether to replace small generative models (such as GPT-4o mini or Gemini Flash) with Jev for classification or routing, developers should consider architectural fit rather than pure token math:
- Task Scope: Jev is purely a decision evaluator. It cannot produce freeform text, explain its reasoning, or rewrite content.
- Token Equivalence: Identical token volumes do not imply identical task capability. Generative models utilize multi-token autoregressive decoding to synthesize answers, whereas Jev evaluates state against predefined question options in a single forward pass.
- Cost Efficiency: Where a workflow strictly requires categorical routing, rubric scoring, or binary gating, Jev eliminates both output token charges and JSON parsing overhead, delivering sub-100ms evaluations at $0.042 per million input tokens.
Account Access and Quotas
During the current early-access phase, accounts generated via console.typesafe.ai operate under dynamic quota envelopes:
- Request Concurrency: Up to 1,200 requests per minute early-access ceiling.
- Throughput Ceiling: Up to 250,000 tokens per second early-access ceiling.
- Access Channels: Direct API access via TypeSafe console waitlist and instant on-demand access through OpenRouter.