OpenRouter
Run on OpenRouter
OpenRouter is one metered key in front of hundreds of hosted models. It was RoboCo's first key-based external provider with a live catalog: what you pick from is what the API actually serves right now, with real per-token pricing, not a hardcoded list.
OpenRouter models run in their own agent image (the OpenRouter CLI runtime), so flipping the fleet to OpenRouter mode re-spawns agents into that image on their next dispatch.
Set it up once
- Get an API key at openrouter.ai.
- In the panel, open Settings → AI Providers, paste the key into the OpenRouter box, and save it. The key is encrypted server-side and never reaches an agent container as a file - it's injected as an environment variable at spawn.
- Flip the routing mode to OpenRouter, or pin individual agents in Mix mode.
Picking models
With the key saved, the picker on the same settings card queries the live catalog: model ids, context lengths, and prompt/completion prices per million tokens. Clicking a row sets the fleet default model. In Mix mode you can pin different OpenRouter models to different agents the same way.
Guardrails
- Rate limits park the provider exactly like every other provider: the agent's session is paused with a retry-after and resumed automatically.
- Auth failures park instead of crash-looping, and the panel shows the park reason.
Usage and cost
Token usage reported by the model's run log shows up on the agent's cost surfaces like any other provider, attributed at the catalog prices.
Next
- Provider Routing - where OpenRouter sits in the ladder
- Run on Nebius - the open-model sibling with a live catalog
- Resilience - parks, retries, and the reaper