Jev use cases
People use Jev for the decisions a system makes over and over: sort this, route that, score this draft, pick the next click, allow or block. This page groups 457 catalogued builds by the job Jev does in them, with the figures their authors published.
Updated 22 Sept 2026 · by Made with Jev
In short
- 457 builds are catalogued here, 223 of them with a published figure. They fall into 8 jobs.
- The two that repeat most: classifying a corpus nobody would pay a large model to read, and choosing the next action inside an agent.
- Median published cost: $0.000068 per decision, across 15 runs where the author gave both a volume and a total.
- Median published latency: 300 ms, across 19 builds. 16 of them are at or under half a second.
The eight jobs, at a glance
Every build below does one of eight things. The taxonomy this site files them under — agents, games, triage, trading — says what the project is. This list says what Jev is for in it, which is the thing worth copying.
| The job | A published result |
|---|---|
| Sort a pile that is too big to read | 100,000 posts, 20.4 s, $0.67 |
| Triage a queue into buckets | 500 emails, 3.5 cents |
| Choose an agent's next action | a flight search in ~7 s |
| Decide inside a frame | Tetris at ~0.3 s a move |
| Score something before it ships | 61 questions in ~1 s |
| Block the risky step | one Noul call per action |
| Shrink what the LLM reads | compaction with no summary |
| Judge every row where the data already is | 129 rows in ~1 s, in SQL |
Sort a pile that is too big to read
One question, or twenty, asked of every item in a corpus. This is where the cost per decision decides whether the job happens at all: the same pass on a large model is usually not worth running.
Movez
@0xMovez
I just built a Jev X Viral Post Analyser. 100,000 viral X posts. 20.4 seconds. $0.67. Claude Opus 5, same corpus, same clock, got through 214 posts and spent $0.98. per post that is ~680x cheaper the full Opus pass would have run $458. viral analysis is the perfect Jev job. • it is not writing, it is 14 yes/no calls per post: > does the hook open a loop, > is there a number in the first line, > is the proof real or claimed. classification, not prose. • what it found: 1,220 posts broke into the top 1%. baseline 1.22%. > superlative claim - 2.34% viral. 1.92x baseline > contrarian take - 1.59%. 1.31x > launch / tool drop - 1.46%. 1.19x and numbered lists, the thing everyone writes: 0.55%. below baseline. the most used hook is the least viral one. full stop. • what you are watching: left is the post under analysis, right is Jev answering 14 typed questions about it, each with a confidence score. the run stops at 20.4s because that is when Jev finished all 100k. pulled the corpus through a few X APIs, one parallel pass into Jev. should I drop it to public? Read my latest article on Jev Engineering below and turn your ideas into reality.
Sabrina
@sabrinaesaquino
Jev is now live on the Venice API. Watch it classify 24,000 Hacker News posts into 12 categories in about 2 minutes
Ian Nuttall
@iannuttall
I gave Jev 3,282 of my X posts across 100M views and asked it to find what actually works for growth. 4,252,330 tokens $0.1282 for the full 8m 34s run! Each post got 8 questions about the topic, hook, tone, whether it teaches something, etc. How-to posts got 150 median likes vs the average median of 44. AI and coding was a 1.9x multiplier topic compared and SEO, despite recent posts, was right at base median 1.0x - surprisingly. The recommended topic + angle + voice formula was: AI coding + teach something + provocative
Hassan
@nutlope
I used Jev to classify 1,018 AI research papers. The result: $0.08 total cost and 256ms median end-to-end latency per paper. The pipeline was: 1. Summarize each paper with DeepSeek V4 Flash 2. Send the title + summary + 24 possible topics to Jev 3. Use Jev to classify each paper 4. Visualize everything on http://1kpapers.com The summaries cost $3.99 on @togethercompute. The classifications cost $0.08 on @typesafeai. So for just over $4 of inference, I ended up with a pretty useful way to explore the top AI research papers from the past year. I think this is where things are heading: different models for different parts of the workflow, instead of using one model for everything. I’m running evals on the Jev classifications before replacing the current ones, but the site is already live: http://1kpapers.com
Dan Shipper
@danshipper
we almost never test new foundation models but we've been testing this for ~a week @every and it's pretty wild. the kind of things that will be obviously indispensible in 6-12 months it doesn't produce words as output, it produces probabilities. so it can efficiently act as a judge in cases where you'd need a Fable-level model—but in our testing was 25x faster and 600x lower priced excellent vibe check by @hammer_mt on @every: https://every.to/also-true-for-humans/mini-vibe-check-typesafe-s-jev-judged-everything-i-ve-written-in-0-7-seconds?utm_cta_source=home_main_a_3
ArticleContent and growth
PickEvery’s editorial vibe check
- Judgments
- 1,709
- Total cost
- <$0.01
- Median per passage
- 0.35 s
Fayaz Ahmed
@fayazara
Made myself a little image classifier with OCR + Jev It was able to categorise ~900 images in 40 seconds Pretty cool
Trinay Hari
@hari_trinay
Built a construction plan-set classifier with Jev. Proq turns civil and building plan sets into bills of materials using an LLM pipeline we built on GPT-4.1. Jev classified an entire 26-sheet plan set in 2.9 seconds for $0.0052. It matched GPT-4.1 and GPT-6 Astra on 100% of sheet-level classifications while running 17–21x cheaper and 5x faster than our production pipeline.
Triage a queue into buckets
Email, tickets, pull requests and leads sorted by what each one needs next. The confidence score is the point: the sure ones are routed automatically and the rest go to a person or to a larger model.
Riley Brown
@rileybrown
Yeah Jev by @typesafeai is very cool. It classified 500 emails in seconds. And it costed 3.5 cents.
Hassan
@nutlope
Jev + Kimi K3 for fraud detection! TLDR: Jev classified 100 emails in 1.42 seconds, then I routed the uncertain cases to Kimi K3. The full pipeline got 96/100 correct for only ~$0.07. Video is not sped up, check out the live run! Here was my process: I gave Jev 100 emails to classify (a mix of 50 legit & 50 fraudelent emails). It classified all of them in 1.42 seconds. An underrated feature about Jev is it will give you the confidence score for a classification, so I routed any prediction under 95% confidence to Kimi K3 to be fully sure. 31 emails fell below that threshold. After routing those to Kimi K3, the combined pipeline reached 96% accuracy. The full run took 16 seconds & ~$0.07 in inference costs: - $0.068 from Kimi K3 on @togethercompute - $0.003 (1/3 of a cent) from Jev on @typesafeai. I think this is a really interesting pattern: use a fast specialized model like Jev for the narrow task, then route the uncertain cases to a larger LLM. I feel like this kind of approach could be a game changer for use cases like fraud or anything realtime. You can use the speed & low cost of Jev while having a larger LLM as a fallback to ensure high accuracy.
XTriage and routing
PickFraud detection with Jev and Kimi K3
- Emails
- 100 in 1.42 s
- Correct
- 96/100
- Cost
- ~$0.07
vogel
@ryanvogel
this model is actually insane at email classification i tested it on 1500 of my own emails to see how well it works and I am blown away
Duncan
@ephraimduncan
Built a model router with Jev by @typesafeai. Jev decides what model fits your request best and the request is sent to that model.
XTriage and routing
A model router on Jev
Raihan Khan
@raihankhan_rk
I got access to Jev by @typesafeai today morning and I built a cool use case for it Introducing DiffJury - simply paste any public PR link and Jev tells you immediately if it's safe to merge or does it require review ✅ 🔗 Feel free to try it out here - http://diffjury.up.railway.app Imagine Jev being able to tell you if you should merge a PR with grounded context of your codebase. that's what we're building at @graphify 👀 It's fascinating how insanely fast Jev is... the model architecture in itself is quite interesting and this has opened up a plethora of new use cases and I'm sure the internet will pick up on it sooner than anyone'd expect
Live siteTriage and routing
DiffJury
Choose an agent's next action
The step decision inside a browser, desktop or mobile agent: given this page, which element do I act on. It is the most common Jev build on this site, and the one where the latency shows up as a stopwatch figure.
Gregor Zunic
@gregpr07
Breaking: Browser Use + Jev = Ultrafast ⚡ Findings flights took 7s and cost only $0.0039 🤯 > new action space every step > DOM state space > small LLM fallback to type (this video is at 1x speed btw) Built a tiny open source browser agent. try it below ↓

