Загрузка видео...

Не удалось загрузить видео

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

Jev with Exa is INSANE. > Jev without websearch confidently gives wrong outputs > Jev with websearch is literally much more accurate Try Jev (with Exa websearch) for free 👇

Ishan Goswami

15,119 subscribers

201,206 просмотров • 8 дней назад •via X (Twitter)

Образование Наука и технологии

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Why is nobody posting about this? This is hands down the BEST way to run Jev right now. You can use the new Jev Playground to start running decisions with Jev for FREE. You're welcome. →

Why is nobody posting about this? This is hands down the BEST way to run Jev right now. You can use the new Jev Playground to start running decisions with Jev for FREE. You're welcome. →

Miles Deutscher

37,131 просмотров • 9 дней назад

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

118,970 просмотров • 13 дней назад

Jev is INSANE 😳 you can use Jev for FREE on OpenRouter it scanned 471 news stories in 31.9 seconds and picked 15 brands worth jumping on - 471 headlines scanned - 15 brand opportunities found - 31.9 seconds - $0.0065 total cost > Claude Opus 5: 17/471 > cost: $0.386 > roughly 1,650x cheaper per headline try Jev here:

K2S

15,167 просмотров • 10 дней назад

After playing with the Jev hybrid model, I started looking into OpenJev, and started with a halite 1 implementation with: GLM 5.3 Flash + Jev [vs] GLM 5.3 Flash + OpenJev OpenJev is just a 4B model handily defeating Jev (in this tiny silly toy example ofc). Now I'm super curious to learn what Jev's actual model size is.

After playing with the Jev hybrid model, I started looking into OpenJev, and started with a halite 1 implementation with: GLM 5.3 Flash + Jev [vs] GLM 5.3 Flash + OpenJev OpenJev is just a 4B model handily defeating Jev (in this tiny silly toy example ofc). Now I'm super curious to learn what Jev's actual model size is.

Harrison Kinsley

24,958 просмотров • 8 дней назад

The gains aren’t free: Jev can't generate text Comparing Jev vs LLMs side-by-side makes the trade-off clear Fun fact: replacing sequential computation with parallel is the same way Transformers leapfrogged RNNs

The gains aren’t free: Jev can't generate text Comparing Jev vs LLMs side-by-side makes the trade-off clear Fun fact: replacing sequential computation with parallel is the same way Transformers leapfrogged RNNs

Diogo Almeida

2,105,604 просмотров • 14 дней назад

This is f*ckin awesome. A Stanford team pairs JEV with Claude Code to sort 75 billion data points every 11 minutes. JEV runs a cheap first pass on everything. Claude only gets the hard cases. Faster, cheaper, way less compute burned.

This is f*ckin awesome. A Stanford team pairs JEV with Claude Code to sort 75 billion data points every 11 minutes. JEV runs a cheap first pass on everything. Claude only gets the hard cases. Faster, cheaper, way less compute burned.

kiosa

61,633 просмотров • 4 дней назад

Found a great production use case for Jev. I used Jev to organize ~2.3K AI research papers. The total cost was $0.14, and it took about 83 seconds. The process: The papers already had old tags, which I ran through a previous open model (DeepSeek V4 Flash). However, I wasn't confident in the classifications, and I didn't want to spend more on tokens unless I spent time tuning it into a good LLM classifier via few-shot (more expensive). Too tedious, too costly, and unsustainable. Luckily for us, we now have Jev to help us with organizing papers better. So Jev first went through all the papers and retagged them. It agreed with 75% of the previous tags. Jev found about 579 high-confidence topic changes. I evaluated reliability by manually labeling 30 disagreements and accepted all of them. I was astonished by Jev's classification capabilities. We applied and verified all changes in production. I'm much more satisfied with the classifications, but I think there is still room for improvement. Check out the papers here: I will experiment with Jev more. The takeaway is that pipelines can be significantly improved by carefully combining System One and System Two models. Jev clearly unlocks more interesting ways to organize papers and offer a more useful discovery layer for research papers. More updates on that soon.

Found a great production use case for Jev. I used Jev to organize ~2.3K AI research papers. The total cost was $0.14, and it took about 83 seconds. The process: The papers already had old tags, which I ran through a previous open model (DeepSeek V4 Flash). However, I wasn't confident in the classifications, and I didn't want to spend more on tokens unless I spent time tuning it into a good LLM classifier via few-shot (more expensive). Too tedious, too costly, and unsustainable. Luckily for us, we now have Jev to help us with organizing papers better. So Jev first went through all the papers and retagged them. It agreed with 75% of the previous tags. Jev found about 579 high-confidence topic changes. I evaluated reliability by manually labeling 30 disagreements and accepted all of them. I was astonished by Jev's classification capabilities. We applied and verified all changes in production. I'm much more satisfied with the classifications, but I think there is still room for improvement. Check out the papers here: I will experiment with Jev more. The takeaway is that pipelines can be significantly improved by carefully combining System One and System Two models. Jev clearly unlocks more interesting ways to organize papers and offer a more useful discovery layer for research papers. More updates on that soon.

