The idea in one sentence OmniRoute is a local app that merges all your AI accounts — paid subscriptions, API keys, AND free tiers — into a single endpoint. Your coding tools connect to localhost:20128/v1 as if it were OpenAI, and OmniRoute decides which account to use, rotates between them, and auto-switches when one hits its limit. ## Why this matters (especially for free accounts) You know those free tiers everyone has? - Gemini CLI → 180K free tokens/month - iFlow → 8 models, unlimited, forever - Qwen → 3 models, unlimited - Kiro → Claude access, free The problem: You can only use one at a time. And if you create multiple free accounts to get more quota, providers detect the proxy traffic and flag you. OmniRoute solves both: 1. Stacks everything together — 5 free accounts + 2 paid subs + 3 API keys = one endpoint that auto-rotates 2. Anti-ban protection — Makes your traffic look like native CLI usage (TLS fingerprint spoofing + CLI request signature matching), so providers can’t tell it’s coming through a proxy Result: Create multiple free accounts across providers, stack them all in OmniRoute, add a proxy per account if you want, and the provider sees what looks like separate normal users. Your agents never stop. ## How the stacking works You configure in OmniRoute: Claude Free (Account A) + Claude Free (Account B) + Claude Pro (Account C) Gemini CLI (Account D) + Gemini CLI (Account E) iFlow (unlimited) + Qwen (unlimited) Your tool sends a request to localhost:20128/v1 OmniRoute picks the best account (round-robin, least-used, or cost-optimized) Account hits limit? → next account. Provider down? → next provider. All paid out? → falls to free. All free out? → next free account. One endpoint. All accounts. Automatic. ## Anti-ban: why multiple accounts work Without anti-ban, providers detect proxy traffic by: - TLS fingerprint (Node.js looks different from a browser) - Request shape (header order, body structure doesn’t match native CLI) OmniRoute fixes both: - TLS Fingerprint Spoofing → browser-like TLS handshake - CLI Fingerprint Matching → reorders headers/body to match Claude Code or Codex CLI native requests Each account looks like a separate, normal CLI user. Your proxy IP stays — only the request “fingerprint” changes. ## 30 real problems it solves Rate limits, cost overruns, provider outages, format incompatibility, quota tracking, multi-agent coordination, cache deduplication, circuit breaking… the README documents 30 real pain points with solutions. ## Get started (free, open-source) Available via npm, Docker, or desktop app. Full setup guide on the repo: GitHub: https://github.com/diegosouzapw/OmniRoute GPL-3.0. Stack everything. Pay nothing. Never stop coding.
submitted by /u/ZombieGold5145
Originally posted by u/ZombieGold5145 on r/ClaudeCode
You must log in or # to comment.
