Connect Claude Code and other model providers

Choose a connection method#

Start by connecting one service you already have access to. You can add other services and switch models in a conversation later.

Signing in to Onevium, activating a Onevium license, and obtaining model access are separate steps. A Claude subscription login does not create an API key for the provider form.

Prepare the right account and credential#

Check which service, region, and product your key belongs to: a general API account or a Coding Plan. Kimi Coding Plan and the Moonshot API are separate connections. GLM, Moonshot, and MiniMax also have regional presets. The preset form's Get API key and Official setup guide links can help you check.

Enter secrets only in API Key, not in chat or screenshots. Presets select the authentication method for you. Even for Bearer authentication, enter the raw credential without a Bearer prefix.

Review chat and image models#

Open Settings → Providers → Add AI service. The tables below show the main choices in the 1.2.0 built-in catalog. They describe app presets, not a live check of your account's access.

Chat services

These connections can be selected in the chat composer. A preset supplies the address and API format; normally you only need your API key.

OpenAI, Grok, and Google Gemini can use their native APIs in chat. The Anthropic, DeepSeek, GLM, Kimi, Moonshot, and MiniMax presets use Anthropic-compatible APIs. For a gateway, select its matching connection type.

Entries whose name ends in (1M) run with a 1M context window in Claude Code. OpenAI, Grok, and Gemini connections do not get that window automatically; see 1M context window for the model entry to add.

These names help you find menu choices; they are not a list of IDs to paste. For example, DeepSeek V4.1 Flash uses deepseek-flash, the Kimi Coding Plan K3 main model uses k3-256k, and Moonshot K3 uses kimi-k3[1m]. Do not swap IDs between these connections. Saved custom settings may also differ from a new preset. Check your account's access with an actual request.

Image generation

To generate images, connect a service under Image generation in the same add-service window:

After saving, set Default image model on the provider entry. If you have several image connections, click Use for image generation on the one you want. Image services do not appear in the chat model menu. Choosing a GPT or Gemini chat connection does not configure its image service for you.

Example: connect the DeepSeek preset#

1. Open Settings → Providers → Add AI service.
2. Under Chat services, find DeepSeek and click Connect.
3. Paste your DeepSeek account's API key. The preset supplies https://api.deepseek.com/anthropic and Bearer authentication.
4. Review Visible models, keeping at least one visible. Leave advanced settings at their defaults for your first connection.
5. Click Connect. Once you see the saved provider entry, return to chat.
6. Find the DeepSeek group in the composer's model menu. Select DeepSeek V4.1 Flash or the corresponding option your account can use.

Follow the same process for OpenAI, Grok, Gemini, and other presets, using each service's own key. Saving an entry does not test the upstream connection or switch every conversation.

The retained screenshot below is from an earlier version. Field positions and model names may differ; follow the steps above and the current app menu.

Enlarge imageOriginal components with isolated example data. Enter your own API key and choose visible models; saving still requires verification with a real request.

Manage models and default reasoning effort#

Check the provider and model in the composer before starting a task. Identically named models can belong to different connections. Use the menu selection, not the model's own description of itself in a reply.

Open Settings → Providers → your saved provider → Manage Models to show or hide models, or add a real ID confirmed by the service. Keep at least one visible model per chat connection. See model entries and role mappings for the fields.

In the same window, Default reasoning effort lets you set a default per provider and model. Changes save immediately and supply the default for new conversations. Existing conversations retain their own choice; use the chat composer to adjust the current task. These settings appear only for models with a choice of supported effort levels.

Provider connections are shared within the app, while conversations retain their own selections. Channels and automations also have separate settings; changing the current chat does not change all of them.

Disconnect deletes the provider entry. For an ordinary model switch, use the composer. Before deleting a connection, move conversations, channels, and automations that still reference it to another working connection.

Check configuration, then verify a real request#

Click the stethoscope icon, Check configuration, beside a saved entry. It checks local addresses, credentials, and model records. It does not make an upstream request.

Select your intended model and send a small request:

Reply with one sentence confirming you received this message.
Do not read files or run commands.

After a successful text response, verify a tool in a test project containing README.md:

Read only README.md in the project root and summarize its run instructions.
If it does not exist, say so. Do not create or modify files or run commands.

Check for the actual file-reading tool call and its result. If you need image generation, subagents, channels, or automations, verify those entry points separately. A text response does not establish that all those capabilities work.

Troubleshoot a connection#

Next steps#

Once connected, complete your first task. For a team gateway, see custom providers. To understand which actions a task can take, read permissions.