Qwen (Alibaba Cloud)

Qwen official API (Alibaba Cloud Model Studio, international). Bring your own key; nothing is billed by us.

What the harness already knows

Provider id	`qwen`
Base URL	`https://dashscope-intl.aliyuncs.com/compatible-mode/v1`
Protocol	OpenAI-compatible chat completions
API key	`DASHSCOPE_API_KEY`
Model discovery	Yes — the model list is asked of the endpoint rather than shipped.

Connecting it

The endpoint above is built in, so there is nothing to configure. Put the key in the environment and the provider appears in the model picker:

$export DASHSCOPE_API_KEY="..."

Keys are issued by Qwen (Alibaba Cloud) — where to get one.

Models on Qwen (Alibaba Cloud)

The newest models Qwen (Alibaba Cloud) serves that can call tools, from the models.dev snapshot OHarness ships. The harness also asks the endpoint for its live list, so a model released after this snapshot still appears in the picker.

Model id	Context / output	$/M in / cached / out	Reasoning
`qwen3.8-flash`	1M / 131K	0.15 / 0.016 / 0.47	Yes
`qwen3.8-max`	1M / 131K	2 / 0.25 / 6	Yes
`deepseek-v4-flash-0731`	1M / 384K	0.2 / 0.04 / 0.4	Yes
`kimi-k3`	1.05M / 1.05M	3 / 0.3 / 15	Yes
`glm-5.2`	1M / 131K	1.4 / 0.28 / 4.4	Yes
`qwen3.7-plus`	1M / 66K	0.5 / 0.05 / 3	Yes
`qwen3.7-max`	1M / 66K	2.5 / 0.5 / 7.5	Yes
`qwen3.6-flash`	1M / 66K	0.1875 / — / 1.125	Yes
`qwen3.6-27b`	262K / 66K	0.6 / — / 3.6	Yes
`qwen3.6-max-preview`	262K / 66K	1.3 / 0.13 / 7.8	Yes

List prices in USD per million tokens, read from models.dev on 2026-09-19. Qwen (Alibaba Cloud) changes its prices and models; its own pricing page is the authority. Start a session on the newest:

$oharness -m qwen/qwen3.8-flash

Worth knowing

Alibaba Cloud International. Only the international endpoint is listed; a mainland account can point this entry at https://dashscope.aliyuncs.com/compatible-mode/v1 in a user catalog.

Pointing it somewhere else

A regional host, a gateway, or a server of your own. Overrides in ~/.oharness/config.json are field level, so changing the endpoint does not mean restating the rest of the provider — this is the whole block, shown holding the default so the shape is clear:

{
  "providers": {
    "qwen": {
      "baseUrl": "https://dashscope-intl.aliyuncs.com/compatible-mode/v1"
    }
  }
}

What you get either way

The same agent loop, the same tools, the same MCP servers and the same permission rules, whichever provider is underneath — and switching between them mid-session converts nothing, because history is never stored in a vendor’s shape. What an agent harness is covers why that is the hard part, and the providers reference covers the catalogue itself.

All 34 providers · Install OHarness