[AINews] TypeSafe/Jev at >$100M ARR, $7.5B valuation 3 weeks after launch
- ID
- 33976
- Status
- summarized
- Published
- 10 Oct 2026, 2:45 PM
- Fetched
- 10 Oct 2026, 3:45 PM
- Provider
- Latent Space
- Category
- developer-ai
- Original URL
- https://www.latent.space/p/ainews-typesafejev-at-100m-arr-75b
- Source URL
- https://www.latent.space/feed
Summary
- Score
- 8.5
- Created
- 10 Oct 2026, 3:45 PM
- Tags
- Audience
- developersvibe_codersai_ml_learnersai_agent_userssaas_startup_founders
What happened
TypeSafe/Jev is the roundup’s lead: the title claims >$100M ARR and a $7.5B valuation three weeks after launch, while a Diogo Almeida X post cites trillions of tokens/day, 29.4% of the Fortune 500, and a large a16z Series A, with the article noting cynics and astroturfing accusations. The bigger technical story is that multiple vendors shipped or updated “decision” models that return typed answers—probabilities, list picks, scores—in one forward pass, including OpenAI Decisions API on GPT-6 Luna ($0.10/M input tokens, no output charge, claimed up to 10x faster), Microsoft-Decision-1, Perplexity pplx-decider-v1.1-27b (claimed 94.5% on 1,071 Decision Bench cases at $0.017/1K decisions), Cloudflare clef, Liquid d1, vLLM Semantic Router Decision 2.0, and LangSmith using Jev as a judge. Unsloth’s free notebook fine-tunes Qwen3.5-4B into a decision model on 8GB VRAM, and a Qwen3.5-0.8B walkthrough reports 37%→65% accuracy in 60 steps (~10 min on 4GB).
Why it matters
For agent builders, typed decision endpoints can replace some free-text LLM calls for routing, grading, and guardrails, and the concrete price points ($0.017/1K decisions, $0.10/M input tokens) plus 4–8GB fine-tuning recipes make local experiments cheap. But Microsoft-Decision-1 early feedback says decision models still struggle with consistency on complex decisions, so test against your own traces before swapping out deterministic rules; for Malaysia/SEA builders there’s no direct local policy/funding/infra angle here, just tooling cost and architecture choices.
Discussion angle
Where in your agent loop are you really making a decision call—routing, grading, tool choice, guardrails—and what Decision Bench-style evidence would you need before replacing a free-text LLM or deterministic rule with a typed endpoint like OpenAI Decisions, Perplexity decider, or a locally fine-tuned Qwen3.5?