Jev Classifies 1,500 Real Inbox Emails in Real Time
A live test of TypeSafe's new classifier model Jev, run against the creator's own 1,500-email inbox export to see if it can actually replace manual triage.
A model built to do nothing but classify, instead of generate text, can sort a real inbox at 38 requests per second and a fraction of a cent per email, which is fast and cheap enough to run as a background triage layer rather than an occasional AI query.
Who This Is For
Read if. Skip if.
READ IF YOU ARE…
You build tools that need to triage or route high volumes of text (email, tickets, leads) and are paying too much in latency or tokens to do it with a general chat model.
You're evaluating whether a narrow, rules-based classifier model is a better fit than GPT-style models for a production pipeline.
You want a real, unscripted before/after: raw claims from a launch post tested against a real 1,500-email inbox, not a synthetic benchmark.
SKIP IF…
You're looking for a general review of chat-style AI assistants — Jev doesn't generate text and isn't a chatbot.
You want deep technical documentation on how Jev's rule format works — the video only shows a UI dashboard, not the underlying API or JSON schema.
TL;DR
The full version, fast.
TypeSafe launched Jev, a model that only classifies text against rules instead of generating it, claiming 20-200x the speed and 40-400x lower cost than standard AI models. The creator tests that claim on a real 1,500-email export from his own inbox, scoring each message for category, priority, spam, and whether it needs a reply. A 100-email batch runs at roughly 200ms average latency and 240ms P95, correctly flagging real security and account-violation emails as high priority and reply-needed. Scaling to a 1,000-email batch holds the same per-email speed across 1.1 million tokens, and the entire run costs about 5 cents. The takeaway is that narrow classification is a distinct AI workload from text generation, and treating it that way unlocks speed and cost that general models can't match for high-volume sorting tasks.
Free for members
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
TypeSafe is introduced as a new company built around a classification-only model.
00:11 – 01:01
02 · What Jev actually is
Jev doesn't generate text, it only classifies input against rules, with headline claims of 20-200x speed and 40-400x cost savings over standard models.
01:01 – 02:14
03 · First live test: 100 real emails
The creator loads 1,500 of his own exported emails and runs a 100-email batch across 8 workers, defining four classification fields: category, priority, spam, and reply-needed.
02:14 – 03:06
04 · Proof in the results, then scaling up
The high-priority and reply-needed flags correctly surface real security and account-violation emails, then the creator scales the test to a 1,000-email batch that holds the same per-email speed across 1.1 million tokens.
03:06 – 04:06
05 · The cost reveal
The full run costs about 5 cents, and the creator closes on what a model built for classification rather than generation unlocks.
Atomic Insights
Lines worth screenshotting.
A model built only to classify text against rules, instead of generating text, can run 20-200x faster and 40-400x cheaper than a standard general-purpose AI model.
A 100-email classification batch averaged 200ms per email with a 240ms P95, processing 38 emails per second on 8 parallel workers.
Four classification fields (category, priority, spam, reply-needed) are enough to cover the two questions that actually matter for email: is this spam, and does it need a reply.
Scaling from 100 to 1,000 emails held the same ~200ms-per-email latency across 1.1 million tokens processed, showing the speed doesn't degrade at higher volume.
A full run of roughly 1,100 real emails cost about 5 cents in API spend, cheap enough to run as a standing background process rather than an occasional query.
Splitting 'does this need a reply' out as its own classification field caught real emails a keyword filter would likely miss, including a 91%-confidence account-violation notice.
Treating classification as a distinct workload from generation is the core bet: a model that never writes a sentence can still be the more useful AI for a sorting problem.
Takeaway
Classification is a different AI workload than generation, and treating it that way is cheap.
WHAT TO LEARN
A model that only sorts text against rules instead of writing it can run fast and cheap enough to sit in the background of a real product, not just answer occasional queries.
Splitting 'what type of task is this' out from 'generate a response to it' lets a narrow classifier model run 20-200x faster than a general-purpose one, per this creator's test.
Real-world latency held at roughly 200ms average and 240ms P95 across 100 parallel-processed emails, a workable speed for near-real-time inbox sorting.
Throughput didn't degrade going from 100 to 1,000 emails: 1.1 million tokens processed at the same ~200ms-per-email pace, which is the number that actually matters for a production workload.
Reducing a messy problem like 'triage my inbox' to four scored fields (category, priority, spam, reply-needed) made a fuzzy task testable and fast to verify by eye.
The all-in cost for classifying roughly 1,100 real emails came out to about 5 cents, cheap enough to run continuously rather than ration as an occasional AI call.
Glossary
Terms worth knowing.
Classifier model
An AI model trained to sort input into predefined categories or scores, rather than generate new text. It answers 'which bucket does this belong in,' not 'what should I say next.'
P95 latency
The response time that 95% of requests finish faster than. A common way to measure worst-case speed instead of just the average.
Worker
A parallel process handling one request at a time. Running 8 workers means 8 emails can be classified simultaneously instead of one after another.
Resources
Things they pointed at.
00:00toolTypeSafe
04:06toolJev
Quotables
Lines you could clip.
04:06
“Jev gives all AI properties of code.”
tight closing tagline that reframes the whole demo in one line→ TikTok hook↗ Tweet quote
03:17
“Look at this. I've used 5 cents. That's it. This is insane.”
concrete, surprising cost number lands as proof→ IG reel cold open↗ Tweet quote
00:11
“It's not like a standard AI model where it generates text or anything like that. It just does essentially classification.”
clean one-line definition of the product category→ newsletter pull-quote↗ Tweet quote
The Script
Word for word.
Read-along
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
17px
So the co -founder of ChatGPT has created a new company and it is called TypeSafe. What it is, is a classifier AI model. And...
It basically, it's not like a standard AI model where it generates text or anything like that. It just does essentially classification. So you can feed in these sort of like Jason rules and everything like that to be like, okay, based on this input, evaluate this set of rules type of thing, like production capability down, uh, credible churn risk.
I don't know all of that stuff, but apparently according to them, it's 20 to 200 times faster and 40 to 400 times. Cheaper with output tokens free, which is absolutely insane. There's a lot of cool stuff in the post, but I wanted to play around with it with what I think might be one of the coolest implementations of this, which is email classification.
So right here, I've got 1500 of my own emails that I've exported from my email. And we're going to run this classification model because I got access to it and see how well it runs the classification on it. We're going to do a batch of a hundred emails just to start out with eight workers and we'll see how long it takes to do it.
So let's start. Boom, a hundred emails done. It doesn't tell me how long it took.
Average was 200 milliseconds, 200 milliseconds per. Email P 95 was 240 milliseconds and it did 38 per second, which is amazing. Okay.
So what I had it do is I gave it four different things to like evaluate for category, priority, spam, or reply. These are really important because these are the core things that you actually care about in email. Do you need to reply to it?
Or is it spam? Those are basically like the two that it could kind of be gone down to. So priority high, uh, safety identifier in your open AI account.
I would count that as high. Okay. Domain revocation account.
That's high. SES custom mail. And then let's look at the ones where it ranked a high reply.
So we had a 51%. Yep. Looks like someone replying to other ones.
Okay. We got a 16%, 11%. Yeah.
So it would have properly, oh, 91 % account violation. Yep, there we go. So that's another email that like needs reply.
This did an amazing job because it ran super fast. Let's get a little dirty, shall we? Let's do a thousand emails.
We have eight workers still. Let's start and let's just watch it cook. Look at that.
It is flying. It is absolutely flying. We've got 1 .1 million tokens in so far and it is just, it is sticking around that 200 milliseconds.
per email that's being classified. And if we go down, we can just see it all. Man, this is incredible.
This is so fast. I'm not used to this type of speed of AI at all because every other like AI, it's like, okay, well, we've got reasoning and we've got this and that, the other. I think this is more than enough for standard email classification.
This is amazing. I love this. I'm gonna try to think up some more ideas.
to to do this with i'm blown away and i'm gonna see if i can implement this into my own like super local project that i was doing because it's hella cheap too it's so incredibly cheap Look at this. I've used 5 cents.
That's it. This is insane. Oh, wait, this isn't even me.
Wait, this is a shared account. What the heck? Because I see Luke Experiments on Playground.
That's the other people on the team. We only have a balance of $5 down here, which just shows how cheap this model is. Why don't we just go ahead and finish out the run?
Just why not, you know, and just look at that average latency. That is insane. That is full trip request, if I recall correctly.
That is full email submitted, email returned. And if you parallelize this even more, oh my gosh, this is insane. This is super cool.
There's so many different use cases here that I can't even think of, but this is going to be a super cool model called Jev. Jev gives all AI properties of code. This is cool.
The Hook
The bait, then the rug-pull.
A launch post claims a new AI model is 20 to 200 times faster and 40 to 400 times cheaper than standard models. Instead of taking that on faith, the creator points it at 1,500 of his own real emails and watches what happens.
Frameworks
Named ideas worth stealing.
01:28list
Four-field email classification schema
category
priority
spam
reply-needed
The creator's own reduction of email triage down to four fields Jev scores per message, arguing the two that matter most are spam and reply-needed.
Steal forany inbox, support-ticket, or lead-routing tool that needs fast automated triage
Add Modern Creator as a preferred source and Google shows you more of our breakdowns in Search, Top Stories, and AI Overviews. It only changes what you see, and you can undo it in your Google settings anytime.
Add to Preferred SourcesOpens your Google source preferences with us pre-loaded. Tick the box and you're done.
A hands-on tour of TypeSafe's new decision-only model, remixing five community projects from X into a Chrome extension that scores YouTube videos, a tool that turns any website section into a rebuild prompt, and a voice-controlled game.
One creator benchmarks TypeSafe's new model against GPT-6 Astra across five real business tasks, and it wins on speed and price every time, as long as you never ask it to actually talk.