跳到正文
RadarAI· X:TypeSafe AI (@typesafeai)·· 1 天前AI 评分38

Jev 计费用法解析:state 只计费一次,多问题并行更省钱

AI 导读

Jev 的输入 token 按 state 加全部问题之和计费,state 部分无论并行问多少个问题都只收一次费。因此把可能需要的问题一次性批量提出、再用代码筛选结果通常更便宜;成本敏感时可按使用频率省略低频追问,速度优先时批量提问基本总是更快,但单个超大追问可能拖慢调用,需按频率拆分。

正文 · 原文

TypeSafe AI· @typesafeai · X·2026-11-17 05:17· 39 分钟前AI 评分60

AI 导读

TypeSafe AI 讲解 Jev 的计费机制:请求按 state 加全部问题计费,state 部分无论并行问多少个问题都只收一次费。因此通常先一次性提出所有可能需要的问题再用代码筛选结果更便宜;引用内容补充,成本敏感时可按使用频率省略低频追问,速度优先时批量提问基本总是更快,但超大追问可能拖慢单次调用,需视频率拆分。

正文 · 原文

how to Jev

  • you pay for the state part of your request once, no matter how many questions you ask about it
  • so it's usually cheaper to ask every question you might want answered, even before you know if you need the answer
  • then use code to sort it out

take in all the information you might need, and filter down to what's important! reliable automation means covering all your bases

引用Allie the Icon@allietheicon

The answer has nuance!

The way Jev charges for input tokens is:
(state+(sum of all questions))

The important bit here is that you only get charged once for your state tokens no matter how many questions you run in parallel.

Within a single call, two questions do cost more than one. But if you ask those two questions as separate requests with the same state, you pay more overall, because you pay for the state again in the second request.

In cases where you are more cost-sensitive than speed-sensitive, it makes sense to do analysis on how often the follow-up questions are used in your use-case. If some follow-ups are needed very rarely, then you can save on cost by running them only when actually needed.

But in cases where speed is more important than cost, then batching pretty much always wins (although there's some nuance there as well, such as a single super-huge follow-up question slowing down the call, so shunting it to its own call could make sense, depending on the frequency that that answer is needed!)

在 X 查看被引用的帖子

来源:TypeSafe AI · x.com

来源:RadarAI · aihot.news