Skip to content

Article

Jev vs LLM-as-a-Judge in Opik

Comet's Opik team ran Jev beside a gpt-4o-mini judge over 1,000 production turns: 89.7% agreement, 3.5x cheaper and 3.8x faster at the median, with the 103 disagreements concentrated at mid probabilities.
Format
Article
Reading time
3 min
Published by
Community
Author
Aswin Thiyagarajan (Comet)
Last verified
Oct 2026

Highlights

  • On 1,000 turns: gpt-4o-mini cost $0.0993 per 1,000 traces at 958 ms p50, and Jev cost $0.0285 at 253 ms p50, each agreeing with the other 89.7% of the time.
  • Jev sends 1.5x more input tokens but is 3.5x cheaper and 3.8x faster, because the Decisions API encodes question structure alongside the text.
  • 64.1% of the 103 disagreements fall between 0.3 and 0.7 on Jev's probability, against 16.7% of agreements; agreement is 100% below 0.2 and 95.6% above 0.8.
  • Opik ships a native integration because the typesafe-sdk is not OpenAI-compatible: track_typesafe(TypeSafeClient()) traces every system_one call as a span.
  • As an online rule Jev sits under the OpenRouter provider, takes Boolean scores only, and the span records the served version, typesafe/jev-1.13-20260917.

Watch out

Vendor-authored by Comet, whose Opik platform is the subject, and the comparison covers one narrow Boolean judging task on one team's traffic: 89.7% agreement measures consistency with the old judge, not correctness. Opik is open-source; the online judge needs a Jev model reachable under the workspace's OpenRouter key.

Questions about this entry

Short answers drawn from the linked project or page.

Reactions & coverage

Posts, threads, and videos about this entry from around the web.

X: Microsoft-Decision-1 against Jev on a private eval

X: Vals AI's independent evaluation of Jev

X: An eval suite for System One models

X: Jev and Laya play chess instead of benchmarks

From the Jev guides

Original write-ups on what this entry is for.

From the Jev AI model community

Posts from builders shipping with Jev right now.

Follow @typesafeai