Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

Another crazy TypeSafe AI Jev example: Predictive spreadsheets Spreadsheets recalculate numbers, not meaning. Jev reads intent. Type "Urgency" at the top of a column and, as you type, it figures out you want each row rated from "no follow-up needed" to "urgent" in ~100 ms.

nader dabit

195,692 subscribers

277,424 görüntüleme • 1 ay önce •via X (Twitter)

Bilim & Teknoloji

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Also have been playing with TypeSafe AI Jev, insane! So many immediate use cases and new apps are possible. What a time to be a builder! Sharing some experiments here starting with: Keystroke oracle / predictive launcher: Your launcher ranks by aliases, fuzzy match, and habit. Jev reads intent: type "the pdf I just downloaded" and the newest PDF is already the top hit with a full confidence on every keystroke, in ~100 ms

Also have been playing with TypeSafe AI Jev, insane! So many immediate use cases and new apps are possible. What a time to be a builder! Sharing some experiments here starting with: Keystroke oracle / predictive launcher: Your launcher ranks by aliases, fuzzy match, and habit. Jev reads intent: type "the pdf I just downloaded" and the newest PDF is already the top hit with a full confidence on every keystroke, in ~100 ms

nader dabit

434,529 görüntüleme • 1 ay önce

Built a model router with Jev by TypeSafe AI. Jev decides what model fits your request best and the request is sent to that model.

Built a model router with Jev by TypeSafe AI. Jev decides what model fits your request best and the request is sent to that model.

Duncan

120,065 görüntüleme • 1 ay önce

This is absolutely f*cking insane. you can put a $0.042-per-million-token model in front of Claude and let it decide what Claude ever has to see. that's Jev signal routing, and the trick is stupidly simple: Jev takes the first look at everything. Claude only gets the hard cases. instead of: data -> Claude -> tokens burnt $ it's: data -> Jev -> only the unsure ones -> Claude and here's the part people miss. every Jev answer comes with a probability. that's your router: -> Jev is sure? its answer is final -> Jev hesitates? the case goes up to Claude set the cutoff once, by testing on your own data, not by guessing. 3 repos that already do the routing for you: -> duckdb-jev: route your data. Jev labels every row straight from SQL, up to 1,000 calls in one request -> quicksilver: route your files. Jev checks all 187 files in parallel and Claude gets the 4 that matter. ~2.4k tokens instead of ~26k -> jev-router: route your models. before every message Jev decides simple or hard and sends it to the fast model or the strong one. works with your normal Claude login where this pays off right away: -> support tickets -> your inbox -> lead lists -> messy spreadsheets -> comment moderation on a public benchmark Jev labeled 1,000 rows for $0.015. Claude charged $0.80 for the same job. faster. cheaper. way fewer tokens burned. Jev sorts the mail so the genius only opens what matters. Claude thinks. Jev routes. code does the job.

This is absolutely f*cking insane. you can put a $0.042-per-million-token model in front of Claude and let it decide what Claude ever has to see. that's Jev signal routing, and the trick is stupidly simple: Jev takes the first look at everything. Claude only gets the hard cases. instead of: data -> Claude -> tokens burnt $ it's: data -> Jev -> only the unsure ones -> Claude and here's the part people miss. every Jev answer comes with a probability. that's your router: -> Jev is sure? its answer is final -> Jev hesitates? the case goes up to Claude set the cutoff once, by testing on your own data, not by guessing. 3 repos that already do the routing for you: -> duckdb-jev: route your data. Jev labels every row straight from SQL, up to 1,000 calls in one request -> quicksilver: route your files. Jev checks all 187 files in parallel and Claude gets the 4 that matter. ~2.4k tokens instead of ~26k -> jev-router: route your models. before every message Jev decides simple or hard and sends it to the fast model or the strong one. works with your normal Claude login where this pays off right away: -> support tickets -> your inbox -> lead lists -> messy spreadsheets -> comment moderation on a public benchmark Jev labeled 1,000 rows for $0.015. Claude charged $0.80 for the same job. faster. cheaper. way fewer tokens burned. Jev sorts the mail so the genius only opens what matters. Claude thinks. Jev routes. code does the job.

kiosa

11,388 görüntüleme • 22 gün önce

Here's another JEV TIP in honor of JEVDAY Jev can answer as many questions as you can fit into context in parallel. You can ask hundreds in one call, and since output is free, why not? 100 questions on a 32k token input document: ~$0.00001 per question ~1ms per question

Here's another JEV TIP in honor of JEVDAY Jev can answer as many questions as you can fit into context in parallel. You can ask hundreds in one call, and since output is free, why not? 100 questions on a 32k token input document: ~$0.00001 per question ~1ms per question

Nathan LeClaire

19,292 görüntüleme • 1 ay önce