elvis

15,427 просмотров • 8 дней назад

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

565,517 просмотров • 12 дней назад

You can now use Jev right inside Claude Code 🤯 It's called jev-model-router, an early access mod built on Claude Code's new function hooks. Before every turn, it checks in with Jev and asks: > how mechanical the task is > how much reasoning it needs > whether it's risky Then it routes: → it'll move up to a stronger model on weak evidence, and only drops to a cheaper one when it's confident the task is simple → every decision gets logged in your transcript → if the call fails, your request runs untouched Setup: 1. copy the install command: npx claude-code-templates@latest --mod productivity/jev-model-router 2. paste it inside Claude Code 3. run claude with CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 set 4. accept the trust prompt on first launch Link: Also works with no api key, it just falls back to a built-in classifier with no confidence score. For real jev routing, add your typesafeApiKey or gatewayApiKey to ~/.claude/settings.json. Follow me for more AI workflows and tutorials.

You can now use Jev right inside Claude Code 🤯 It's called jev-model-router, an early access mod built on Claude Code's new function hooks. Before every turn, it checks in with Jev and asks: > how mechanical the task is > how much reasoning it needs > whether it's risky Then it routes: → it'll move up to a stronger model on weak evidence, and only drops to a cheaper one when it's confident the task is simple → every decision gets logged in your transcript → if the call fails, your request runs untouched Setup: 1. copy the install command: npx claude-code-templates@latest --mod productivity/jev-model-router 2. paste it inside Claude Code 3. run claude with CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 set 4. accept the trust prompt on first launch Link: Also works with no api key, it just falls back to a built-in classifier with no confidence score. For real jev routing, add your typesafeApiKey or gatewayApiKey to ~/.claude/settings.json. Follow me for more AI workflows and tutorials.

Alvaro Cintas

42,282 просмотров • 8 дней назад

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

431,889 просмотров • 12 дней назад

I shared 10 Jev use cases for marketers. Here are 10 more: 11. Ad creative scoring - Feed it 100 ad variations. Jev can score which hooks, headlines, or angles are most worth testing first. 12. Social post filtering - Monitor thousands of posts. Jev can flag the ones worth replying to, reposting, or using as sales signals. 13. ICP detection - Give it a company, profile, or website. Jev can score how closely it matches your ideal customer. 14. Buying signal detection - Someone posts that they're switching tools, hiring, raising money, or struggling with a problem. 15. Comment prioritization - Get hundreds of comments across LinkedIn, X, YouTube, or Product Hunt. Jev can score which ones deserve a reply first. 16. Review analysis - Feed it thousands of customer reviews. Jev can classify sentiment, complaints, feature requests, and purchase intent. 17. Influencer matching - Give it 5,000 creators. Jev can score which ones best match your product, audience, and campaign. 18. Sponsorship qualification - Feed it newsletters, podcasts, or creator media kits. Jev can score audience fit, relevance, and whether they're worth reviewing. 19. UGC selection - Give it dozens of videos, screenshots, and testimonials. Jev can score which ones are strongest for ads or landing pages. 20. Product Hunt monitoring - Scan launches, comments, and makers to find competitors, customers, partners, or interesting products. The more repetitive marketing decisions you have to make at scale, the more interesting Jev becomes.

Yum⋆₊˚

385,317 просмотров • 10 дней назад

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

337,656 просмотров • 13 дней назад

JEV is INSANE. We gave it 400 companies and one candidate profile. In 12 seconds, it predicted which jobs the candidate had the highest chance of getting, assigned a confidence score and detected job-candidate mismatches. All for just $0.0005 It can also score companies, analyse your experience, match you with the right roles and identify the opportunities you’re most likely to get based on your profile. Coming soon to Backdoor Comment “JEV” for early access.

Sarvagya Kulshreshtha

150,828 просмотров • 11 дней назад

