One builder ran Jev on 1,500 of his own emails
Ryan Vogel posted a long clip of Jev classifying his mail. The sample size is real; the accuracy number is not in the post. Parallel calls were the part viewers argued about.
The morning after launch, Ryan Vogel posted a video demonstrating Jev processing 1,500 personal emails. The post praised the model’s classification speed, followed by a longer YouTube video. Observers discussed whether issuing requests in parallel was more efficient than combining queries into batched calls.
Email categorization is a standard scenario in TypeSafe’s documentation, covering folder routing, urgency scoring, and spam detection. Vogel tested the system on a substantial personal archive rather than synthetic samples. The post omitted formal benchmark statistics, such as accuracy metrics, error distributions, or handling of low-confidence predictions.
In this pattern, the application manages mailbox storage and mail actions, while Jev evaluates the declared classification questions.
This site's reading
Editorial notes evaluating claims against primary sources, contextualizing findings alongside related implementations, and defining technical terms.
Verify
The post reports 1,500 personal emails and notes the author's positive reaction. It does not publish precision, recall, confusion matrices, or the full label set. Responding to questions about parallel requests versus batched evaluations, TypeSafe documentation indicates multiple questions about a single state can share a request, while 1,500 distinct emails require individual requests unless formatted into a single batch. We did not independently run the evaluation. The author's enthusiasm represents a personal demonstration rather than a published benchmark.
Compare
This setup illustrates a basic classification task: assigning text to a defined category or workflow. LangChain's subsequent tutorial follows a similar pattern by scoring ticket urgency and routing. Netlify's changelog provides a contact form triage example routing between sales, support, and spam. Vogel's demonstration predates these and uses a larger dataset. It does not demonstrate whether Jev outperforms a fine-tuned classifier on his data, but shows how a structured model avoids the latency of conversational LLMs for sorting tasks. Reported confidence on Choice reflects the probability distribution rather than measured retrieval precision.
Terms
- State
- The input data provided to Jev, such as a single email or batch. The calling application retrieves and supplies the data.
- Choice
- Selecting a single label from a user-defined set (such as invoice, personal, or newsletter), returning a probability distribution across the options.
- Parallel questions
- Submitting multiple questions regarding the same state within one API request, distinct from classifying multiple different emails simultaneously.