You can now classify documents with open-weight VLMs at ultra-low cost with our TypeSafe AI Jev-compatible API in the VLM Run gateway! $1 buys you 6700+ pages, and the full 1,651-page OmniDocBench run cost 25 cents. It reads the page as pixels (no OCR->LLM hacks) and hands back one typed, calibrated decision per page - ~180ms p50 e2e. Jev really opened developers' eyes to re-thinking how we process data at the cost-pareto front. A week later we're bringing that to our APIs with vision as a first-class citizen. Try our gateway today - free to sign-up and try!

You can now classify documents with open-weight VLMs at ultra-low cost with our TypeSafe AI Jev-compatible API in the VLM Run gateway! $1 buys you 6700+ pages, and the full 1,651-page OmniDocBench run cost 25 cents. It reads the page as pixels (no OCR->LLM hacks) and hands back one typed, calibrated decision per page - ~180ms p50 e2e. Jev really opened developers' eyes to re-thinking how we process data at the cost-pareto front. A week later we're bringing that to our APIs with vision as a first-class citizen. Try our gateway today - free to sign-up and try!

Sudeep Pillai

20,816 görüntüleme • 1 ay önce

Jev 🤝 CopilotKit We tested UI rendering side by side to demonstrate how Jev from TypeSafe AI can instantly stream components with GPT-6 Luna. Same prompt, renderer and sample data.

Jev 🤝 CopilotKit We tested UI rendering side by side to demonstrate how Jev from TypeSafe AI can instantly stream components with GPT-6 Luna. Same prompt, renderer and sample data.

CopilotKit🪁

21,708 görüntüleme • 1 ay önce

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 Together AI - $0.003 (1/3 of a cent) from Jev on TypeSafe AI. 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.

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 Together AI - $0.003 (1/3 of a cent) from Jev on TypeSafe AI. 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.

Hassan

61,281 görüntüleme • 1 ay önce

Jev by TypeSafe AI is now on OpenRouter, in beta. Jev is a System One model. Instead of generating text, it takes your app's state plus a typed question and returns a typed decision with a probability attached. There is no JSON prompting, parsing layer, and nothing to validate against.

Jev by TypeSafe AI is now on OpenRouter, in beta. Jev is a System One model. Instead of generating text, it takes your app's state plus a typed question and returns a typed decision with a probability attached. There is no JSON prompting, parsing layer, and nothing to validate against.

OpenRouter

568,781 görüntüleme • 1 ay önce

Analyzed a few thousand hours of agentic runs with TypeSafe AI Jev - turns out it's: • The best option I've tested at measuring progress and estimating completion • Dangerous if you use it for detecting harmful commands (more on that below) and • Not very good at catching models being lazy Actual prompts and results in the article:

Analyzed a few thousand hours of agentic runs with TypeSafe AI Jev - turns out it's: • The best option I've tested at measuring progress and estimating completion • Dangerous if you use it for detecting harmful commands (more on that below) and • Not very good at catching models being lazy Actual prompts and results in the article:

Hrishi

28,551 görüntüleme • 1 ay önce

Alright TypeSafe AI cooked Jev is truly the next era of building w LLMs Added this to Scappa tonight

Alright TypeSafe AI cooked Jev is truly the next era of building w LLMs Added this to Scappa tonight

Pontus Karlsson

27,630 görüntüleme • 1 ay önce

Will Jev TypeSafe AI turn $10.000 into profit? Let's find out! Running decisions for paper trades via

Will Jev TypeSafe AI turn $10.000 into profit? Let's find out! Running decisions for paper trades via

Marcel Pociot 🧪

104,714 görüntüleme • 1 ay önce

thanks to TypeSafe AI's Jev we now have massively parallel browser-based adversarial testing suite that tries to break each release. and it costs pennies.

thanks to TypeSafe AI's Jev we now have massively parallel browser-based adversarial testing suite that tries to break each release. and it costs pennies.

Rafal Wilinski

416,039 görüntüleme • 1 ay önce

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 The summaries cost $3.99 on Together AI. The classifications cost $0.08 on TypeSafe AI. 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:

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 The summaries cost $3.99 on Together AI. The classifications cost $0.08 on TypeSafe AI. 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:

Hassan

343,168 görüntüleme • 1 ay önce

Opus 5.5 + GrokBot + Jev... I can't believe that I build it I packed the best of AI into ONE agent - now 99% of people’s AI agents look dumb, slow, and expensive Try here (free): prompt → GrokBot → Jev chooses LLM → Claude / GPT working on GrokBot's computer 24/7 → result → Jev sends only the tasks Grok is weak at to Opus or GPT → Jev picks the best model for each task - for example, Claude for motion design and Codex for web design → runs on the ChatGPT and Claude subscriptions you already pay for (API also work) → works on GrokBot computer while you keep chatting → checks every result against the goal before you see it → GrokBot gets smarter and cheaper at the same time → And plenty more features in a bot everyone will call "obvious" by 2030 Try Jevopus, thank me later - then read the article on the full Jev architecture ↓

