正在加载视频...

视频加载失败

Jev by TypeSafe AI is now on the Venice API, in beta. It answers, it doesn't write. Send it your app's state and typed questions. Get back a typed answer your code can branch on: a probability, a chosen option, or a score on your rubric. No JSON to...

536,864 次观看 • 6 天前 •via X (Twitter)

10 条评论

Venice 的头像
Venice6 天前

Questions you'd hand it: - Which team does this ticket belong to? - Is this refund request eligible? - How urgent is this message? - How frustrated does this customer sound? - Should the agent keep going, or wait for a human? All answered from state your app already has.

Venice 的头像
Venice6 天前

Three question types, one state, one call: 1. noul: "Does this message convey urgency?" → P(yes) = 0.92 2. choice: "Which team should handle this?" → one option, a probability for each, a confidence 3. score: "How frustrated is the customer?" Calm 1 / Frustrated 2 / Very angry 3 → 1.27

Venice 的头像
Venice6 天前

$0.042 per 1M input tokens, output free. 64K tokens per call. Branch on the confidence: 0.90+ act, 0.60+ confirm, below that, hand it to a human. API only: POST /api/v1/decisions with model jev-latest. Same key you use for chat, image, video, and audio.

Eugene Shvarts 的头像
Eugene Shvarts6 天前

@typesafeai My parents call me Jevgeniy

Dae 的头像
Dae6 天前

@typesafeai it's jev 🔥🔥🔥🔥🔥🔥

SkillHub 的头像
SkillHub6 天前

@typesafeai How does it handle uncertainty in the input state?

kimiloo 的头像
kimiloo6 天前

@typesafeai how does it handle inputs that fall outside the rubric?

EKOS _ AGI 🦊 🇮🇷 的头像
EKOS _ AGI 🦊 🇮🇷6 天前

@typesafeai

🌍 EARTH ONLINE 的头像
🌍 EARTH ONLINE5 天前

@typesafeai @RialtoVenice

steadyfreddy.eth 💚 的头像
steadyfreddy.eth 💚5 天前

@typesafeai

相关视频

Jev is cool. So is it's OSS companion, Laya. The Latest Cool Thing In AI™ tends to get a lot of hype, sometimes without everyone even understanding it. So... what is this thing? Jev is an AI model that consumes input and produces output VERY differently than chat, claude, grok. The input is two things: 1) Text state to assess. Email, html, code, whatever. 2) A set of questions which will be asked about the attached state. The canonical example from TypeSafe's docs is to identify the urgency of a support ticket. We pass the model the customer text + a single noul question "is this urgent?". Jev returns a full set of JSON. This JSON is not generated with token-by-token autoregression. Jev is not trained to produce sequences of text tokens, rather to answer questions, and guarantees well-formed responses. In the example below, we see it produces a 0.99 probability (on a 0-1.0 scale) that the answer is "yes." Jev supports exactly three types of questions (seconds example in video): a) Noul: 0–1 probability that the answer to a yes/no question is "yes." b) Choice: Ask question with pre-defined set of answers. Jev chooses the best and assigns probabilities to each. c) Score: Ask question with pre-defined scale of answers. Jev produces a position on the scale. Jev computes answers for all questions in parallel, making responses super fast even for many questions in a single request. This might seem like a narrow set of capabilities, but in the right contexts leads to incredible potential. It also makes for a useful API / primitive for programming, since the outputs are... *ahem*... type-safe and predictable in structure. Jev is not going to replace LLMs for writing your code, auto-generating your docs, or being at the core of an agent harness. But Jev IS incredibly cool, and will be used to build a lot of amazing tech. Hope this helps.

Ben Dicken

40,810 次观看 • 5 天前

LLMs vs. Jev, clearly explained! LLMs are great, and the ceiling is one you can watch scroll past: an LLM writes the answer one token at a time. give it a failed deploy and four decisions, and it produces a small JSON object where every token depends on the one before it. token nine cannot exist until token eight does, so four decisions that had nothing to do with each other just stood in a queue. then your code parses it, validates the shape, and retries when the shape is wrong. Jev fixes this without being a smaller or faster model: it removes the order. one turn on that deploy has to know: → whether the incident is urgent → which team owns it → whether the next command is risky → whether the task is actually done you declare the questions and the answer type upfront, and all four come back together, typed, with a probability on each. three primitives cover almost every fork in an agent: 1. **Choice** picks one of up to 255 options you define, like engineering, billing or sales. 2. **Score** places the state on an ordered scale you define, like low, medium or high risk. 3. **Noul** returns the probability that a yes-or-no condition is true. here is the sentence that resolves the whole confusion: text is a line you have to walk. an answer space is a room you see all of at once. ↳ generation: one order you cannot change, one string at the end, a shape you hope holds ↳ evaluation: no order at all, typed answers, a probability on every option Prompts → Agents → Loops → Graphs → Jev the probabilities matter more than the answer. ↳ engineering at 0.91 against billing at 0.09 is a route you can automate ↳ 0.52 against 0.46 is a coin flip wearing a label, and the label alone never told you which one you got that last one catches careful people. an LLM would have said "engineering" in a confident sentence and given you no way to know the race was that close. thresholds live in your code, one per action, scaled to what being wrong costs. it works when the options are known and the call depends on meaning. it is not for writing, code, arithmetic, or anything where question two needs the answer to question one. and the one that eats whole nights: type safety prevents malformed output, not incorrect judgment. Jev cannot return an option outside your schema, and it can still pick the wrong valid one with confidence. a schema-valid mistake refunds the wrong customer just as fast. an LLM writes new language when the answer space is open. Jev evaluates known paths when the answer space is closed. below i have quoted my full breakdown on Jev. it covers the three primitives, the parallel battery, the thresholds, and where it does not belong. save this and read it below ↓

Hanako

42,632 次观看 • 4 天前