Qwen qwen¶

Alibaba's Qwen models through the DashScope OpenAI-compatible endpoint. Routes are qwen/<model> over openai-chat, paid by the deployment's own API key.

How we authenticate¶

There is no login flow here. Alibaba Cloud issues a long-lived API key in its own console; an operator stores it once in the Skarbiec vault, and at final use the gateway redeems the deployment's capability for this provider through the local entitlements router, reduces the stored document to the bare key, and sends it as Authorization: Bearer <key>. The key has no refresh path and no invented expiry — it works until DashScope revokes it or an operator replaces it in the vault.

The two failure shapes point at two different repairs: a 503 credential_unauthorized means no capability, read grant or trust material produced a key at final use — repair the authorization chain (runbook); a 502 provider_failure with a provider_authentication: prefix means the key was produced and DashScope rejected it — repair the provider account.

Models¶

No pinned rows: the catalog is discovered live from https://dashscope-intl.aliyuncs.com/compatible-mode/v1/models. Discovery follows the shared provider transport contract; public metadata comes from models.dev and is advisory only. Chat names a concrete qwen/<model> or an alias the route registry points here.

Plan usage¶

DashScope publishes no free plan-usage report for API keys. The ledger records that absence as the provider's own answer, never as a zero (subscription).

Endpoints¶