we've been paying AI to read the same document 13 times
TypeSafe gave Jev a 53,777-character GDPR article and 13 questions: 8 Noul, 2 Choice and 3 Score.
they tested two methods, five times each:
> 13 separate calls, one question each
> 1 Jev call containing all 13 questions
batching didn't measurably change the answers. it changed the bill.
13 calls → $0.006090 → 2.71s
1 batch → $0.000497 → 0.27s
12.2× cheaper. 10.0× faster than sequential calls.
the reason is almost stupidly simple: each separate call resends the entire article. Jev can read it once and score all 13 questions against the same state.
if you're building this into an agent:
> put the shared context into one state
> define independent decisions up front
> batch Choice, Score and Noul questions
> execute high-confidence decisions in code
> send uncertain cases to a human
11 of 13 tracked answers were identical across all five runs. the other two varied slightly under both methods.
if your agent asks several questions about the same document, let Jev read it once.
save the complete 4-page Jev field note - then read the full 9-step roadmap and four agent patterns in the article below ↓
someone finally fixed the expensive part
a new AI called Jev was released only a few days ago. it doesn’t generate paragraphs - it makes typed decisions that software can use directly
TypeSafe says Jev is up to 193.6× faster and 444.6× cheaper than frontier models in selected workflow tests
the listed price is $0.042 per million input tokens. output tokens are free
that changes the economics of agents. instead of spending a full LLM call on every yes-or-no branch, Jev can classify, route or score the entire batch
one author-reported example:
700 leads → match / no match → 40 seconds → $0.09
business lift is still unverified, but the decision itself is measurable and easy to audit
the setup:
> define allowed outputs
> batch the inputs
> set a confidence threshold
> execute high-confidence decisions
> send uncertain cases to a human
four patterns already map the idea:
slop detector → score or null
UI selector → choose a component
Mac intent → choose an action
lead matcher → score 700 leads
the 28-second video follows:
FIND → TYPE → BUILD → SHIP
LLMs write and explain. Jev decides. software executes
the full 9-step blueprint and all four patterns are in the article below ↓
WHAT, YOU DON’T LIKE MAKING F***ING GREAT MONEY?
Then why haven’t you watched IBM’s lesson on designing AI teams to handle business workflows?
Just 11 minutes:
01:32 — limit access to company resources
04:15 — give the client one interface
05:50 — organize a team of agents
09:32 — isolate their tools
10:07 — track every action
Absolutely free. Save & watch if you want to earn more with AI and build something of your own.
Want to take those skills further? My guide below walks you through building a working tool with Claude Code + Jev ↓