GitHubAgents and browsers
Pickjev-ultrafast
Browser Use’s browser agent, with Jev choosing each next step.
Browser Use
~2.9k
GitHubAgents and browsers
Mobile Jev
A mobile agent on a real Android phone, with Jev making each decision.
Droidrun
9 actions in ~21 s
GitHubAgents and browsers
typesafe-computer-use
Computer use on macOS, with one Jev decision per step.
Andrew Levin
~$0.0002Milind S
@milindlabs
Okay so Jev can actually do computer use really well Without any screenshots, or LLMs and no Pixels leave my mac I dont even read the Dom elements A local CoreML model segments every button and UI element on screen. On-device OCR reads the labels. That text is all Jev gets. It returns a probability across those elements and tells me the best one to click. Then it clicks, re-runs detection, and decides again. In a loop until the goal is done. ~90ms per decision. Faster than any LLM computer use I've tried. Blazing fast computer use, without any latency @typesafeai is building something really interesting
XAgents and browsers
Computer use without screenshots

GitHubAgents and browsers
jev-mcp-dispatcher
Plain-language MCP tool calls with no LLM at all, only Jev.
abhishekashokvkumar
CJ (Coding Garden)
@CodingGarden
I built a chat bot with jev, no LLM at all! Responses are instant, no hallucinations. I hooked it up to web search, wikipedia, weather, todoist and home assistant. Jev decides what tool to call and what args to use based on the prompt. Instant answers cite sources as well!
XAgents and browsers
A chat bot with no LLM
Decide inside a frame
Games, control loops and price feeds, where an answer that arrives late is the same as no answer. A large model cannot hold this loop; these builds run it at 2.5 to 10 decisions a second.
Diogo Almeida
@CompleteSkeptic
We love how this doomo doomonstrates real-time intelligence and what can be doone with code + AI! ~10 calls/sec = ~$7/hour
Alan Daitch
@AlanDaitch
Puse a Jev, la nueva IA de @typesafeai, a jugar al Tetris en modo súper difícil. Decidió cada jugada en unos 0,3 segundos. Acomodó 357 piezas e hizo 134 líneas en solo 2 minutos. Increíble.
paulwei
@coolish
昨天出的 typesafe.ai Jev 模型 适合高频决策,那岂不又是适合打游戏? 之前用 GPT-6 Astra 代打杀戮尖塔2 能力强但速度慢。 我刚实测用 Jev 打,行动思考只需 0.7秒, 画面我都没看清它就操作完了。 这超人类游戏速度, 着实又让我震惊瘫坐了😅 语言很难描述这感觉,看视频⬇️
Jarrod Watts
@jarrodwatts
I built a trading bot with Jev! Jev decides if it should "buy" or "sell", given the price feed of an asset pair, and executes real trades. It uses Monad to place the orders on Kuru's on-chain order book in every 300ms block. Demo link → jev-trader.vercel.app
Chandramouly Kandachar
@chandamamz
@typesafeai's Jev controls the 2 hands and each finger to play the piano in real-time. Jev only "sees" what we see and plays this from the "note waterfall". It uses @browser_use's jev-ultrafast and some decision scheduling to make this happen in real-time. Sound on 🔈🔉🔊
XGames and real time
Both hands on a piano, in real time
ラプター | ロボコン ビジコン
@Raptor_zip
型付き意思決定AIモデル「Jev」で双腕ロボを動かした結果まとめてみた🦾 3層制御のうち意思決定(2層)をJevに任せ、IKや物理計算はコード側に分離する構造を作りました。500msの応答と0.5円/試行で早くて激安。
XRobotics and devices
A dual-arm robot with Jev in the middle layer
- Response
- ~500 ms
- Cost per attempt
- ~¥0.5

