Jev case: Introducing the Papers with Code MCP server!
Used Claude Code with a papers search tool to research Jev's architecture and describe it as a schema-conditioned encoder with parallel label heads.
The original post
Introducing the Papers with Code MCP server!
To celebrate its release, I've asked Claude Code to research the architecture of Jev by @typesafeai using the `search_papers` tool.
Here's what it came up with:
"If Jev is architecturally anything public, it's a large schema-conditioned bidirectional encoder with parallel label-query heads (GLiNER/ML-Decoder shape) trained with a proper-scoring-rule RL objective (RLCR shape), scaled far past the ~150M-param range those papers operate in — "neither small nor an LLM" fits that. The 40–200× speedup is consistent with removing autoregression, not with any exotic mechanism."
Engagement when collected
Numbers are a snapshot taken from X when the case was added to the library (schema v1, collected 2026-09-19); they will not match today.
Where this case fits
Filed under agents & workflows, coding & developer tools, classification & data extraction. In the pattern Jev is built for, the model answers a bounded question per step — and ordinary code acts on the answer, because the answer is already a value rather than a paragraph. Other posts in the same family are on the agents & workflows page.
Related Jev cases
found the perfect use case for @typesafeai Jev: instant
Agents
Breaking: Browser Use + Jev = Ultrafast Findings flights
AgentsBrowser agents
The gains aren’t free: Jev can't generate text Comparing
Dev toolsClassification
Jev was adopted faster than any other model in AI Gateway
Classification
Keep browsing: all 1173 Jev cases · more from @NielsRogge · builders · what Jev is
Last updated: 2026-09-22 · sources & corrections · every card links to its author's original post