$Jev + Muse is the first AI agent system that actually automate 100% of my life 99% of people pay 200x more for slower AI agents - while 1% run this 2030 setup just 5 min and setup is ready: prompt → Muse → Jev decision → Muse execution → result step 1 → create your Jev API key (typesafe website) step 2 → clone and install the complete router from Github below python3 -m venv .venv && .venv/bin/pip install -r requirements.txt && cp config.example.yaml config.yaml step 3 → export the key before running anything: export TYPESAFE_API_KEY='YOUR_KEY' add the same export to ~/.zshrc or ~/.bashrc if you want it to survive a new terminal session step 4 → give your agent skill/jev-decision-layer.SKILL.md and connect it to src/router.py + recipes/ , raw Jev returns probabilities - the router converts them into executable actions step 5 → test the entire chain, not the raw Jev API: .venv/bin/python -m src.cli '{"goal":"what is 2+2?","kind":"chat"}' the final JSON should contain action, reason, mode, jev_used and confidence details step 6 → keep mode: shadow for 20–50 real decisions: the agent works normally while Jev’s routes are logged and checked; promote only reliable question packs step 7 → switch to mode: active with hard confidence gates: ≥0.80 act automatically, 0.50–0.79 advisory only, <0.50 escalate to the human the result: Jev + Muse is a system that decides what to do, what to skip and when to bring in - I’ve tested it across my daily workflows, and it’s the best setup I’ve found for automating routine Take the exact stack I built, run it yourself from the repo - then read the full Jev architecture behind it ↓$

Jev + Muse is the first AI agent system that actually automate 100% of my life 99% of people pay 200x more for slower AI agents - while 1% run this 2030 setup just 5 min and setup is ready: prompt → Muse → Jev decision → Muse execution → result step 1 → create your Jev API key (typesafe website) step 2 → clone and install the complete router from Github below python3 -m venv .venv && .venv/bin/pip install -r requirements.txt && cp config.example.yaml config.yaml step 3 → export the key before running anything: export TYPESAFE_API_KEY='YOUR_KEY' add the same export to ~/.zshrc or ~/.bashrc if you want it to survive a new terminal session step 4 → give your agent skill/jev-decision-layer.SKILL.md and connect it to src/router.py + recipes/ , raw Jev returns probabilities - the router converts them into executable actions step 5 → test the entire chain, not the raw Jev API: .venv/bin/python -m src.cli '{"goal":"what is 2+2?","kind":"chat"}' the final JSON should contain action, reason, mode, jev_used and confidence details step 6 → keep mode: shadow for 20–50 real decisions: the agent works normally while Jev’s routes are logged and checked; promote only reliable question packs step 7 → switch to mode: active with hard confidence gates: ≥0.80 act automatically, 0.50–0.79 advisory only, <0.50 escalate to the human the result: Jev + Muse is a system that decides what to do, what to skip and when to bring in - I’ve tested it across my daily workflows, and it’s the best setup I’ve found for automating routine Take the exact stack I built, run it yourself from the repo - then read the full Jev architecture behind it ↓

codila

91,306 просмотров • 7 дней назад

JEV ENGINEERING JUST CUT A CLAUDE LOOP FROM $765/MONTH TO $3.02 the expensive part isn’t always writing code. a busy overnight loop can burn ~600 decisions just asking what to do next, whether a command is safe, or if the task is finished. trigger → Jev → allow / stop / wake → Claude only builds when needed at roughly 4,000 tokens per decision, those checks can cost ~$25.50 a night on Fable 5.1. Jev handles the same decision layer at $0.042 per 1M input tokens with output free. over 30 nights that moves the decision bill from ~$765 to $3.02. batch multiple questions into one call and it falls again to about $1.08/month. that’s the part i care about: Claude keeps the expensive work that actually needs intelligence, while Jev handles the hundreds of tiny judgment calls around it.

JEV ENGINEERING JUST CUT A CLAUDE LOOP FROM $765/MONTH TO $3.02 the expensive part isn’t always writing code. a busy overnight loop can burn ~600 decisions just asking what to do next, whether a command is safe, or if the task is finished. trigger → Jev → allow / stop / wake → Claude only builds when needed at roughly 4,000 tokens per decision, those checks can cost ~$25.50 a night on Fable 5.1. Jev handles the same decision layer at $0.042 per 1M input tokens with output free. over 30 nights that moves the decision bill from ~$765 to $3.02. batch multiple questions into one call and it falls again to about $1.08/month. that’s the part i care about: Claude keeps the expensive work that actually needs intelligence, while Jev handles the hundreds of tiny judgment calls around it.

Gipp 🦅

24,887 просмотров • 2 дней назад

