ZergRouter

ZergRouter is a routing service built for people who use coding agents and want to keep their existing tools while choosing which models power them. It presents one OpenAI-compatible endpoint that connects supported clients, so tools that speak the OpenAI protocol can point at ZergRouter rather than being tied to a single model provider. The product's stated promise is simple: keep your coding tools, and choose your models. With ZergRouter you can run DeepSeek in Codex, connect compatible apps through one Router endpoint, set daily budgets for API keys, and see quotas and reset times across your connected Codex accounts. It is aimed at developers and individual users of coding agents such as Codex, Pi, OpenCode, or terminal-native environments, and it gives them a single place to manage routing policy, access, and spend instead of configuring each tool separately. The problem ZergRouter addresses is the fragmentation that appears once you start using more than one model provider and more than one coding account. Normally the routing policy — which model to use, what limits apply, and what happens when a provider fails — lives inside each individual tool, duplicated and drifting out of sync. ZergRouter moves that policy into your account instead; the Product Hunt description states plainly that the routing policy lives in your account, not inside each tool. That matters because developers may work with multiple Codex accounts, each with its own weekly quota and reset schedule, and they may want to try different models such as DeepSeek without abandoning the workflow they already have. Managing budgets per API key, tracking when quota data was last updated, and knowing whether an account has banked resets are all awkward to do by hand. ZergRouter centralizes these concerns behind one endpoint, so the tool you already use stays the same while routing, budgeting, and monitoring happen in one account-level layer. The first core capability is routing. ZergRouter provides one endpoint for your tools. You use provider API credentials together with scoped Router keys, choose models, set limits, and configure explicit fallback chains for supported chat requests. The flow shown on the site is a client sending requests to https://zergrouter.com/v1, which then routes to a model. A Router key connects supported clients, and model availability depends on credentials, permissions, and protocol support. Explicit fallbacks mean that on a 5xx error, a 429 rate-limit response, or a timeout, the system can try your next model rather than simply failing. This is useful because provider errors can otherwise interrupt a request; with an explicit fallback chain that you have already approved, the next model in line is attempted instead. The documentation covers routing behavior in detail, and the site notes that the authenticated catalog is the authority for which models are available to you, so you can check before connecting a client. The second capability group is Codex capacity monitoring. ZergRouter lets you see your Codex capacity by comparing accounts by remaining weekly quotas, each quota's reset date, and banked resets. Stale data stays clearly marked, which means you are told when quota information was last updated rather than being shown a misleading number. API keys and personal subscriptions are separate access paths; a Router API key authenticates routed requests, while provider credentials and Codex subscriptions remain separate. The FAQ makes this explicit: a Router key does not include a model subscription. The value here is decision-making. ZergRouter does not switch your local Codex account automatically; you choose the account for a local Codex session. What the router provides is visibility — quotas and reset times — so that you can decide which account to use. For developers who maintain several accounts to spread load or to keep working when one quota runs dry, having remaining weekly quotas, reset dates, and banked resets in one view removes guesswork and makes account selection deliberate rather than accidental. The third capability group is understanding what ran. ZergRouter lets you explore routed usage by model, by date, and by client. Where providers report them, you can see input, cached input, and output figures. The site is careful about accuracy: account-wide Codex history does not invent missing token breakdowns, and unknown data is labeled as unknown rather than guessed. That approach matters for anyone trying to reconcile what they spent, which client generated the traffic, or which model is driving their token consumption. Because ZergRouter sits between the client and the model, it can aggregate routed usage across the tools you connect — such as Codex, Pi, OpenCode, and other OpenAI-compatible apps — and present it in one place. Rather than relying on each provider's dashboard separately, you get a routed view that distinguishes between input, cached input, and output where that data exists, and clearly marks where it does not. The product's overall approach is a three-part chain: your tool stays the client, ZergRouter is the router, and your chosen model sits behind it. The homepage frames this as keeping the client and choosing the route. A Router key connects supported clients, and requests are sent to the single endpoint at https://zergrouter.com/v1. Model availability depends on your credentials, permissions, and protocol support, and the authenticated catalog is the authority on what you can use. For Codex specifically, the site explains that you can use a model advertised by /v1/models?capability=codex_responses, and that the Modal route supports native Responses forwarding. DeepSeek 4.1 Flash is available as a route. New personal accounts can try it through Modal Shared Endpoints for 14 days after account creation, using a Router key, under a $0.50 UTC-day account-wide trial cap and a 5M-token monthly quota. Other Modal models are not included. Trial access also depends on shared platform capacity and on the Modal endpoint being available, and the site advises checking your authenticated catalog before connecting a client. After the trial, the paid route is metered at $0.30 per 1M input tokens, $0.03 per 1M cached input tokens, and $1.20 per 1M output tokens, up to your monthly usage cap. ZergRouter supports paid usage or bringing your own provider keys, and when you bring your own provider keys they are billed by your provider. The benefits follow directly from those capabilities. Daily budgets for API keys, enforced per request, give you spend control at the key level rather than relying on after-the-fact reporting. Explicit fallback chains reduce the chance that a single provider error stops a request. Quota visibility across connected Codex accounts helps you plan which account to use and when capacity resets. Routed usage by model, date, and client helps you understand where tokens are going. Because the routing policy is stored in your account, changing a model or a limit does not require reconfiguring every tool; you update the policy once. Sign-up and Codex account monitoring are free, so you can evaluate the visibility layer before committing to paid usage. The overall outcome is a coding setup that keeps the tools developers already know while making model choice and spend manageable from one account. Concrete scenarios include running DeepSeek in Codex while keeping your existing Codex workflow, since ZergRouter points the Codex Responses provider at one endpoint. Another is bringing your routed model catalog into the Pi coding agent, or using ZergRouter as an OpenAI-compatible provider in OpenCode. People who use ZTC, a terminal-native coding environment, can connect through the supported client path as well. Developers who already hold provider API keys can bring them and route through one endpoint rather than configuring each tool separately. Anyone maintaining multiple Codex accounts can use the monitoring view to compare remaining weekly quotas, reset dates, and banked resets before choosing which account to use for a local Codex session. A first request is as simple as sending a curl call to https://zergrouter.com/v1/responses with a Router key and a model such as modal/deepseek-v4.1-flash, and the site also provides Python and TypeScript examples for the Router API. ZergRouter is intended for developers and individual users working with coding agents, particularly those who want to choose models independently of the client they use. The integrations and connected tools explicitly listed on the site are ZergAI, Zerg, ZTC, ZDE, Codex, Pi, OpenCode, and OpenAI-compatible apps generally. ZergAI is where you create your Zerg identity and sign in across the stack. Zerg is described as a platform for building and running autonomous software agents, ZTC as a fast terminal-native coding environment, and ZDE as a visual workspace for seeing agent work, files, and execution state. On pricing: creating an account and Codex account monitoring are free. Eligible new personal accounts receive a bounded 14-day DeepSeek trial on platform tokens, subject to the $0.50 UTC-day trial cap and the 5M-token monthly quota. Beyond the trial, DeepSeek on ZergRouter's tokens requires a $5/month plan, metered usage, and a card on file. Your own provider keys are billed by your provider. Access and any billing requirements are confirmed in ZergAI rather than inferred from the marketing page. In short, ZergRouter is an account-level routing layer for coding agents: one OpenAI-compatible endpoint, scoped Router keys with per-key daily budgets, explicit fallback chains, Codex quota visibility, and routed usage analytics. It lets developers keep the tools they already use while choosing the models behind them and keeping spend and capacity in view.