<Steps>

<Step title="Set an API key">

```bash

openclaw onboard --auth-choice qwen-standard-api-key

```

</Step>

<Step title="Set a default video model">

```json5

{

agents: {

defaults: {

videoGenerationModel: {

primary: "alibaba/wan2.6-t2v",

},

},

}

```

</Step>

<Step title="Verify the provider is available">

```bash

openclaw models list --provider alibaba

```

</Step>

</Steps>

<Note>

Any of the accepted auth keys (`MODELSTUDIO_API_KEY`, `DASHSCOPE_API_KEY`, `QWEN_API_KEY`) will work. The `qwen-standard-api-key` onboarding choice configures the shared DashScope credential.

</Note>

| Model ref | Mode |

| -------------------------- | ------------------------- |

| `alibaba/wan2.6-t2v` | Text-to-video |

| `alibaba/wan2.6-i2v` | Image-to-video |

| `alibaba/wan2.6-r2v` | Reference-to-video |

| `alibaba/wan2.6-r2v-flash` | Reference-to-video (fast) |

| `alibaba/wan2.7-r2v` | Reference-to-video |

| Parameter | Limit |

| --------------------- | --------------------------------------------------------- |

| Output videos | Up to **1** per request |

| Input images | Up to **1** |

| Input videos | Up to **4** |

| Duration | Up to **10 seconds** |

| Supported controls | `size`, `aspectRatio`, `resolution`, `audio`, `watermark` |

| Reference image/video | Remote `http(s)` URLs only |

<Warning>

Reference image/video mode currently requires **remote http(s) URLs**. Local file paths are not supported for reference inputs.

</Warning>

<AccordionGroup>

<Accordion title="Relationship to Qwen">

The bundled `qwen` provider also uses Alibaba-hosted DashScope endpoints for

Wan video generation. Use:

- `qwen/...` when you want the canonical Qwen provider surface

- `alibaba/...` when you want the direct vendor-owned Wan video surface

See the [Qwen provider docs](/providers/qwen) for more detail.

</Accordion>

<Accordion title="Auth key priority">

OpenClaw checks for auth keys in this order:

1. `MODELSTUDIO_API_KEY` (preferred)

2. `DASHSCOPE_API_KEY`

3. `QWEN_API_KEY`

Any of these will authenticate the `alibaba` provider.

<CardGroup cols={2}>

<Card title="Video generation" href="/tools/video-generation" icon="video">

Shared video tool parameters and provider selection.

</Card>

<Card title="Qwen" href="/providers/qwen" icon="microchip">

Qwen provider setup and DashScope integration.

</Card>

<Card title="Configuration reference" href="/gateway/configuration-reference#agent-defaults" icon="gear">

Agent defaults and model configuration.

</Card>

</CardGroup>

| Property | Value |

| -------- | ------------------------------------------------------------------------------------- |

| Provider | `arcee` |

| Auth | `ARCEEAI_API_KEY` (direct) or `OPENROUTER_API_KEY` (via OpenRouter) |

| API | OpenAI-compatible |

| Base URL | `https://api.arcee.ai/api/v1` (direct) or `https://openrouter.ai/api/v1` (OpenRouter) |

<Tabs>

<Tab title="Direct (Arcee platform)">

<Steps>

<Step title="Get an API key">

Create an API key at [Arcee AI](https://chat.arcee.ai/).

</Step>

<Step title="Run onboarding">

```bash

openclaw onboard --auth-choice arceeai-api-key

```

</Step>

<Step title="Set a default model">

```json5

{

agents: {

defaults: {

model: { primary: "arcee/trinity-large-thinking" },

},

},

}

```

</Step>

</Steps>

</Tab>

<Tab title="Via OpenRouter">

<Steps>

<Step title="Get an API key">

Create an API key at [OpenRouter](https://openrouter.ai/keys).

</Step>

<Step title="Run onboarding">

```bash

openclaw onboard --auth-choice arceeai-openrouter

```

</Step>

<Step title="Set a default model">

```json5

{

agents: {

defaults: {

model: { primary: "arcee/trinity-large-thinking" },

},

},

}

```

The same model refs work for both direct and OpenRouter setups (for example `arcee/trinity-large-thinking`).

</Step>

</Steps>

</Tab>

</Tabs>

<Tabs>

<Tab title="Direct (Arcee platform)">

```bash

openclaw onboard --non-interactive \

--mode local \

--auth-choice arceeai-api-key \

--arceeai-api-key "$ARCEEAI_API_KEY"

```

</Tab>

<Tab title="Via OpenRouter">

```bash

openclaw onboard --non-interactive \

--mode local \

--auth-choice arceeai-openrouter \

--openrouter-api-key "$OPENROUTER_API_KEY"

```

</Tab>

</Tabs>

<Tip>

</Tip>

| Feature | Supported |

| --------------------------------------------- | ---------------------------- |

| Streaming | Yes |

| Tool use / function calling | Yes |

| Structured output (JSON mode and JSON schema) | Yes |

| Extended thinking | Yes (Trinity Large Thinking) |

<AccordionGroup>

<Accordion title="Environment note">

If the Gateway runs as a daemon (launchd/systemd), make sure `ARCEEAI_API_KEY`

(or `OPENROUTER_API_KEY`) is available to that process (for example, in

`~/.openclaw/.env` or via `env.shellEnv`).

</Accordion>

<Accordion title="OpenRouter routing">

When using Arcee models via OpenRouter, the same `arcee/*` model refs apply.

OpenClaw handles routing transparently based on your auth choice. See the

[OpenRouter provider docs](/providers/openrouter) for OpenRouter-specific

configuration details.

</Accordion>

</AccordionGroup>

<CardGroup cols={2}>

<Card title="OpenRouter" href="/providers/openrouter" icon="shuffle">

Access Arcee models and many others through a single API key.

</Card>

<Card title="Model selection" href="/concepts/model-providers" icon="layers">

Choosing providers, model refs, and failover behavior.

</Card>

</CardGroup>