Skip to main content
Choose the tool for the way you work, then use its dedicated guide. Do not copy Base URLs or configuration files blindly between clients: some clients use OpenAI Chat Completions, while others use native Messages or Responses protocols.

​
Quick choice

​
Before changing a local configuration

  1. Create an API key and set a suitable project limit.
  2. Confirm that its token group includes the target model.
  3. Copy the exact model ID from the Model Marketplace or /v1/models.
  4. Back up an existing configuration file before editing it.
  5. Test with one small, read-only request and check the usage log.
Do not run unknown one-click scriptsInstallation or configuration scripts can modify local settings, write credentials, or install third-party code. Use official sources, read a script before running it, and never paste an API key into a script you do not trust.

​
Match the tool to the protocol

The available protocol depends on the model and token group. Read the API and model capability matrix before deciding that a visible model should work in a specific client.

​
A tool is not listed here

If the client supports a custom OpenAI-compatible Base URL, begin with the quick start and that client’s official documentation. Confirm whether it adds /v1 automatically, which protocol it sends, and whether it permits a custom model ID. We do not publish unverified client instructions merely to expand the list.