OpenAI-compatible routing endpoint
Send supported chat and Responses requests through https://zergrouter.com/v1 from tools such as Codex, Pi, OpenCode, ZTC, and compatible applications.
ZergRouter
Freemium
ZergRouter routes API traffic for coding clients and OpenAI-compatible apps. Choose available models, use provider credentials or platform-funded DeepSeek access, set Router-key budgets, and track routed usage and connected Codex quotas.
What is ZergRouter?
ZergRouter is an API routing layer that connects supported coding clients and OpenAI-compatible applications to models available through a personal Router. It separates Router API keys, provider credentials, and personal subscriptions so each access path can be managed independently.
The product combines model routing with key controls, usage visibility, and connected Codex quota monitoring. Users can bring provider-issued credentials for eligible routes, use documented platform-managed DeepSeek access when funding requirements are met, and check the authenticated catalog before configuring a client.
What can ZergRouter do?
Model and credential selection
Choose from routes available in the authenticated catalog. Add provider-issued credentials when a route requires them, or use a platform-managed route where explicitly supported.
Scoped Router API keys
Create Router keys with configurable scopes, including the documented chat:write, models:read, and usage:read defaults. Keys can be revoked from the dashboard.
Daily spending budgets
Set a daily USD budget on a Router key. Recorded spend causes requests to be refused after the limit is reached, although in-flight requests can still add usage.
Usage and quota monitoring
Review routed usage by model, date, and client, including input, cached input, and output where providers report those values. Connected Codex accounts show weekly quotas, reset dates, and freshness.
Explicit routing and failover controls
Configure explicit fallback chains for supported chat requests. Among eligible credentials for the same provider, lower priority numbers are tried first; failover is limited to eligible failures before output begins.
Use Cases
“Run DeepSeek from Codex”
Create a Router key, confirm that a model is advertised with Codex Responses capability, and point Codex at the ZergRouter endpoint instead of changing the rest of the coding workflow.
“Standardize model access across tools”
Give coding clients or applications scoped Router keys and route them through one OpenAI-compatible base URL while selecting models and credentials in the Router configuration.
“Control API-key spending”
Assign a daily USD budget to a key used by a script, coding client, or application so recorded Router spend is capped at the configured threshold.
“Choose among connected Codex accounts”
Use subscription monitoring to compare remaining weekly quotas, reset timing, and freshness across connected accounts before selecting an account for a local Codex session.
“Investigate routed activity”
Filter usage by model, date, or client to understand which routes ran and which token categories providers reported, without assuming missing token breakdowns.
Frequently Asked Questions
How do I get started with ZergRouter?
Create a Zerg identity, create a Router API key in the dashboard, store the full key securely, and check the authenticated model catalog. Then configure the relevant client with the Router endpoint and key.
Do I need a separate DeepSeek or Modal API key?
Not for the documented platform-funded DeepSeek route. Check Billing for an available no-card trial or add a card for paid usage. Other routes can require a provider-issued credential or an explicit funding arrangement.
Does creating a Router key purchase model access?
No. A Router key authenticates and scopes requests; it does not provide a model subscription or account balance. The selected route must have eligible credentials or approved platform-funded access.
Will ZergRouter automatically switch my local Codex account?
No. You choose the account for a local Codex session. ZergRouter displays quotas and reset times to help with that decision. Hosted Codex selection is a separate documented workflow.
Where does a DeepSeek request go?
The client sends the request to ZergRouter, which forwards the selected request to Modal Shared Endpoints or Fireworks for DeepSeek inference. The documented shared route is not a customer-controlled deployment, and no particular data-residency region is promised.
Quick Facts
- Category
- Developer Tool
- Primary users
- Developers using coding clients and OpenAI-compatible applications
- API base URL
- https://zergrouter.com/v1
- Documented clients
- ZTC, Codex, Pi, OpenCode, and OpenAI-compatible apps
- DeepSeek route
- modal/deepseek-v4.1-flash, subject to account access and capacity
- Key control
- Scoped Router keys with optional daily USD budgets
