Jev vs Kev: published benchmark comparison

Data: JevBench v1.7.23, published 2026-10-29 · method v1.7 (10 s rule), re-scored from the recorded per-decision times

Outside the Capability caps in v1.7.23.

Compare Jev-compatible models by separate measures and their measurement conditions. A historical measurement is not a current rank.

Jev and Kev: published axes and category radars

Pick any two. Radars for the score axes, capability by subject topic and use cases, chance-corrected competence per request type on the open and sealed sets, and competence per tier on each set. Further out is better on every spoke; the link keeps the pair.

System A

System B

A: Jev 1.13.0REFERENCE · TypeSafe — Jev — reference (TypeSafe, closed) · Score 71.4 (ranked, not ranked)
B: Kev 27B — Open weights · LLM decoder · Score 5.8 (ranked, not ranked)

The four score axes

0–100, the values in the table. An axis a system has no published value for is left as a gap (it counts as 0 in the composite).

Capability by subject topic

Linear signed scale: −100 at the centre, 0 on the bold middle ring, 100 at the rim.

What the decision is about — math and dates, coding, rules, money, support work, everyday messages, safety. Chance-corrected competence per category (0 = at or below chance; negative averages are reported as 0, 100 = perfect), Jev 1.13.0: S+P+L1+L2+L3; Kev 27B: S+P+L1+L2+L3 items pooled; only categories with at least 30 items are spokes, smaller ones are listed below. Hover a category for its definition and item count.

What each category means · items per category

Rules, policy & law — applying written rules: company policies, contracts, regulations, eligibility. 1616 items (151 open / 1465 sealed)
Coding & software — code, SQL, repositories, developer tools and IT systems. 382 items (62 open / 320 sealed)
Math & numbers — a calculation decides the answer: arithmetic, word problems, probability, dates, units. 370 items (37 open / 333 sealed)
Finance & commerce — money: payments, refunds, invoices, orders, expenses, insurance payouts. 223 items (12 open / 211 sealed)
Support & operations — support tickets, incidents, logistics, scheduling desks and routing work to a team. 160 items (21 open / 139 sealed)
Everyday language — short everyday messages: intents, assistant requests, reading a detail out of a text. 145 items (11 open / 134 sealed)
Safety & security — untrusted or injected instructions, fraud, moderation, access and security triage. 109 items (6 open / 103 sealed)

Use cases (TypeSafe categories)

Linear signed scale: −100 at the centre, 0 on the bold middle ring, 100 at the rim.

The real-world application area of each decision, after the TypeSafe use-case map; an item can count in two. Chance-corrected competence per category (0 = at or below chance; negative averages are reported as 0, 100 = perfect), Jev 1.13.0: S+P+L1+L2+L3; Kev 27B: S+P+L1+L2+L3 items pooled; only categories with at least 30 items are spokes, smaller ones are listed below. Hover a category for its definition and item count.A point on the bold 0 ring printed 0.0 is a measured value, not a gap: these published cells clip below-chance results to 0, so 0 means at or below chance. Their score markers cannot fall inside that ring.

What each category means · items per category

Model routing — deciding which LLM or model tier should handle a prompt; classifying a request's intent, domain, difficulty or risk to pick a model. 524 items (86 open / 438 sealed)
Legal and compliance — contracts, policies, regulations, eligibility rules, checking documents against written requirements. 515 items (74 open / 441 sealed)
Customer support — classifying tickets and customer intents, urgency, refunds, routing cases to a team, checking support replies. 240 items (37 open / 203 sealed)
Other — none of the above: general reasoning, arithmetic or date puzzles, everyday assistant requests without a business workflow. 174 items (24 open / 150 sealed)
E-commerce marketplaces — product listings, product attributes, orders and deliveries, seller catalog policy. 119 items (9 open / 110 sealed)
Insurance claims — first-notice-of-loss reports, claim complexity, missing information, claim triage. 119 items (9 open / 110 sealed)
Risk assessment — estimating probabilities and severity of risks, incidents, vendor or underwriting risk. 118 items (8 open / 110 sealed)
Financial crime — suspicious transactions, KYC, fraud alerts, entity matching for investigations. 101 items (9 open / 92 sealed)
Feature extraction for predictive modeling — turning natural-language data into probabilistic features or estimates for a downstream prediction. 99 items (5 open / 94 sealed)
Lead generation — matching companies or inbound messages to an ideal customer profile, buyer intent, prioritising and routing sales leads. 95 items (4 open / 91 sealed)
Recruiting — resumes, applications, interview feedback, matching candidates to roles. 94 items (1 open / 93 sealed)
Graphs and knowledge graphs — entity types, relationships between records, contradictions between facts, multi-step lookups across linked facts. 94 items (3 open / 91 sealed)
LLM guardrails — checking LLM inputs, outputs and tool calls: prompt injection, jailbreaks, policy violations, tool-call errors, answer quality. 93 items (5 open / 88 sealed)
Moderation and trust and safety — user content moderation: toxicity, harassment, spam, unsafe advice, personal data exposure. 93 items (7 open / 86 sealed)
Semantic code linting — checking code or writing against conventions and guidelines, as in CI review of code. 90 items (3 open / 87 sealed)
Search and retrieval — scoring query-to-candidate relevance, reranking results, selecting useful context for RAG. 90 items (5 open / 85 sealed)
Scientific discovery — screening papers, labelling research passages or survey answers, checking that citations support claims, methodology checks. 90 items (2 open / 88 sealed)
Advertising — ad creatives, campaign copy, brand safety, prohibited claims in ads. 88 items (3 open / 85 sealed)
Gaming — player reports, in-game chat, game support. 86 items (3 open / 83 sealed)
Demand forecasting — purchase intent, product interest, demand and supply signals for forecasting. 83 items (3 open / 80 sealed)

