01 / Routing
One endpoint for your tools
Use provider API credentials with scoped Router keys. Choose models, set limits, and configure explicit fallback chains for supported chat requests.
Model choice. API budgets. Codex capacity.
Run DeepSeek in Codex and connect compatible apps through one Router endpoint. Set daily budgets for API keys. See quotas and reset times across your connected Codex accounts.
Continue to ZergAI to check current account access. Existing users can sign in.
One endpoint / many routes
A Router key connects supported clients. Model availability depends on credentials, permissions, and protocol support.
curl https://zergrouter.com/v1/responses \
-H "Authorization: Bearer $ZERGROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "model": "modal/deepseek-v4.1-flash", "input": "Say hi" }'01 / Routing
Use provider API credentials with scoped Router keys. Choose models, set limits, and configure explicit fallback chains for supported chat requests.
02 / Subscriptions
Compare accounts by remaining weekly quotas, each quota’s reset date, and banked resets. Stale data stays clearly marked. API keys and personal subscriptions are separate access paths.
03 / Usage
Explore routed usage by model, date, and client. See input, cached input, and output where providers report them. Account-wide Codex history does not invent missing token breakdowns.
Available route / open-model inference
Create a free Router account and check Billing for an available no-card DeepSeek trial: $1 of usage or 5M tokens, whichever comes first, once per verified email. The dollar limit usually applies first. Paid access through Modal Shared Endpoints or Fireworks requires a card. The 5M-token monthly Router quota and your usage cap are separate controls. Other Modal models are not included.
modal/deepseek-v4.1-flashThe paid route is metered at $0.30 / 1M input tokens, $0.03 / 1M cached input tokens, and $1.20 / 1M output tokens, up to your monthly usage cap. Access also depends on shared platform capacity and the serving endpoint being available; check your authenticated catalog before connecting a client.
Try the DeepSeek quickstart →Works where you work
Connect a supported coding client or build with the Zerg ecosystem. Follow the setup guide for your tool.
Create your Zerg identity and use it to sign in across the stack.
Build and run autonomous software agents on the Zerg platform.
Work with agents from a fast, terminal-native coding environment.
See agent work, files, and execution state in a visual workspace.
Point the Codex Responses provider at one ZergRouter endpoint.
Bring your routed model catalog into the Pi coding agent.
Use ZergRouter as an OpenAI-compatible provider in OpenCode.
No. A Router API key authenticates routed requests; provider credentials and Codex subscriptions remain separate. Platform-funded DeepSeek needs an available trial allowance or paid billing; other provider routes use your own credentials.
Yes. Use a model advertised by /v1/models?capability=codex_responses. The Modal route supports native Responses forwarding; the authenticated catalog is the authority for your available models. Follow the Codex setup guide.
Sign-up and Codex account monitoring are free. Check Billing for an available no-card DeepSeek trial and its remaining allowance. Paid DeepSeek is pay as you go, with no monthly base fee and a card on file. Your own provider keys are billed by your provider.
No. You choose the account for a local Codex session. Router shows quotas and reset times so you can decide which account to use.
Continue to ZergAI to check current account access. Existing users can sign in. Access and any billing requirements are confirmed in ZergAI, not inferred from this page.
Check access