We built a mechanism that asks 150 famous Jev fictional
Queried Jev with 12 questions across 150 fictional personas to gauge product adoption intent for about 1.8 yen in 5 seconds.
The original post, translated
We built a mechanism that asks 150 famous Jev fictional character introductions about their intention for the product. Each of the 150 throws 12 questions into the API.
The actual cost incurred was 1.8 yen, and the time taken was about 5 seconds. Although it is fast enough, it includes Japan-US latency, so it should be faster
Show the original post in its source language ▾
話題のJevで架空のペルソナ150人に製品の導入意向を聞く仕組みを作ってみた。150人ごとに12個の質問をAPIで投げる。
実際にかかった費用は、1.8円でかかった時間は約5秒。十分爆速だけど日本↔︎アメリカのレイテンシが含まれているので本来はもっと早いはず
The post above is a machine translation from ja; the untranslated text is in the fold-out.
Engagement when collected
Numbers are a snapshot taken from X when the case was added to the library (schema v1, collected 2026-09-19); they will not match today.
Where this case fits
Filed under general Jev builds. In the pattern Jev is built for, the model answers a bounded question per step — and ordinary code acts on the answer, because the answer is already a value rather than a paragraph. Browse the full case library for the work it sits next to.
Keep browsing: all 1173 Jev cases · more from @ytiskw · builders · what Jev is
Last updated: 2026-09-22 · sources & corrections · every card links to its author's original post