Competence per request type, open / sealed

Linear signed scale: −100 at the centre, 0 on the bold middle ring, 100 at the rim.

Chance-corrected competence for Choice, Noul and Score on the 300 open and 1200 sealed decisions.

Competence per tier — open set

Linear signed scale: −100 at the centre, 0 on the bold middle ring, 100 at the rim.

Per-tier competence, the three request types pooled by their published decision counts.

Competence per tier — sealed set

Linear signed scale: −100 at the centre, 0 on the bold middle ring, 100 at the rim.

Per-tier competence on the sealed decisions, types pooled the same way; item text stays private.

How the categories were made

O1S chance-corrected competence: equal mean across the request types present, clipped to 0–100. Zero means the equal-weight mean across present request types was at or below baseline; negative means are clipped. It does not mean every type scored zero. Choice uses a random-option baseline; Noul uses a fixed 50% accuracy baseline (abstentions count as wrong); Score uses the midpoint-guess error (random-guess fallback when every gold is at the midpoint). Compare models within a category; row pools and supported types can differ.

Categories use ruled subject-topic labels and authoring use-case precedence across the answered pool union, with stable item identities counted once.

Official O1S; recorded failures count where supported; no missing response is imputed; stable identity dedupe parent first.
S-based category cells pool recorded supported responses from S+P and the answered L1/L2/L3 supplements. API overlay category cells keep their separately recorded A4/A5+P union. Headline and per-type/tier scores are unchanged.

All values as a table

Spoke	A: Jev 1.13.0	B: Kev 27B
The four score axes
Intelligence	63.6	64.2
Calibration	90.6	93.7
Speed	91.2	82.8
Cost	54.7	18.3
Capability by subject topic
Rules, policy & law	49.4	54.7
Coding & software	64.3	77.3
Math & numbers	10.4	15.5
Finance & commerce	40.9	45.1
Support & operations	48.8	54.2
Everyday language	77.5	75.2
Safety & security	52.2	64.7
Use cases (TypeSafe categories)
Model routing	73.0	75.8
Legal & compliance	68.6	69.9
Customer support	49.6	49.2
Other	40.1	32.4
E-commerce	40.5	52.0
Insurance claims	46.1	45.7
Risk assessment	32.8	34.5
Financial crime	35.8	35.1
Feature extraction	28.3	31.0
Lead generation	49.2	57.3
Recruiting	0.0	6.1
Knowledge graphs	28.8	66.7
LLM guardrails	68.0	84.6
Moderation	51.6	59.2
Code linting	29.1	72.3
Search & retrieval	80.9	84.7
Science	21.2	21.7
Advertising	16.4	24.9
Gaming	5.1	19.3
Demand forecasting	0.0	0.0
Competence per request type, open / sealed
Choice · open	79.0	81.2
Choice · sealed	75.8	78.4
Noul · open	54.5	47.3
Noul · sealed	46.1	50.8
Score · open	63.3	63.7
Score · sealed	63.0	63.5
Competence per tier — open set
Easy	93.9	91.1
Standard	63.2	55.7
Judge	67.7	58.9
Hard	65.6	73.3
Competence per tier — sealed set
Easy	78.4	76.0
Standard	68.7	73.5
Judge	66.9	72.2
Hard	58.9	60.0