Opus 5.5 + GrokBot + Jev... I can't believe that I build it I packed the best of AI into ONE agent - now 99% of people’s AI agents look dumb, slow, and expensive Try here (free): prompt → GrokBot → Jev chooses LLM → Claude / GPT working on GrokBot's computer 24/7 → result → Jev sends only the tasks Grok is weak at to Opus or GPT → Jev picks the best model for each task - for example, Claude for motion design and Codex for web design → runs on the ChatGPT and Claude subscriptions you already pay for (API also work) → works on GrokBot computer while you keep chatting → checks every result against the goal before you see it → GrokBot gets smarter and cheaper at the same time → And plenty more features in a bot everyone will call "obvious" by 2030 Try Jevopus, thank me later - then read the article on the full Jev architecture ↓

codila

274,517 görüntüleme • 1 ay önce

Doc-OCR router using Jev TypeSafe AI A Jev-powered router that looks at a PDF page by page, decides which pages actually need OCR, extracts the rest locally. Result: save cost on # OCR pages + speed

Doc-OCR router using Jev TypeSafe AI A Jev-powered router that looks at a PDF page by page, decides which pages actually need OCR, extracts the rest locally. Result: save cost on # OCR pages + speed

Misbah Syed

27,028 görüntüleme • 1 ay önce

Introducing Amos 1, four open-weight decision models from 0.5B to 27B. > 94.9% on Decision Bench, ahead of Perplexity, Gemini and Jev > beats Jev by 10 points on JevBench hard > reads photos and answers with boxes > decisions in 27 to 122 ms, free API, Apache 2.0

Introducing Amos 1, four open-weight decision models from 0.5B to 27B. > 94.9% on Decision Bench, ahead of Perplexity, Gemini and Jev > beats Jev by 10 points on JevBench hard > reads photos and answers with boxes > decisions in 27 to 122 ms, free API, Apache 2.0

Zaid

36,280 görüntüleme • 1 ay önce

Jev + GrokBot is the best AI agent system I’ve built in my life It just made my setup CHEAPER and FASTER than what 95% of people are running... setup takes literally 7 minutes: prompt → GrokBot → Jev decision → GrokBot execution → result step 1 → open TypeSafe AI , create API key (keep it off chat paste) step 2 → tell Grok Bot: store TYPESAFE_API_KEY in the secure field step 3 → prompt Grok Bot: install typesafe-sdk on Agent Computer + smoke system_one (Choice) step 4 → tell Grok Bot: build the usage lab (router, dry-run, config, logs) - or clone Github below step 5 → add skill jev-usage-router: before browser / research / retry / extra bot → call the router, honor action step 6 → stay shadow first, read logs, then active when you trust it - kill switch: bypass jev or enabled: false step 7 → flip active: GrokBot obeys route - Jev decides - GrokBot executes - humans control irreversible actions the result: Jev + GrokBot the best and fastest agent running directly on your computer rn, I’ve already tested it on routine tasks - and the results are genuinely incredible You can come up with endless ways to use Jev + GrokBot - but the most important thing is to install it as soon as possible Copy this 2028 setup, explore my repo below - then read the full Jev deep dive ↓

Jev + GrokBot is the best AI agent system I’ve built in my life It just made my setup CHEAPER and FASTER than what 95% of people are running... setup takes literally 7 minutes: prompt → GrokBot → Jev decision → GrokBot execution → result step 1 → open TypeSafe AI , create API key (keep it off chat paste) step 2 → tell Grok Bot: store TYPESAFE_API_KEY in the secure field step 3 → prompt Grok Bot: install typesafe-sdk on Agent Computer + smoke system_one (Choice) step 4 → tell Grok Bot: build the usage lab (router, dry-run, config, logs) - or clone Github below step 5 → add skill jev-usage-router: before browser / research / retry / extra bot → call the router, honor action step 6 → stay shadow first, read logs, then active when you trust it - kill switch: bypass jev or enabled: false step 7 → flip active: GrokBot obeys route - Jev decides - GrokBot executes - humans control irreversible actions the result: Jev + GrokBot the best and fastest agent running directly on your computer rn, I’ve already tested it on routine tasks - and the results are genuinely incredible You can come up with endless ways to use Jev + GrokBot - but the most important thing is to install it as soon as possible Copy this 2028 setup, explore my repo below - then read the full Jev deep dive ↓

codila

389,079 görüntüleme • 1 ay önce

