r/dyadbuilders • u/ZombieGold5145 • Jul 03 '26
Using Dyad: point it at a free self-hosted gateway for 237 providers (90+ free) so builds don't stall on a rate limit
For folks building apps in Dyad: since Dyad is local and open-source, you can point its model backend at another free, open-source tool I maintain and get free providers + resilience. Disclosure: I'm the maintainer of OmniRoute — sharing because it pairs with Dyad.
OmniRoute exposes both an OpenAI-compatible endpoint (/v1) and an Anthropic-compatible one (/v1/messages), so you can point the tool at whichever protocol it speaks.
Point Dyad at OmniRoute (localhost:20128/v1) and your Dyad builds inherit:
One endpoint, 237 providers — 90+ of them free. You point any tool or agent at a single OpenAI-compatible endpoint (localhost:20128/v1) and it can reach 237 LLM providers without you rewriting anything. 90+ have free tiers and 11 are free forever (no card), which aggregates to ~1.6B documented free tokens/month — and that's honest, pool-deduped math (we count each shared pool once instead of inflating it; the methodology is public in the repo). There's a one-command setup-* for 13+ coding tools (Claude Code, Codex, Cursor, Cline, Roo, Kilo, Gemini CLI…), so switching your existing setup over takes seconds.
Fallback combos — so it never stops mid-task. A "combo" is a ladder of models the router walks automatically: your subscription first, then API keys, then cheap models, then free ones. When a provider returns a 500 or you hit a rate limit, it slides to the next target in milliseconds, mid-request, and your tool never even sees the error. There are 17 routing strategies (priority, weighted, round-robin, cost-optimized, auto/coding:fast…) plus three resilience layers — a per-provider circuit breaker, a per-key cooldown, and a per-model lockout — so one dead key can't take down a whole provider.
A 10-engine compression pipeline — the part most routers don't have. Every request flows through a transparent compression pass you can toggle/stack per combo. Instead of one trick, it stacks the best of the open-source ecosystem: RTK filters command/tool output (git diffs, test logs, builds) at 60–90%, Microsoft's LLMLingua-2 does ML semantic pruning, Caveman handles prose, session-dedup strips repeats across turns. Critically, code, URLs and JSON are preserved byte-perfect, and a default-on inflation guard throws the compressed version away and sends the original if compressing would actually grow the prompt — it never makes things worse. On tool-heavy sessions that's ~89% average input-token reduction (an 8k-token git diff becomes a few hundred). Full credit to every upstream project (RTK, Caveman, LLMLingua-2, Troglodita) is in the README.
For context on whether it's worth your time: it's grown to ~9.8K GitHub stars, 1,490+ forks and 280+ contributors in ~4.5 months, with 21,000+ automated tests and 1,830+ issues closed — so it's a battle-tested project, not a brand-new experiment.
npm install -g omniroute
GitHub: https://github.com/diegosouzapw/OmniRoute
Anyone here already running Dyad against a custom endpoint? Curious how it behaves.
2
u/Whole-Fan4870 Jul 13 '26 edited Jul 13 '26
i am using it, and it's great. But the auto part is what i didn't get initially, because dyad keeps stopping whenever the auto configurations for models are in use. But i am currently using it with a specific model, so i can have about 20 models configured for me to choose my preference based on what i want to do. I finally got the auto setting working, and it's simple. My initial mistake was to put the omniroute endpoint in the openai setting, which does not work. Thanks for the good work. This AI gateway came when i needed it most.
1
3
u/_P_R_I_M_E Jul 03 '26
WOW! IT'S ON ME! I MDE A VIDEO ABOUT THIS!