Jev vs GPT-5.6 Luna
TypeSafe AI's scoring model against OpenAI's cheapest general model, for the job of tagging and routing text.
Pick Jev from TypeSafe AI if you run high-volume sorting and scoring where output token billing inflates your monthly invoice. Pick GPT-5.6 Luna from OpenAI if your classification pipeline must draft natural language explanations, extract text, or evaluate calendar dates. In machine learning, Jev refers strictly to the scoring model launched in early access by TypeSafe AI on September 15, 2026.
At Layer3Labs, we design automated intake systems and classification pipelines for client operations, and the decision between specialized classifiers and general large language models (LLMs) turns on whether your downstream software expects text or structured categories. GPT-5.6 Luna is OpenAI's lowest-cost general tier, operating at $0.20 per million input tokens and $1.20 per million output tokens following its July 30, 2026 price cut. Jev takes an opposite architectural direction by eliminating output tokens entirely, billing a flat $0.042 per million input tokens while returning a decision and a confidence score.
Testing Jev requires entering an early-access waitlist or using its browser playground. TypeSafe AI documents no free tier and no complimentary credits.
Jev vs. GPT-5.6 Luna: Side-by-Side
| Dimension | Jev | GPT-5.6 Luna |
|---|---|---|
| Primary output format | Typed decisions (Choice, Score, Noul) with confidence scores | Unconstrained text strings or schema-constrained JSON documents |
| Cost per 1M input tokens | $0.042 per million input tokens | $0.20 per million input tokens ($0.02 cached) |
| Output token billing | Free ($0.00) | $1.20 per million output tokens |
| Can it generate text | No (cannot write prose, code, or explanations) | Yes (full text, conversational prose, code generation) |
| Confidence scores | Yes (trained via RLCD for decision calibration) | No native calibration scores returned |
| Published latency | 70 to 500 ms end-to-end (vendor-reported) | Not published by OpenAI for this tier |
| Access model | Early-access waitlist and browser playground | OpenAI API and Codex (general availability) |
| Production maturity | Early access (launched September 15, 2026) | Production tier (price cut July 30, 2026) |
Suggest a correction — if you work at one of the products above and something here is out of date, tell us and we'll fix it.
Core Architecture and Interface Design
Jev classifies input text into predefined categorical slots without generating strings, while GPT-5.6 Luna predicts sequential tokens to form sentences or schema-compliant JSON documents. Diogo Almeida, formerly of OpenAI, founded TypeSafe AI to build Jev as what TypeSafe calls a System One model. It relies on Reinforcement Learning for Calibrated Decisions (RLCD) to optimize categorical selection rather than conversational fluency.
The interface for Jev consists of three specific question types. Choice asks the model to select one option from a predefined set of up to 255 entries, returning the selected value, a full probability distribution, and a confidence score. Score places an input onto an ordered scale with defined rubric tiers, providing tier distributions alongside a confidence metric. Noul handles binary true-or-false determinations, returning a direct probability between 0 and 1 without a separate confidence field.
All questions in a Jev API call run in parallel across the same input text. Adding twenty rubric checks to a request costs only the additional input tokens required to define the questions. In contrast, running twenty separate extractions through GPT-5.6 Luna with structured outputs requires generating dozens of JSON keys and string values, expanding the billed output footprint on every run. Our overview in GPT-5.6 Luna explained covers how OpenAI handles schema enforcement.
- Jev interface: Choice (up to 255 options), Score (rubric tiers), and Noul (binary probability)
- Question processing: All questions in a single Jev request execute in parallel against identical state
- Luna interface: Standard completions and tool calls outputting variable-length strings or JSON objects
Pricing Math and the Output Token Gap
Jev costs $0.042 per million input tokens with free output, whereas GPT-5.6 Luna bills $0.20 per million input tokens and $1.20 per million output tokens. The price gap between these models is wider than input rates suggest. On short-answer classification tasks, output token pricing represents the bulk of an OpenAI invoice because output tokens cost six times more than input tokens.
Consider a concrete enterprise scenario: an automation pipeline processes 100,000 documents per month, averaging 1,000 input tokens per document. If GPT-5.6 Luna returns a compact 50-token JSON response containing a label and metadata, the bill splits into two tiers. The 100 million input tokens cost $20.00, while the 5 million output tokens add $6.00, yielding a $26.00 monthly expense.
Running that identical 100,000-document workload through Jev consumes 100 million input tokens at $0.042 per million. Because output decisions carry zero charge, the total bill comes to exactly $4.20. For teams comparing broader market rates, Anthropic's Claude Haiku 4.5 ($1.00 input and $5.00 output per million tokens) would cost $125.00 for the same task, as detailed in our analysis of Jev vs Claude Haiku 4.5. Full details on TypeSafe AI's rates appear in our guide to Jev pricing.
- 100,000 calls (1,000 input tokens, 50 output tokens): Jev costs $4.20 total
- 100,000 calls (1,000 input tokens, 50 output tokens): GPT-5.6 Luna costs $26.00 total
- 100,000 calls on Claude Haiku 4.5: $125.00 total under identical volume assumptions
- Cached inputs: GPT-5.6 Luna offers a $0.02 per million token cached rate for static system prompts
Decision Calibration Against Structured Outputs
Jev returns mathematical confidence scores across candidate choices, whereas GPT-5.6 Luna returns structured values without native confidence calibration. When building triage systems, automated software needs to know when an assessment is doubtful. GPT-5.6 Luna can output a numerical confidence field if prompted, but that number is a generated token sequence rather than a statistical distribution.
TypeSafe AI trains Jev using RLCD to align its internal distribution with classification outcomes. Calibration is a training objective. It does not guarantee the answer is correct on any particular task. A probability score of 0.85 indicates strong model certainty relative to its training distribution, but it does not guarantee that the factual answer will be correct 85 percent of the time on your specific proprietary records. Confidence values on Choice and Score questions are calculated directly from the distribution spread across available options.
Structured outputs in GPT-5.6 Luna solve a different operational problem. OpenAI guarantees that output conforms perfectly to a supplied JSON schema, preventing parsing errors in API pipelines. Luna cannot tell you how close the second-place category was to being selected without external multi-sample sampling. Jev preserves the entire distribution, allowing automated systems to route borderline evaluations to staff review.
Published Accuracy and Functional Boundaries
TypeSafe AI's internal dashboard places Jev at an aggregate accuracy score of 67.8 percent, trailing an unidentified top comparator that achieved 74.1 percent. Across individual tasks on the dashboard, Jev's accuracy ranges from 61.7 percent to 76.0 percent. TypeSafe AI publishes these metrics directly, documenting that Jev trades raw accuracy points in exchange for low latency and zero output cost. No independent or third-party benchmark of Jev exists as of September 22, 2026.
Functional limitations form a clear dividing line between the two tools. Jev cannot write prose, explain its decisions, or generate programming code. TypeSafe AI documentation explicitly warns that Jev cannot perform arithmetic, count items, execute date comparisons, or conduct indirect reasoning. TypeSafe AI instructs developers to keep exact calculations in their application code and restrict Jev queries to direct categorical judgments.
GPT-5.6 Luna handles open-ended text processing that Jev cannot attempt. Luna drafts client correspondence, explains legal terms, performs basic calculations, extracts variable-length text entities, and reasons across temporal schedules. If a workflow requires answering 'Why was this claim flagged?', Jev cannot answer. Pairing a specialized classifier with a general model often resolves this tension.
- Jev benchmark score: 67.8% aggregate accuracy on TypeSafe AI's internal dashboard
- Best comparator score: 74.1% aggregate accuracy (unidentified model in TypeSafe AI testing)
- Jev hard boundaries: No arithmetic, no counting, no date comparison, and no text generation
- Luna boundaries: Requires strict schema prompting to prevent unneeded conversational filler
Operational Speed and Ecosystem Integration
TypeSafe AI reports end-to-end response times between 70 and 500 milliseconds for Jev, while OpenAI has not published official latency metrics for GPT-5.6 Luna. Diogo Almeida has stated that Jev operates 20 to 200 times faster and 40 to 400 times more cost-efficiently than conversational models, though these figures represent vendor claims rather than independent lab audits.
Vendor-reported creator demonstrations showcase specific processing speeds. TypeSafe AI documents 724 advertisements analyzed in 40 seconds for $0.09, 384 headlines triaged in 24.9 seconds for $0.19, and an automated browser flight search completed in 7 seconds for $0.0039. A community project called JevSEO, documented at jevseo.epergaboni.com, demonstrates this throughput in website auditing. JevSEO combines 20 deterministic code checks with about 25 semantic reading questions sent to Jev in one request, scoring pages across SEO, AEO, and GEO metrics for a cost the project puts at roughly $0.0001 per page in about 2.3 seconds.
Access models differ significantly. GPT-5.6 Luna is generally available across OpenAI's global API infrastructure with standard billing. Jev remains restricted to an early-access waitlist, a browser playground, and an experimental Requesty integration (typesafe/jev-1.13.0). Cloudflare maintains documentation for Jev on Cloudflare Workers AI, following coverage by Forbes on September 19, 2026 reporting that Vercel and Cloudflare moved quickly to integrate the model.
Workload Routing and Production Decision Rules
Deploy Jev when a system processes high volumes of text strictly to route, filter, or score records against predefined options. Good fits include customer ticket routing, content moderation flagging, sentiment categorization, and document triage. Jev's 32,000-token request budget (approximately 150,000 English characters) provides ample room for substantial context.
Deploy GPT-5.6 Luna when your application needs to write sentences, create summaries, or complete complex reasoning steps. Luna fits customer email drafting, data extraction requiring free-form string outputs, and tasks demanding multi-step logic. The trade is a real one. You accept higher token costs and get natural-language flexibility.
In our legal intake and CRM automation engagements at Layer3Labs, a frequent failure mode is using an expensive generative model for basic boolean routing, or conversely using a classifier for jobs that require written justification. If your team cannot tolerate early-access waitlists or experimental API endpoints, GPT-5.6 Luna is the safer operational choice today.
- Select Jev: High-volume triage, automated tagging, and score rubrics where output prose is unneeded
- Select GPT-5.6 Luna: Generative drafting, variable entity extraction, code writing, and production SLA requirements
- Hybrid approach: Use Jev as a rapid low-cost triage filter, then pass flagged exceptions to GPT-5.6 Luna for drafting
The Verdict
Choose Jev if your priority is cutting token costs on structured classification tasks where no output prose is required. At $0.042 per million input tokens and free output, Jev provides unmatched price performance for high-frequency sorting and scoring. Choose GPT-5.6 Luna if your workflow requires generating text, performing arithmetic, explaining decisions, or relying on stable general-availability infrastructure.
This recommendation would change if OpenAI cut GPT-5.6 Luna output token pricing down to its input token level. It would also change if TypeSafe AI failed to move Jev off the early-access waitlist into stable commercial availability. To establish which model serves your stack, sample 500 records from your backlog and evaluate classification accuracy against total token expenditure.
Researched from primary vendor documentation and public regulator sources. Pricing and availability are accurate as of Sep 22, 2026 and can change — confirm current terms with each vendor before you buy.
Frequently Asked Questions
- Jev is substantially cheaper for classification tasks. Jev charges $0.042 per million input tokens with free output tokens, while GPT-5.6 Luna charges $0.20 per million input tokens and $1.20 per million output tokens. On a 100,000-request workload with 50 output tokens per call, Jev costs $4.20 compared to $26.00 for GPT-5.6 Luna.
- No. Jev cannot produce text, generate code, or draft explanations. It only returns typed values corresponding to Choice, Score, or Noul question definitions. If your application needs natural language output, use GPT-5.6 Luna.
- TypeSafe AI documents no free tier and no trial credits for Jev. Access is currently managed through an early-access waitlist and a browser playground, with usage billed at published token rates.
- Jev outputs mathematical confidence scores across candidate choices derived through RLCD training. GPT-5.6 Luna structured outputs guarantee that generated strings conform to a JSON schema, but Luna does not attach a native confidence score to the value it picks.
- No. TypeSafe AI documentation explicitly states that Jev cannot do arithmetic, counting, or date comparisons. Developers must execute mathematical operations and date logic in application code before querying Jev.
- Jev has a request budget of roughly 32,000 tokens, which TypeSafe AI describes as approximately 150,000 English characters. All questions in a request evaluate concurrently against this shared state.
Need help benchmarking classification models for production?
Layer3Labs designs and evaluates automated document classification pipelines. We analyze your volume, accuracy needs, and infrastructure requirements before you build.
Get a Free Audit