Integrations
OpenRouter
An OpenRouter integration stores an organization-owned OpenRouter API key. Agents can use that key when they run selected OpenRouter models.
Use OpenRouter when your organization should reach models available through the OpenRouter catalog. Mobius calls OpenRouter through its OpenAI-compatible chat completions endpoint, so you do not need separate credentials for each upstream model provider. The integration does not add actions or source events.
Capability map
| Capability | Value |
|---|---|
| Provider ID | openrouter |
| Auth kind | api_key |
| Connect flow | Inline API key |
| Actions | No |
| Events | No |
| Webhook delivery | No |
| Event samples | No |
| Live status | No |
Connect OpenRouter
| Surface | Support |
|---|---|
| App | Open Library > Integrations, choose OpenRouter, and paste an OpenRouter API key. |
| CLI | The mobius CLI does not connect OpenRouter integrations yet. Use the app or API. |
| API | Call POST /v1/integrations/providers/openrouter/connect with api_key. |
An organization-owned key takes precedence over the platform credential for OpenRouter models. This keeps agent model calls on your OpenRouter account when platform-funded calls are capped.
Supported models
Mobius currently lists these OpenRouter models in the agent model catalog:
| Model | Catalog ID |
|---|---|
| GLM 5.2 | z-ai/glm-5.2 |
| Qwen3.6 Plus | qwen/qwen3.6-plus |
Use the catalog ID when setting an agent's model field through the API.
Actions
OpenRouter does not register action catalog entries. Use it through agent model selection.
Events
OpenRouter does not register source events.
Next
- Configure model use from agents.
- Review model routing in agent definitions.
- Keep provider keys in integrations.