Answers before you connect
Frequently asked questions
ZergRouter gives your tools one routing endpoint. Your Router key, provider API credentials, and personal subscriptions are different things.
Continue to ZergAI to check current account access. Existing users can sign in.
DeepSeek access
How do I use DeepSeek 4.1 Flash?
Sign in, create a Router key, then send a request to modal/deepseek-v4.1-flash. The DeepSeek guide has a copyable curl command and the Codex setup path. Check GET /v1/models with your Router key for the routes available to your account before configuring a client.
Do I need a separate DeepSeek or Modal API key?
No separate provider credential is needed for platform-funded DeepSeek. Check Billing for an available no-card DeepSeek trial: one-time text usage bounded by both tokens and dollars, with no monthly reset. Paid usage requires a card and is billed monthly with no monthly base fee, subject to your usage cap, the 5M-token monthly Router quota, and shared platform capacity. Without trial or paid access, the request is refused with 402; exhausted trial or global capacity returns 429. Other routes require your own provider credential or an explicit funding arrangement.
Are other DeepSeek or Modal models included?
No. Platform-funded access covers DeepSeek Flash through modal/deepseek-v4.1-flash or the configured funded fireworks/deepseek-v4p1-flash alias, not other models. The authenticated model catalog, not a marketing list, determines what you can call.
Subscriptions, keys, and charges
Why use Router if I already have a Codex subscription?
A Codex subscription is not a Router API balance. Router can connect supported coding clients to models available through your Router, and shows their routed request activity in one place. Separately, Subscriptions can monitor connected personal Codex quota and reset timing. The platform-funded DeepSeek and provider API routes do not spend your ChatGPT or Codex subscription quota.
Does creating a Router key buy model access?
No. A Router key authenticates and scopes requests; it does not itself purchase a subscription. The route must have an eligible credential or approved platform-funded access. Set key scopes and optional daily budgets in the dashboard; check the route and funding path before running paid work.
Can I connect my Claude subscription the same way?
Anthropic API credentials and Claude subscriptions are separate. The Anthropic subscription view records manual quota readings; it does not sign in to Claude or automatically synchronize subscription usage. See the tracking guide.
Data flow and control
Where does a DeepSeek request go?
Your client sends the request to ZergRouter, which forwards the selected model request to Modal Shared Endpoints or Fireworks for DeepSeek inference. This is a shared Modal route, not a customer-controlled deployment. We do not claim a particular data-residency region or that request data never crosses a particular jurisdiction. Review the route and provider terms before sending restricted data.
Can I run my own model deployment?
The shared route does not create or control your own deployment. If deployment location or operator control is required, use a separately configured route whose serving path and terms you have verified. See routing behavior and security architecture.