Proposal: document QwenCloud as the current Qwen API platform while preserving LiteLLM compatibility

[evelyn-jialin-zhang]

Context

QwenCloud is an AI model platform for international developers, providing access to Qwen, Wan, CosyVoice, and other models through OpenAI- and Anthropic-compatible APIs. DashScope, Bailian, Alibaba Cloud Model Studio, TONGYI, and related ecosystem-facing brands are being unified under QwenCloud.

Aider can already access Qwen models through LiteLLM-compatible model names such as dashscope/qwen-*. We would like to make the current QwenCloud entry points easier to discover without breaking existing Aider or LiteLLM configurations.

Proposal

Would the maintainers prefer:

1. updating the existing Qwen/DashScope documentation to identify QwenCloud as the current user-facing platform while preserving dashscope/ model compatibility; or
2. waiting for the upstream LiteLLM migration decision before changing Aider documentation?

This proposal does not require a new Aider-native provider unless the maintainers believe one is necessary.

Official references

• Website: https://www.qwencloud.com/
• API keys: https://home.qwencloud.com/api-keys
• Developer docs: https://docs.qwencloud.com/developer-guides/getting-started/introduction
• Models: https://www.qwencloud.com/models
• Pricing: https://docs.qwencloud.com/developer-guides/getting-started/pricing

The QwenCloud team can provide validated configuration examples and documentation updates after the preferred path is confirmed.

QwenCloud contact: Jialing / QwenCloud Product Manager / https://github.com/evelyn-jialin-zhang

[chen-jiying]

I'd like to work on this.
I can create a Qwen/QwenCloud documentation page for aider.