OpenRouter

Mobius can store an organization-owned OpenRouter API key and prefer it over a platform OpenRouter credential. The connection does not add actions or source events.

The current assistant model picker does not offer an OpenRouter model. Mobius retains metadata for older GLM 5.2 and Qwen3.6 Plus assignments so it can interpret existing records, but those entries are outside the current list for new assistant models and conversation overrides. Connecting a key does not put them back in the picker.

Connect only for an existing assignment

If your organization already has an assistant assigned to an OpenRouter model, open Build > Integrations > OpenRouter, select Connect OpenRouter, enter the OpenRouter API key, and select Save credentials.

Through the API, send api_key to POST /v1/integrations/providers/openrouter/connect. The provider ID is openrouter.

An organization key uses the connected account's quota. Without it, an existing OpenRouter assignment may use a configured platform credential, which requires eligible Mobius funding when the turn runs. Read the turn error if an existing assignment fails; credential, plan, and model-availability failures need different fixes.

For a new assistant, choose a model that appears in its current Model menu. Do not copy a retained OpenRouter ID from an old record into a new definition. The saved assistant model remains the default for unpinned conversations, while a model selected at conversation creation stays pinned to that conversation.

See Integrations for how connections are owned and Assistant instructions and settings for the current model behavior.