Jev + GrokBot is the best GTM system I've ever built It just made my GTM x200 CHEAPER and x400 FASTER than what 95% of teams are running... setup takes literally 9 minutes: prompt → GrokBot → Jev routes every candidate → GrokBot opens only survivors → campaign step 1 → open TypeSafe AI, create API key (keep it off chat paste) step 2 → tell GrokBot: store TYPESAFE_API_KEY in the secure field step 3 → prompt GrokBot: install typesafe-sdk on Agent Computer + smoke system_one (Choice) step 4 → point it at a target: "read end to end, pull positioning, ICP, every proof point. no copy yet" step 5 → add skill gtm-router: every candidate from X / LinkedIn / YouTube gets 6 typed questions → CHEAP SKIP / OPEN FULL / FLAG KOL step 6 → let Jev rank hook archetypes by viral rate, not by how often people post them - this is where the whole playbook comes from step 7 → GrokBot assembles the KOL shortlist and the 7-day plan - you stay in control of anything irreversible the result: → 3,412 candidates, X, LinkedIn and YouTube. → 15.7 seconds. $0.41. → me doing the same reading: 6h 12m. 8 grok bots brief it, Jev decides, GrokBot executes. no fine-tuning, no embeddings, no vector db - 6 typed questions and a schema. Setup your GrokBot JEV GTM today, then read the article below to learn how to build an agent team with JEV.

Jev + GrokBot is the best GTM system I've ever built It just made my GTM x200 CHEAPER and x400 FASTER than what 95% of teams are running... setup takes literally 9 minutes: prompt → GrokBot → Jev routes every candidate → GrokBot opens only survivors → campaign step 1 → open TypeSafe AI, create API key (keep it off chat paste) step 2 → tell GrokBot: store TYPESAFE_API_KEY in the secure field step 3 → prompt GrokBot: install typesafe-sdk on Agent Computer + smoke system_one (Choice) step 4 → point it at a target: "read end to end, pull positioning, ICP, every proof point. no copy yet" step 5 → add skill gtm-router: every candidate from X / LinkedIn / YouTube gets 6 typed questions → CHEAP SKIP / OPEN FULL / FLAG KOL step 6 → let Jev rank hook archetypes by viral rate, not by how often people post them - this is where the whole playbook comes from step 7 → GrokBot assembles the KOL shortlist and the 7-day plan - you stay in control of anything irreversible the result: → 3,412 candidates, X, LinkedIn and YouTube. → 15.7 seconds. $0.41. → me doing the same reading: 6h 12m. 8 grok bots brief it, Jev decides, GrokBot executes. no fine-tuning, no embeddings, no vector db - 6 typed questions and a schema. Setup your GrokBot JEV GTM today, then read the article below to learn how to build an agent team with JEV.

Movez

87,189 görüntüleme • 1 ay önce

We gave Jev 2,029 real phone calls. No transcripts or audio; it never heard a word. Our AI receptionist's calls were reduced to pure structure, meaning turns, tool calls, workflow stages and timing. During the calls, Jev made 38,012 turn-level forecasts at 118 ms median latency, reviewed every call with five typed questions and produced 10,145 answers in 26 seconds with 256 requests in flight. The experiment was zero-shot, with no fine-tuning or examples from our data. We compared Jev's forecasts with what actually happened in the EHR. By the halfway point, Jev could meaningfully separate calls that would book from those that wouldn't (AUC 0.78), and near the end it ranked them correctly 94% of the time. Even though Jev over-focused on visible errors our agent usually overcomes, it's still pretty incredible that it analyzed thousands of real calls in seconds for only $3.

We gave Jev 2,029 real phone calls. No transcripts or audio; it never heard a word. Our AI receptionist's calls were reduced to pure structure, meaning turns, tool calls, workflow stages and timing. During the calls, Jev made 38,012 turn-level forecasts at 118 ms median latency, reviewed every call with five typed questions and produced 10,145 answers in 26 seconds with 256 requests in flight. The experiment was zero-shot, with no fine-tuning or examples from our data. We compared Jev's forecasts with what actually happened in the EHR. By the halfway point, Jev could meaningfully separate calls that would book from those that wouldn't (AUC 0.78), and near the end it ranked them correctly 94% of the time. Even though Jev over-focused on visible errors our agent usually overcomes, it's still pretty incredible that it analyzed thousands of real calls in seconds for only $3.

Muratcan Koylan

374,487 görüntüleme • 1 ay önce

instead of generating text, jev from TypeSafe AI generates structured output this makes it great for classification tasks like model routing, tool selection/search, and guardrails of many forms! it's also ridiculously fast and cheap compared to LLMs doing the same tasks

instead of generating text, jev from TypeSafe AI generates structured output this makes it great for classification tasks like model routing, tool selection/search, and guardrails of many forms! it's also ridiculously fast and cheap compared to LLMs doing the same tasks

Sydney Runkle

52,876 görüntüleme • 1 ay önce