Genesis now treats Qwen as a first-class bundled provider with canonical id qwen. The bundled provider targets the Qwen Cloud / Alibaba DashScope and Coding Plan endpoints and keeps legacy modelstudio ids working as a compatibility alias.

• Provider: qwen
• Preferred env var: QWEN_API_KEY
• Also accepted for compatibility: MODELSTUDIO_API_KEY, DASHSCOPE_API_KEY
• API style: OpenAI-compatible

Getting started

Choose your plan type and follow the setup steps.

Coding Plan (subscription)

**Best for:** subscription-based access through the Qwen Coding Plan.

Get your API key

    Create or copy an API key from [home.qwencloud.com/api-keys](https://home.qwencloud.com/api-keys).

Run onboarding

    For the **Global** endpoint:

    ```bash
    genesis onboard --auth-choice qwen-api-key
    ```

    For the **China** endpoint:

    ```bash
    genesis onboard --auth-choice qwen-api-key-cn
    ```

Set a default model

    ```json5
    {
      agents: {
        defaults: {
          model: { primary: "qwen/qwen3.5-plus" },
        },
      },
    }
    ```

Verify the model is available

    ```bash
    genesis models list --provider qwen
    ```
  




<div class="callout 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.
</div>

Standard (pay-as-you-go)

**Best for:** pay-as-you-go access through the Standard Model Studio endpoint, including models like `qwen3.6-plus` that may not be available on the Coding Plan.

Get your API key

    Create or copy an API key from [home.qwencloud.com/api-keys](https://home.qwencloud.com/api-keys).

Run onboarding

    For the **Global** endpoint:

    ```bash
    genesis onboard --auth-choice qwen-standard-api-key
    ```

    For the **China** endpoint:

    ```bash
    genesis onboard --auth-choice qwen-standard-api-key-cn
    ```

Set a default model

    ```json5
    {
      agents: {
        defaults: {
          model: { primary: "qwen/qwen3.5-plus" },
        },
      },
    }
    ```

Verify the model is available

    ```bash
    genesis models list --provider qwen
    ```
  




<div class="callout 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.
</div>

Plan types and endpoints

The provider auto-selects the endpoint based on your auth choice. Canonical choices use the qwen-* family; modelstudio-* remains compatibility-only. You can override with a custom baseUrl in config.

Built-in catalog

Genesis currently ships this bundled Qwen catalog. The configured catalog is endpoint-aware: Coding Plan configs omit models that are only known to work on the Standard endpoint.

Multimodal add-ons

The qwen plugin also exposes multimodal capabilities on the Standard DashScope endpoints (not the Coding Plan endpoints):

• Video understanding via qwen-vl-max-latest
• Wan video generation via wan2.6-t2v (default), wan2.6-i2v, wan2.6-r2v, wan2.6-r2v-flash, wan2.7-r2v

To use Qwen as the default video provider:

{
  agents: {
    defaults: {
      videoGenerationModel: { primary: "qwen/wan2.6-t2v" },
    },
  },
}

Advanced configuration

Image and video understanding

The bundled Qwen plugin registers media understanding for images and video
on the **Standard** DashScope endpoints (not the Coding Plan endpoints).

| Property      | Value                 |
| ------------- | --------------------- |
| Model         | `qwen-vl-max-latest`  |
| Supported input | Images, video       |

Media understanding is auto-resolved from the configured Qwen auth — no
additional config is needed. Ensure you are using a Standard (pay-as-you-go)
endpoint for media understanding support.

Qwen 3.6 Plus availability

`qwen3.6-plus` is available on the Standard (pay-as-you-go) Model Studio
endpoints:

- China: `dashscope.aliyuncs.com/compatible-mode/v1`
- Global: `dashscope-intl.aliyuncs.com/compatible-mode/v1`

If the Coding Plan endpoints return an "unsupported model" error for
`qwen3.6-plus`, switch to Standard (pay-as-you-go) instead of the Coding Plan
endpoint/key pair.

Capability plan

The `qwen` plugin is being positioned as the vendor home for the full Qwen
Cloud surface, not just coding/text models.

- **Text/chat models:** bundled now
- **Tool calling, structured output, thinking:** inherited from the OpenAI-compatible transport
- **Image generation:** planned at the provider-plugin layer
- **Image/video understanding:** bundled now on the Standard endpoint
- **Speech/audio:** planned at the provider-plugin layer
- **Memory embeddings/reranking:** planned through the embedding adapter surface
- **Video generation:** bundled now through the shared video-generation capability

Video generation details

For video generation, Genesis maps the configured Qwen region to the matching
DashScope AIGC host before submitting the job:

- Global/Intl: `https://dashscope-intl.aliyuncs.com`
- China: `https://dashscope.aliyuncs.com`

That means a normal `models.providers.qwen.baseUrl` pointing at either the
Coding Plan or Standard Qwen hosts still keeps video generation on the correct
regional DashScope video endpoint.

Current bundled Qwen video-generation limits:

- Up to **1** output video per request
- Up to **1** input image
- Up to **4** input videos
- Up to **10 seconds** duration
- Supports `size`, `aspectRatio`, `resolution`, `audio`, and `watermark`
- Reference image/video mode currently requires **remote http(s) URLs**. Local
  file paths are rejected up front because the DashScope video endpoint does not
  accept uploaded local buffers for those references.

Streaming usage compatibility

Native Model Studio endpoints advertise streaming usage compatibility on the
shared `openai-completions` transport. Genesis keys that off endpoint
capabilities now, so DashScope-compatible custom provider ids targeting the
same native hosts inherit the same streaming-usage behavior instead of
requiring the built-in `qwen` provider id specifically.

Native-streaming usage compatibility applies to both the Coding Plan hosts and
the Standard DashScope-compatible hosts:

- `https://coding.dashscope.aliyuncs.com/v1`
- `https://coding-intl.dashscope.aliyuncs.com/v1`
- `https://dashscope.aliyuncs.com/compatible-mode/v1`
- `https://dashscope-intl.aliyuncs.com/compatible-mode/v1`

Multimodal endpoint regions

Multimodal surfaces (video understanding and Wan video generation) use the
**Standard** DashScope endpoints, not the Coding Plan endpoints:

- Global/Intl Standard base URL: `https://dashscope-intl.aliyuncs.com/compatible-mode/v1`
- China Standard base URL: `https://dashscope.aliyuncs.com/compatible-mode/v1`

Environment and daemon setup

If the Gateway runs as a daemon (launchd/systemd), make sure `QWEN_API_KEY` is
available to that process (for example, in `~/.genesis/.env` or via
`env.shellEnv`).

Related

• Model selection Choosing providers, model refs, and failover behavior.

• Video generation Shared video tool parameters and provider selection.

• Alibaba (ModelStudio) Legacy ModelStudio provider and migration notes.

• Troubleshooting General troubleshooting and FAQ.