OpenRouter API key
Prefer not to use an Anthropic key — or want to run SILV on a different model entirely? OpenRouter gives you one key for many providers: Claude, GPT, Gemini, Grok, DeepSeek, Qwen, and more, billed from a single prepaid balance.
Where to get it
Sign in at openrouter.ai (Google or GitHub login works).
Open Keys from your account menu and click Create Key — copy the sk-or-… value it gives you.
Add credits under Credits — OpenRouter is prepaid, and every model call draws from that balance.
Connect it to SILV
Open the console and switch the provider toggle from ANTHROPIC to OPENROUTER.
Paste your key into the OpenRouter API key field.
Pick a model from the dropdown, or choose Custom model slug… to type any other model. Then start the session — the key and model are validated with a minimal ping before anything else happens.
Picking a model
The dropdown lists flagship tool-calling models — anthropic/claude-opus-4.8 (default), Claude Sonnet 5, Claude Fable 5, GPT-5.5 and GPT-5.5 Pro, Gemini 3.5 Flash, Grok 4.3, DeepSeek V4 Pro, Qwen 3.7 Max, Kimi K2.7 Code, Mistral Medium 3.5, and GLM 5.2. Anything else on openrouter.ai/models works through the Custom model slug option.
tool calling required
SILV drives Discord, Telegram, monitors, and schedules through tools. A model without tool support can hold a conversation but can't operate anything — stick to models that list “tools” in their supported parameters.
Billing & privacy
Usage is billed by OpenRouter against your prepaid credits at each model's own rate — SILV AI adds nothing on top and never sees your balance. Each chat turn and each automation run (a monitor firing, a scheduled task executing) makes model calls on your key.
The same privacy rules as the Anthropic path apply: the key lives in server memory only, scoped to your browser session for at most 12 hours, never written to disk. Every request goes straight from your machine to OpenRouter. Revoke the key anytime at openrouter.ai → Keys; disconnecting already wipes it from memory.
Troubleshooting
“Invalid OpenRouter API key”
The key was rejected — re-copy it from openrouter.ai → Keys (it starts with sk-or-), or generate a fresh one. Zero-balance accounts can also fail here: add credits first.
“OpenRouter couldn't find that model”
The model slug doesn't exist. Check the exact spelling against openrouter.ai/models — slugs look like vendor/model-name.
The model chats but tools and automations fail
The model you picked doesn't support tool calling. Everything in the built-in dropdown does; for custom slugs, check for “tools” support on the model's openrouter.ai page and switch to one that has it.