GitHubRobotics and devices
jev-drone
A simulated drone that asks Jev for a judgment 2.5 times a second.
Roman Slack
2.5 HzScore something before it ships
A draft, an ad, a lead or a page gets graded against a rubric while its author waits. Many questions in one call cost about the same as one, so the rubric can be long.
Rob Hallam
@robj3d3
Jev + SuperX = virality solved ✅ Every post gets 61 questions in ~1s for $0.0004 🤯 > fitted on 9,481 real posts from 207 creators > picks the viral post 2 in 3 times > never rewards reply bait So: write, score, rewrite, stop when it peaks. Free, no signup. try it below ↓
Romàn
@romanbuildsaas
JEV is INSANE. We gave it 700 high-intent leads and personalised outreach messages. In 40 seconds, it predicted how each message would perform, assigned a confidence score and detected lead-message mismatches. All for just $0.09. JEV can also score leads, analyse buying signals, match each prospect with the best message and identify the campaigns most likely to perform based on data. Coming soon to @GojiberryAI+ MCP. Comment “JEV” for early access.
Matthew Berman
@TheMattBerman
jev is INSANE. in 40 seconds it broke down 724 live ads from 37 brands. every hook. every format. offer. cta. awareness stage. landing page mismatch. used 9 cents of tokens. (will be avail in @stealads + mcp)
Jon Kraayenbrink
@kraayenJon
jev is INSANE. in 243 ms it checked a website for 35 tells of ai slop. purple gradients. emoji headers. "seamlessly". fake testimonials. bento grids. the works. used $0.00015 of tokens. paste any url, get a slop score. free: madewithjev.com/free-tools/ai-…
Niaz Morshed
@niazmorshed_
built `jev-review` @typesafeai it's an experimental, local-first MCP plugin that gives coding agents a score quality feedback loop across different metrics. agents call jev while they work, get scored, make improvements, and repeat the loop try below 👇
XTools and apps
jev-review
Block the risky step
A gate in front of an action that cannot be undone: a tool call, a merge, an install, a post. Jev answers one Noul question and code decides what the threshold is.
😎Nick 常胜
@isNickMa
Tested TypeSafe’s Jev (no-text, probability-only model) as an AI agent safety monitor. Checking each action first worked well caught most attacks with almost no false blocks, and much faster than Gemini.
XAgents and browsers
Jev as an agent safety monitor
7Stars
MetalBear

