Using KwikQA
Bring your own key
On the BYOK plans, the CLI sends requests straight to OpenRouter with your own key, and OpenRouter bills your account for model usage. Your evidence never passes through KwikQA's servers.
| Plan | Price | Limits |
|---|---|---|
| BYOK | $10 / month or $100 / year | 500 analyses and 150 fixes a month |
| BYOK Team | $15 / seat / month or $150 / seat / year, 3+ seats | Unlimited, shared by the team |
To count requests toward your plan, the CLI tells KwikQA each request's kind (analysis or fix), model, and provider before it sends it, and nothing else. If OpenRouter doesn't answer, the request is given back.
1. Subscribe
$ npx kwikqa upgrade byo
$ npx kwikqa upgrade byo-team --seats 4Or choose the plan in Billing.
2. Provide your key
$ export OPENROUTER_API_KEY=sk-or-...KwikQA reads the key from the environment and never stores it. If it's missing, commands stop before sending anything.
3. Choose models (optional)
By default you use the same models as the hosted plans. To choose your own, set routes as author/model@provider:
$ export KWIKQA_DIAGNOSIS_MODEL=anthropic/claude-haiku-5.5@anthropic
$ export KWIKQA_REPAIR_MODEL=openai/gpt-6-luna@openai- The model must support strict JSON Schema output through that provider. KwikQA checks OpenRouter's endpoint details before every request and refuses routes that can't meet it.
- Requests use only the provider you name, with fallbacks turned off.
- With your own model routes, KwikQA sends no reasoning-effort setting.
- Token and cost caps still apply to every request and are shown in each preview.
KwikQA's prompts and caps are tuned for the hosted models. Other models may diagnose less reliably.