text
Copy
<Steps>
  <Step title="Get your API key">
    Create or copy an API key from [home.qwencloud.com/api-keys](https://home.qwencloud.com/api-keys).
  </Step>

  <Step title="Run onboarding">
    For the **Global** endpoint:

    ```bash}
    openclaw onboard --auth-choice qwen-api-key
    ```

    For the **China** endpoint:

    ```bash}
    openclaw onboard --auth-choice qwen-api-key-cn
    ```
  </Step>

  <Step title="Set a default model">
    ```json5}
    {
      agents: {
        defaults: {
          model: { primary: "qwen/qwen3.5-plus" },
        },
      },
    }
    ```
  </Step>

  <Step title="Verify the model is available">
    ```bash}
    openclaw models list --provider qwen
    ```
  </Step>
</Steps>

<Note>
  Legacy `modelstudio-*` auth-choice ids and `modelstudio/...` model refs still
  work as compatibility aliases, but new setup flows should prefer the canonical
  `qwen-*` auth-choice ids and `qwen/...` model refs. If you define an exact
  custom `models.providers.modelstudio` entry with another `api` value, that
  custom provider owns `modelstudio/...` refs instead of the Qwen compatibility
  alias.
</Note>

text
Copy
<Steps>
  <Step title="Get your API key">
    Create or copy an API key from [home.qwencloud.com/api-keys](https://home.qwencloud.com/api-keys).
  </Step>

  <Step title="Run onboarding">
    For the **Global** endpoint:

    ```bash}
    openclaw onboard --auth-choice qwen-standard-api-key
    ```

    For the **China** endpoint:

    ```bash}
    openclaw onboard --auth-choice qwen-standard-api-key-cn
    ```
  </Step>

  <Step title="Set a default model">
    ```json5}
    {
      agents: {
        defaults: {
          model: { primary: "qwen/qwen3.5-plus" },
        },
      },
    }
    ```
  </Step>

  <Step title="Verify the model is available">
    ```bash}
    openclaw models list --provider qwen
    ```
  </Step>
</Steps>

<Note>
  Legacy `modelstudio-*` auth-choice ids and `modelstudio/...` model refs still
  work as compatibility aliases, but new setup flows should prefer the canonical
  `qwen-*` auth-choice ids and `qwen/...` model refs. If you define an exact
  custom `models.providers.modelstudio` entry with another `api` value, that
  custom provider owns `modelstudio/...` refs instead of the Qwen compatibility
  alias.
</Note>