The bundled alibaba plugin registers a video-generation provider for Wan models on Alibaba Model Studio (the international name for DashScope). It is enabled by default; only an API key is needed.

Getting started

Store the key against the `alibaba` provider through onboarding:

```bash
apus onboard --auth-choice alibaba-model-studio-api-key
```

Or pass the key directly:

```bash
apus onboard --alibaba-model-studio-api-key <your-key>
```

Or export one of the accepted env vars before starting the Gateway:

```bash
export MODELSTUDIO_API_KEY=sk-...
# or DASHSCOPE_API_KEY=...
# or QWEN_API_KEY=...
```

```json5
{
  agents: {
    defaults: {
      mediaModels: {
        video: {
          primary: "alibaba/wan2.6-t2v",
        },
      },
    },
  },
}
```

```bash
apus models list --provider alibaba
```

The list includes all five bundled Wan models. If `MODELSTUDIO_API_KEY` cannot be resolved, `apus models status --json` reports the missing credential under `auth.unusableProfiles`.

Built-in Wan models

Capabilities and limits

With exactly one reference image and no video, wan2.6-t2v automatically uses wan2.6-i2v; the result reports the resolved model. This routing applies only when a same-generation image-to-video sibling exists in the known model catalog. Other requests use the selected model's mode. Geometry follows the vendor protocol for that model family.

Wan 2.6 text/reference models translate resolution plus aspectRatio to the documented exact size. Wan 2.6 image-to-video sends the resolution tier and uses the input image's aspect ratio. Wan 2.7 reference-to-video sends the newer media, resolution, and ratio fields and always generates audio.

A request that omits durationSeconds gets DashScope's accepted default of 5 seconds.

Image-to-video and Wan 2.7 reference images accept local files or remote http(s) URLs. Apus sends local images as base64 data URIs, with a maximum of 20 MB per image before encoding. See the Model Studio references for image-to-video and Wan 2.7 reference-to-video. Reference videos and Wan 2.6 reference-to-video images still require remote http(s) URLs.

Advanced configuration

The provider defaults to the international DashScope endpoint. To target the China-region endpoint:

```json5
{
  models: {
    providers: {
      alibaba: {
        baseUrl: "https://dashscope.aliyuncs.com",
      },
    },
  },
}
```

The provider strips trailing slashes before constructing AIGC task URLs.

Apus resolves the Alibaba API key from environment variables in this order, taking the first non-empty value:

1. `MODELSTUDIO_API_KEY`
2. `DASHSCOPE_API_KEY`
3. `QWEN_API_KEY`

Configured `auth.profiles` entries (set via `apus models auth login`) override env-var resolution. See [Auth profiles in the models FAQ](/help/faq-models#auth-profiles-what-they-are-and-how-to-manage-them) for profile rotation, cooldown, and override mechanics.

Both bundled plugins talk to DashScope and accept overlapping API keys. Use:

- `alibaba/wan*.*` ids for the dedicated Wan video provider documented on this page.
- `qwen/*` ids for Qwen chat, embedding, and media understanding (see [Qwen](/providers/qwen)).

Setting `MODELSTUDIO_API_KEY` once authenticates both plugins, since the auth env var list intentionally overlaps; onboarding each plugin separately is not required.

Related

Shared video tool parameters and provider selection.

Qwen chat, embedding, and media-understanding setup on the same DashScope auth.

Agent defaults and model configuration.

Auth profiles, switching models, and resolving "no profile" errors.