Jev + SERV is actually insane. We already showed you can increase Jev's performance with SERV Reasoning. Now we're taking it further, bringing Jev-powered Decision nodes into Graph Sharding with the upcoming SERV v3. Here's a breakdown of how it works: Jev is a decision-making model. Given a task and a set of options, it predicts which path is more likely. Think of the octopus that predicted World Cup results. Jev does that for your business, except it's not luck. It weighs every option and tells you how sure it is. It does this by assigning probabilities to outcomes. It doesn't generate text on its own, so you can't expect it to create a new outcome for you. But that's also what enables it to be lightning fast and dirt cheap. For example, in customer service you can ask Jev how to triage an incoming query and route it to the correct department. It can only select from the list of departments you provide it. This also means it can't hallucinate a new outcome outside the options it's given, which makes it incredibly interesting for OpenServ. In Graph Sharding, we take a single system prompt and break it down into multiple LLM steps with deterministic input and output shapes. Some of these steps require an LLM to produce new output, while others are simply decision routers that determine the next possible path. Traditionally, LLMs are slow and expensive. Breaking a single prompt into multiple steps increases accuracy and reliability by a ton, but it also introduces latency. Jev takes on those decision nodes, which are the backbone of a business process and therefore SERV graphs, and makes them super consistent and lightning fast, lowering the overall cost and latency of graph execution. SERV Reasoning on its own is a great force multiplier for Jev because, like all other models, it works by interpreting input instructions. The clearer those instructions are, the better the model performs. That's where SERV Reasoning comes into play. Just like amplifying any other model, we also amplify the accuracy and consistency of Jev's responses. And now we're bringing Jev-powered Decision nodes into Graph Sharding with SERV v3.

Jev + SERV is actually insane. We already showed you can increase Jev's performance with SERV Reasoning. Now we're taking it further, bringing Jev-powered Decision nodes into Graph Sharding with the upcoming SERV v3. Here's a breakdown of how it works: Jev is a decision-making model. Given a task and a set of options, it predicts which path is more likely. Think of the octopus that predicted World Cup results. Jev does that for your business, except it's not luck. It weighs every option and tells you how sure it is. It does this by assigning probabilities to outcomes. It doesn't generate text on its own, so you can't expect it to create a new outcome for you. But that's also what enables it to be lightning fast and dirt cheap. For example, in customer service you can ask Jev how to triage an incoming query and route it to the correct department. It can only select from the list of departments you provide it. This also means it can't hallucinate a new outcome outside the options it's given, which makes it incredibly interesting for OpenServ. In Graph Sharding, we take a single system prompt and break it down into multiple LLM steps with deterministic input and output shapes. Some of these steps require an LLM to produce new output, while others are simply decision routers that determine the next possible path. Traditionally, LLMs are slow and expensive. Breaking a single prompt into multiple steps increases accuracy and reliability by a ton, but it also introduces latency. Jev takes on those decision nodes, which are the backbone of a business process and therefore SERV graphs, and makes them super consistent and lightning fast, lowering the overall cost and latency of graph execution. SERV Reasoning on its own is a great force multiplier for Jev because, like all other models, it works by interpreting input instructions. The clearer those instructions are, the better the model performs. That's where SERV Reasoning comes into play. Just like amplifying any other model, we also amplify the accuracy and consistency of Jev's responses. And now we're bringing Jev-powered Decision nodes into Graph Sharding with SERV v3.

Armagan Amcalar

365,108 просмотров • 6 дней назад

Introducing Motion Studio. Edit animations directly on your site with our intuitive visual editor and our new Ultramotion animation editing agent (powered by TypeSafe AI's Jev) for at least 10x faster edits than code LLMs. Inspection and visual editing are free!

Introducing Motion Studio. Edit animations directly on your site with our intuitive visual editor and our new Ultramotion animation editing agent (powered by TypeSafe AI's Jev) for at least 10x faster edits than code LLMs. Inspection and visual editing are free!

Motion

29,362 просмотров • 8 дней назад

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

85,453 просмотров • 9 дней назад

WAIT. This is actually insane. I fed Jev my last 468 tweets and hid all the numbers. It picked out my strongest hooks without seeing a single view count. Like it somehow knew which ones stopped the scroll just by reading them. That was 2,340 decisions in 60 seconds for 1.3 cents. Every boring decision you make by staring at a screen can run like this now. This is actually stupid how good this is. If you haven't set up Jev as your decision maker yet, you're already behind. Full breakdown in the article below.

WAIT. This is actually insane. I fed Jev my last 468 tweets and hid all the numbers. It picked out my strongest hooks without seeing a single view count. Like it somehow knew which ones stopped the scroll just by reading them. That was 2,340 decisions in 60 seconds for 1.3 cents. Every boring decision you make by staring at a screen can run like this now. This is actually stupid how good this is. If you haven't set up Jev as your decision maker yet, you're already behind. Full breakdown in the article below.

Prajwal Tomar

30,000 просмотров • 8 дней назад

Looking for inspiration on what you are able to do with Jev (by Typeface) this weekend? Built a website called Jevable ( which showcases all the fun demos on X - filterable by a few categories. Feel free to add your own project by using the + button!

Looking for inspiration on what you are able to do with Jev (by Typeface) this weekend? Built a website called Jevable ( which showcases all the fun demos on X - filterable by a few categories. Feel free to add your own project by using the + button!

Nikunj Kothari

174,357 просмотров • 11 дней назад