Question: preferred migration path from existing Alibaba provider IDs to QwenCloud

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.

models.dev already contains an Alibaba provider family covering pay-as-you-go, Token Plan, Coding Plan, and China/international variants, including:

• alibaba
• alibaba-cn
• alibaba-token-plan and alibaba-token-plan-cn
• alibaba-coding-plan and alibaba-coding-plan-cn

Keeping this upstream data accurate will let OpenCode and other consumers discover the current QwenCloud brand without breaking existing provider references.

Before preparing a PR, could the maintainers advise which migration path is preferred?

1. Update user-visible names, documentation links, and branding to QwenCloud while preserving the existing provider IDs for compatibility;
2. Add new qwencloud* provider entries or aliases while retaining the existing Alibaba IDs; or
3. Use another migration structure recommended by the maintainers.

Once the direction is confirmed, we can prepare a focused PR with the required provider TOML changes, a currentColor SVG logo, and any model metadata updates requested by the maintainers.

Current provider examples

• https://github.com/anomalyco/models.dev/blob/dev/providers/alibaba/provider.toml
• https://github.com/anomalyco/models.dev/blob/dev/providers/alibaba-token-plan/provider.toml

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

QwenCloud contact: Jialin / QwenCloud ecosystem integration / https://github.com/evelyn-jialin-zhang

Start with providers/alibaba/provider.toml and providers/alibaba-token-plan/provider.toml, then wait for maintainers to choose the compatibility and migration structure. Done means applying that decision consistently to the provider TOML, currentColor SVG logo, and requested model metadata without breaking existing provider references.