Both Alibaba Token Plan providers still point at the region-scoped maas.aliyuncs.com base URLs:
providers/alibaba-token-plan/provider.toml: https://token-plan.ap-southeast-1.maas.aliyuncs.com/compatible-mode/v1providers/alibaba-token-plan-cn/provider.toml: https://token-plan.cn-beijing.maas.aliyuncs.com/compatible-mode/v1
The vendor replaced those on its own Token Plan documentation on 2026-09-23. The quickstart, FAQ and best-practice pages on both the international and mainland China sites now give brand-scoped canonical hosts instead:
- International:
https://token-plan.maas.qwencloudapi.com/compatible-mode/v1
- Mainland China:
https://token-plan.maas.qianwenaiapi.com/compatible-mode/v1
That matches the branding split described in #4296, where qwencloud serves markets outside mainland China and the Qwen AI Platform brand serves mainland China.
What I checked
On 2026-09-24, with a live Token Plan key, GET /compatible-mode/v1/models against both the old and the new international host returned HTTP 200 with a byte-identical list of model ids. The new host is the same service, not a different catalogue.
Without a key both hosts return the same 401, so the new host is in service and behind the same auth gate rather than being a documentation typo.
The old hosts still answer today. The concern is that they are no longer the documented ones, so they are the pair likely to be retired, and downstream consumers reading the api field would break at that point with no warning.
Suggested fix
Change the api line in each of the two provider TOMLs. Two lines, no model rows touched.
This is deliberately narrower than the provider ID and display-name migration under discussion in #4296. The base URL change is a concrete, verifiable fact today and does not depend on how that naming question is resolved.
Both Alibaba Token Plan providers still point at the region-scoped
maas.aliyuncs.combase URLs:providers/alibaba-token-plan/provider.toml:https://token-plan.ap-southeast-1.maas.aliyuncs.com/compatible-mode/v1providers/alibaba-token-plan-cn/provider.toml:https://token-plan.cn-beijing.maas.aliyuncs.com/compatible-mode/v1The vendor replaced those on its own Token Plan documentation on 2026-09-23. The quickstart, FAQ and best-practice pages on both the international and mainland China sites now give brand-scoped canonical hosts instead:
https://token-plan.maas.qwencloudapi.com/compatible-mode/v1https://token-plan.maas.qianwenaiapi.com/compatible-mode/v1That matches the branding split described in #4296, where
qwencloudserves markets outside mainland China and the Qwen AI Platform brand serves mainland China.What I checked
On 2026-09-24, with a live Token Plan key,
GET /compatible-mode/v1/modelsagainst both the old and the new international host returned HTTP 200 with a byte-identical list of model ids. The new host is the same service, not a different catalogue.Without a key both hosts return the same 401, so the new host is in service and behind the same auth gate rather than being a documentation typo.
The old hosts still answer today. The concern is that they are no longer the documented ones, so they are the pair likely to be retired, and downstream consumers reading the
apifield would break at that point with no warning.Suggested fix
Change the
apiline in each of the two provider TOMLs. Two lines, no model rows touched.This is deliberately narrower than the provider ID and display-name migration under discussion in #4296. The base URL change is a concrete, verifiable fact today and does not depend on how that naming question is resolved.