[FEATURE] Add an official QwenCloud configuration path for CrewAI users

[evelyn-jialin-zhang]

Feature Area

Core functionality

Is your feature request related to a an existing bug? Please link it here.

N/A — this is a provider discovery and configuration enhancement.

Describe the solution you'd like

QwenCloud provides Qwen models through OpenAI- and Anthropic-compatible APIs. Please confirm whether CrewAI should expose QwenCloud through a native provider path or through the project's current compatible-provider documentation. The selected path should preserve existing Qwen/DashScope configurations, point users to the current official API-key, model, and pricing pages, and make the runtime dependency clear rather than assuming LiteLLM is always used.

Describe alternatives you've considered

Relying only on generic OpenAI-compatible configuration is possible but hard to discover and does not clarify which provider implementation is maintained. Treating LiteLLM as the only path would be inaccurate for versions that use native provider SDKs.

Additional context

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, recommended models, and detailed specifications after the preferred path is confirmed.

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

Willingness to Contribute

I could provide more detailed specifications