Models and tools
OpenRouter
An OpenRouter integration stores a project-owned OpenRouter API key so Mobius-hosted agents can run selected OpenRouter models through that key.
Use OpenRouter when a project should reach models available through the OpenRouter catalog without giving Mobius direct credentials for each upstream model provider. Mobius calls OpenRouter through its OpenAI-compatible chat completions endpoint. 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 Govern > 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/projects/{project}/integrations/providers/openrouter/connect with api_key. |
A project-owned key takes precedence over the platform credential for OpenRouter models. This lets paid projects keep agents running through bring-your-own-key credentials even when platform-funded model 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 steps.
- Keep provider keys in integrations.