Qoder integration status

Qoder ships an IDE, a CLI and a JetBrains plugin. Supporting bring-your-own API keys (BYOK) does not mean supporting an arbitrary third-party gateway.

What we verified

As of this check, the official Qoder IDE custom-model documentation lists Alibaba Cloud Model Studio, DeepSeek, Z.ai, Kimi, MiniMax and Xiaomi MiMo. The documented steps select a built-in provider and model, then enter that provider's API key. A field for an arbitrary Base URL is not confirmed.

InOneAPI integration therefore cannot be confirmed from that documentation. The model detail page no longer generates a file, shows key entry steps or offers a CC Switch import, and it no longer describes selecting a custom endpoint as a supported action.

How to check your version

In Qoder IDE Settings → Models → Add, check the fields in the version you use, and see the official Qoder custom model documentation. Verify the CLI and the JetBrains plugin against their own official documentation; you cannot infer them from the IDE's BYOK support.

Only try https://api.inoneapi.com/v1, an InOneAPI API key and the model ID from the model detail page when your version explicitly supports a custom OpenAI-compatible endpoint. If only a fixed provider catalog exists, do not put an InOneAPI key into the key field for DeepSeek, Model Studio or another official provider.

This means the official capability is not yet confirmed; it is not a runtime proof that no Qoder version supports it. These steps will be updated once official support is documented.