Understand this story
On November 17, 2026, TypeSafe AI introduced how to use Jev: the state portion of a request is billed only once, no matter how many questions are asked based on it, so it is usually more cost-effective to first ask all the questions that might be needed, and then use code to filter and organize them. The cited Allie the Icon pointed out that Jev's input token billing is (state + the sum of all questions); asking questions in parallel on the same state incurs the state fee only once, but within a single call, two questions are still more expensive than one question; when cost-sensitive, low-frequency follow-up questions can be run only when actually needed, and when speed is the priority, batch questioning is usually better.
AI-generated from public reports
Latest development · Report
TypeSafe AI discusses Jev's state billing and question strategyDevelopments
1 confirmed developments
Reports and discussion timeline
Browse reports and discussion by time. Their evidence levels remain distinct.
Nov 17
TypeSafe AIFirst-party
TypeSafe AI discusses Jev's state billing and question strategy
TypeSafe AI explains how to use Jev: the `state` portion of a request is billed only once, no matter how many questions you ask based on it; therefore it is usually more cost-effective to first ask all the questions you might need, then use code to filter and organize the results. The cited Allie the Icon points out that Jev bills input tokens as (state + (sum of all questions)); asking questions in parallel against the same state charges the state fee only once, but within a single call two questions still cost more than one; when cost-sensitive, you can run low-frequency follow-up questions only when actually needed, while when speed is the priority, batch questioning is usually better.