Marcel Pociot 🧪
@marcelpociot
I built a browser extension with Jev @typesafeai that can hide/collapse posts on X based on natural language. It's so fast that it's not noticeable and insanely cheap...this must be the future of "ad blockers" and content firewalls.
XTools and apps
Hide posts on X in plain language
Ian Nuttall
@iannuttall
Pro tip: You can use Jev to remove annoying reply guy comments that X seems to always miss. Takes 5 minutes in Astra with the docs and an API key.
XContent and growth
A filter for reply-guy comments
Shrink what the LLM reads
Jev scores each piece of a long context and drops what no longer matters, in place of a summarization prompt. It is the fastest-spreading pattern in the directory, because every coding agent has the problem.
tamara
@tamarajtran
found the perfect use case for @typesafeai Jev: instant compaction in 2026, why is compaction still a summarization prompt? Jev can make it instant by scoring every tool call and dropping what’s irrelevant
XTools and apps
PickInstant compaction for Claude


GitHubAgents and browsers
codex-context-diet
A Codex plugin where Jev trims bulky tool results.
Konstantinos Botonakis

GitHubAgents and browsers
pi-jev-compaction
Automatic context clearing for Pi, without losing the conversation.
Nour
Judge every row where the data already is
A Jev call written as a SQL function, so a plain-language condition runs in the query rather than in a script beside it. No index, no embeddings and no pipeline.
Zachi
@iam_zachi
I think I just cooked something 🔥 jev(): a PostgreSQL extension that searches your whole database in natural language. No index, no embeddings, just one function. WHERE jev(people, 'could work from home') or WHERE jev(people, 'name sounds european') 129 rows judged in ~1s for $0.0009. Second run: 6ms from cache.

GitHubResearch and data
duckdb-jev
Ask a question about every row in SQL, and get a real SQL type back.
Colliber
By the work you do, rather than the decision
The groups above are decisions. If you came here as a marketer, an SEO or a media buyer, the same builds are grouped again by the job title that cares about them, with the published costs restated in the terms that function uses.
How to tell whether your job is one of these
Three tests, in the order they rule things out. First, can the answer be written down as a fixed set of options before the call? Jev returns a choice, a level or a probability, never a sentence, so a job that needs prose is not one of these. Second, does the same decision happen many times, or under a deadline? One decision a day is not worth moving. Third, is a wrong answer recoverable, or does a confidence threshold make it recoverable? Every guard build on this page works by acting on the sure answers and escalating the rest.
If all three hold, the pattern the builds here share has a name: Jev Engineering. An LLM writes, Jev decides, code acts.
The same builds, by what they are
The directory's own use-case pages hold the full lists, including the builds this page did not have room for.
- Agents and browsers81
- Games and real time49
- Triage and routing27
- Trading and markets10
- Content and growth59
- Research and data74
- Robotics and devices14
- Tools and apps143
For the counts behind all of it — builds per day, cost per decision, latency, GitHub stars — see the Jev Build Report. For what the model is and what a call looks like, start at what is Jev, and for the choice between Jev and a large model on one of these jobs, see Jev vs an LLM.
Built something that is not here? Submit it, or read TypeSafe’s launch thread for the demos they shipped on day one.
Common questions
- What is Jev actually used for?
- Eight jobs cover almost every build in this directory: classifying a large corpus, triaging a queue, choosing an agent's next action, deciding inside a real-time loop, scoring something against a rubric, blocking a risky step, pruning an LLM's context, and judging rows inside a database query.
- What is the most common Jev use case?
- Picking the next action in an agent. Browser, desktop and mobile agents send the page or screen as text and ask Jev which element to act on, which removes a large-model call from every step of the loop.
- Is Jev worth it for a small job?
- Rarely on cost alone. The gain shows up when the same decision repeats: a median published run costs about $0.000068 per decision, so the saving is per item and only adds up over thousands of them, or when the decision has to arrive in well under a second.
- Can Jev replace my LLM?
- Not for anything that has to be written. It replaces the classify, route, score and approve calls inside a system an LLM still writes for. Most builds here keep both and hand Jev only the closed decisions.
- Where do these numbers come from?
- Every figure is the one the build's author published, and every card links to the post or repository it came from. Nothing on this page is measured by Made with Jev.
Made with Jev is independent and not affiliated with TypeSafe AI. Every figure on this page is the one its author published, linked to where it can be checked.