co-founder @daridotdev // prev @ycombinator, @caltech, basketball data @lakers, software @uber, startups

Fremont, CA
Today, we're releasing our open-weight, auto-routing model @daridotdev, built for coding agents. We're state-of-the-art on the Pareto Frontier, w/ 70% cost reduction + comparable coding performance to Fable. Bring your own evals, choose your models, or use our defaults.
15
21
135
78,316
Avyay Varadarajan retweeted
Today we’re launching Keythorn. AI isn’t just thinking anymore. It’s moving money, talking to customers, and taking action. Every new agent brings new risk. The future runs on AI. We’re building the insurance for it. Meet @TryKeythorn ↓
73
30
199
30,892
Avyay Varadarajan retweeted
Today we're launching > the world's fastest TTS endpoint at 50 ms time-to-first-audio (TTFA) > the world's cheapest modern TTS endpoint at $5 / 1M characters Powered by Qwen3-TTS 1.7B on Nari Labs inference engine. 🚀 5x faster than Cartesia 💸 10x cheaper than ElevenLabs 🎙️ expressive voices, outperforming industry average 🎁 available FREE for a limited time We believe open-source will win: not just in LLMs, but also in multimodal AI. Nari Labs is here to accelerate that future, starting with speech. Try now at narilabs.com
46
48
608
43,498
Avyay Varadarajan retweeted
A 14B open model on a single RTX 4090 matched our hosted frontier model on text-to-SQL. That wasn’t supposed to happen. We ran 28 configurations, graded 25,000+ answers, and benchmarked against Snowflake + Databricks. What we learned: model size, model reputation, and vendor benchmark scores are bad shortcuts for predicting performance on your database. So today we’re open-sourcing mnemiq. Test it on your own data ↓
11
17
118
14,905
Avyay Varadarajan retweeted
token pricing is effectively meaningless now. 3.8 flash looks 13x cheaper when measured per token, but Astra is cheaper per task since it's far more efficient. measure your costs per task, not per token.
GPT-6 Astra is on the pareto-frontier of cost efficiency due to being EXTREMELY token efficient. It is in a whole league of it's own. It is cheaper than Gemini 3.8 Flash per task (a model 13x cheaper than Astra).
66
111
2,168
195,346
if you're running out of Fable weekly limits try running `dari --claude` Use Fable + open models and make your subscriptions last for 2x longer with no quality degredation :)
Literally unusable. The rate limits are absurd. Oh, and by the way, Fable’s automatic continuation is bugged and doesn’t even work. I honestly don’t know why I still bother using Claude at this point. 5.6 is simply better overall anyway. Give me GPT-Astra and im fine. its so frustrating. seriously. oh, and btw. For subscription users, Anthropic has not announced lower prices or higher usage limits regarding Fable 5.1s efficency gains; the savings explicitly apply “wherever usage is billed by token,” so greater efficiency within Pro or Max subscriptions possible not gonna happen.
2
4
14
1,076
some thoughts re: subagents subagents are *great* if you’re selling tokens. increasing token throughput is a massive win for a token seller. nobody has the bandwidth to manage 100 agents concurrently, but if all it takes is one prompt and “ultracode”, you can easily 10x usage!
hot take: you dont need subagents for most work (esp wrt coding agents) yes, it can save context, compaction is fine yes, it can make fanout better, except coordinated work often still sucks yes, its good for adversarial verification, but you prob are doing that elsewhere
1
8
842
of course, the appeal of multi-/sub-agent is massive. you essentially get infinite context if done right (the hugging face exploit is clear evidence of the potential/danger of multi-agent) the labs will obviously continue with multi-agent RL and performance will only improve.
1
2
115
if you’re not cost-insensitive, though, it’s super important to benchmark multi-agent *within your codebase/the environments where you are doing work* harness/thinking level are important to benchmark as well, but subagents naturally have the potential to spike your $/outcome
1
2
66
Avyay Varadarajan retweeted
Overall, I’m very surprised at how little media coverage there’s been around the OpenAI / Hugging Face attack. It’s clearly one of the most important things to happen this year.
606
925
12,314
1,280,323
Model routers and evals go hand-in-hand - router decisions should be based on evals, and you need to eval different models/harnesses within the exact (or very similar) environments that your agents act in to properly measure savings
And people think building model routers is the hard part of "token spend management". :) If you're serious about AI costs, priorities 1 through 10 is having good evals.
2
2
14
1,338
Public evals are saturated. What matters is that a model reliably works in your codebase. To solve this, we built self-bench (github.com/mupt-ai/self-benc…) - an open source package to automatically build evals on your own private PRs. One CLI command -> get a clean Harbor dataset.
10
6
53
8,352
Companies are trying to reduce token costs by using smaller / open-source models, but switching without evals is flying blind. We built evals based on some popular OSS packages like Next.js and Vite. @daridotdev 's auto-router is on the pareto-frontier in all of our tests!
1
4
364
If you want to reduce your token costs without sacrificing performance, you can now: - build an eval on your repo - run open weight models, frontier models, and our router - see cost/performance/latency tradeoffs! book a call to reduce token cost: calendly.com/avyay-dari/30mi…
2
176
Avyay Varadarajan retweeted
We had a great time at last week's Agents & APIs SF Developer Meetup! Thanks to @kwindla of @pipecat_ai, @codemathics of @coderabbitai, Matt Colozzo of @astropods_ and @avyvar of @daridotdev for presenting! 🫶
4
9
2,090
Today, we're releasing our open-weight, auto-routing model @daridotdev, built for coding agents. We're state-of-the-art on the Pareto Frontier, w/ 70% cost reduction + comparable coding performance to Fable. Bring your own evals, choose your models, or use our defaults.
15
21
135
78,316
To get here, we finetuned an SLM to be benchmark, cost, and cache aware. Using our SLM adds negligible latency - we only use the results for the next query in an agent loop. Blog: dari.dev/blog/auto-routing-m…, dari.dev/cache-cost-curve/in… Model link: huggingface.co/dari-ai/route…
2
12
925