Published values

Measure	Jev 1.13.0 (TypeSafe AI)	Kev 27B (Kev 1.0, Qwen3.8-27B)
Capability Score	77.1	78.9
Rank (open-weights board)	Reference, not ranked	Outside caps
Composite (secondary)	71.4	5.8
intelligence	63.6	64.2
calibration	90.6	93.7
speed	91.2	82.8
cost	54.7	18.3
USD per 1,000 decisions	$0.032 per 1,000 decisions	$0.529 per 1,000 decisions
p50 latency (seconds)	0.2	0.187 measured on-GPU, no network · 0.52 est. incl. network (2x + 150 ms)
Method	v1.7 · 10 s rule	v1.7 · 10 s rule
p95 (measured) · decisions over 10 s	p95 0.311 s (measured) · 0 of 1,500 over 10 s	p95 0.422 s (measured) · 0 of 1,500 over 10 s
Before the 10 s rule (v1.6)	v1.6.43: A 71.49 · #18	v1.6.43: A 5.77 · #184
Last measured	2026-10-05	2026-10-06

* Self-hosted rows: the first value is the p50 we measured on our own hardware over loopback (on-GPU, or on-CPU where marked, no network). It is not directly comparable with API latency, which we time end to end from our measuring host, network included. “est.” is the est. incl. network (2x + 150 ms) that the ranking and the latency cap use for every self-hosted row. Model authors can ask us to time a hosted endpoint instead (on request).

Jev 1.13.0 (TypeSafe AI)

proprietary API

Published source

Measured on: the operator's hosted API
Cost basis (not published): TypeSafe list tariff USD 0.042 per 1M input tokens, output free; measured on the v1.6.1 common cost basis (all items except those outside the Jev reference input range) from this run's token usage
Latency adjustment: none (API)

Kev 27B (Kev 1.0, Qwen3.8-27B)

apache-2.0

Published source

Measured on: evaluator-owned Lium GPU pod, 1x NVIDIA H100 80GB, the author's own server in its own pinned environment, offline (Hub offline mode, all credentials unset), driven over loopback only by the JevBench client with its loopback guard; label-free inputs; pod destroyed afterwards; HF Jev Decision Index intake, 6-7 Oct 2026
Cost basis (estimated): ESTIMATE (base-model reference; self-hosted open weights, no public tariff): frozen BASE_REFERENCES Qwen/Qwen3.8-27B market price, the pair the published autojev-27b, eikos-27b and open-jev-zefan-27b-v1.1 rows use, USD 0.42 per 1M input and USD 3.0 per 1M output x this row's own measured tokens. Estimated, not charged
Latency adjustment: x2 + 0.15 s (assumption, not measured)

Using these models through an API

Decision Models offers a Jev-compatible API; its comparison page lists hosted options and prices, checked on the date shown there.

Kev model explained (Decision Models)

Decision Models is run by the same company as Benchmark Heaven. This link is the same on every comparison page and never affects scores or ranks.

Frequently asked questions

What does JevBench show for Jev and Kev?: Jev 1.13.0 has Capability 77.1 and is the unranked reference (the open-weights board ranks 171 open-weights systems; hosted API offerings are ranked on the API leaderboard). Kev 27B (Kev 1.0, Qwen3.8-27B) has Capability 78.9. Outside the Capability caps in v1.7.23. Historical scores use their original method and are not ranked against the current release.
Is there a time limit per decision?: Yes, from JevBench v1.7.0 (method v1.7): a decision that takes longer than 10 seconds (measured time) counts as a wrong answer and as zero calibration for that item. Each row shows its p95 and how many decisions were over the limit; the v1.6 values stay visible.
How does Capability differ from Composite?: Capability is the mean of Intelligence and Calibration; headline ranks require both official cost and median-latency caps. Composite additionally scores Speed and Cost and is secondary.
Can I compare the prices as actual bills?: Jev 1.13.0 (TypeSafe AI): not published, $0.032 per 1,000 decisions. Kev 27B (Kev 1.0, Qwen3.8-27B): estimated, $0.529 per 1,000 decisions. Estimates and self-reported vendor prices are not measured charges.
Is Kev open source?: The published licence note for Kev 27B (Kev 1.0, Qwen3.8-27B) is apache-2.0. Jev 1.13.0 is listed as proprietary API. Check the linked sources for terms.