API compatibility - 5 documented limits
Alibaba Cloud Model Studio (Qwen) API compatibility
Alibaba Cloud Model Studio documents an OpenAI-compatible API at https://{WorkspaceId}.ap-southeast-1.maas.aliyuncs.com/compatible-mode/v1 (chat/completions). Its Anthropic-compatible base URL, the value for ANTHROPIC_BASE_URL, is https://{WorkspaceId}.ap-southeast-1.maas.aliyuncs.com/apps/anthropic. The docs list 5 limitations: 2 for the OpenAI-compatible layer and 3 for the Anthropic-compatible layer.
Verified against Alibaba Cloud Model Studio's own documentation. Not documented means the docs read that day do not say; it never means No.
Compare every provider in the API compatibility matrix.
OpenAI-compatible API
Supportedhttps://{WorkspaceId}.ap-southeast-1.maas.aliyuncs.com/compatible-mode/v1- Endpoints
- chat/completions
- Auth
- Authorization: Bearer $DASHSCOPE_API_KEY
- Regional and alternate URLs
- Singapore
https:// {WorkspaceId}. ap-southeast-1. maas. aliyuncs. com/ compatible-mode/ v1 - US Virginia
https:// {WorkspaceId}. us-east-1. maas. aliyuncs. com/ compatible-mode/ v1 - Hong Kong
https:// {WorkspaceId}. cn-hongkong. maas. aliyuncs. com/ compatible-mode/ v1 - Tokyo
https:// {WorkspaceId}. ap-northeast-1. maas. aliyuncs. com/ compatible-mode/ v1
- Singapore
- Notes
- Singapore is the international default used in every SDK example. API keys are region-bound: a key from another region returns 401 invalid_api_key. Workspace-specific domains replace the legacy dashscope domains, which 'remain available'. The OpenAI page's BASE_URL block lists Beijing with the ap-southeast-1 host, which contradicts its own migration note (cn-beijing), so the Beijing base URL is left out here until Alibaba's docs agree. Legacy domains (dashscope-intl.aliyuncs.com, dashscope.aliyuncs.com, cn-hongkong.dashscope.aliyuncs.com) still work per the migration note. Supported models via this interface include Qwen, Qwen-VL, Qwen-Coder, Qwen-Omni, Qwen-Math, DeepSeek, Kimi, GLM, MiniMax.
From the docs
The Qwen models on Model Studio support OpenAI compatible interfaces. You can migrate your existing OpenAI code to Model Studio by changing only the API key, base URL, and model name. ... Singapore: https://{WorkspaceId}.ap-southeast-1.maas.aliyuncs.com/compatible-mode/v1 Virginia: https://{WorkspaceId}.us-east-1.maas.aliyuncs.com/compatible-mode/v1 Beijing: https://{WorkspaceId}.ap-southeast-1.maas.aliyuncs.com/compatible-mode/v1 Hong Kong (China): https://{WorkspaceId}.cn-hongkong.maas.aliyuncs.com/compatible-mode/v1 Japan (Tokyo): https://{WorkspaceId}.ap-northeast-1.maas.aliyuncs.com/compatible-mode/v1
Anthropic-compatible API
Supportedhttps://{WorkspaceId}.ap-southeast-1.maas.aliyuncs.com/apps/anthropic- Auth
- x-api-key or Authorization: Bearer (API reference); Claude Code guide uses ANTHROPIC_AUTH_TOKEN
- Regional and alternate URLs
- Singapore
https:// {WorkspaceId}. ap-southeast-1. maas. aliyuncs. com/ apps/ anthropic - Beijing
https:// {WorkspaceId}. cn-beijing. maas. aliyuncs. com/ apps/ anthropic - Frankfurt
https:// {WorkspaceId}. eu-central-1. maas. aliyuncs. com/ apps/ anthropic - US Virginia
https:// {WorkspaceId}. us-east-1. maas. aliyuncs. com/ apps/ anthropic - Tokyo
https:// {WorkspaceId}. ap-northeast-1. maas. aliyuncs. com/ apps/ anthropic - Coding Plan
https:// coding-intl. dashscope. aliyuncs. com/ apps/ anthropic - Token Plan Personal
https:// token-plan. ap-southeast-1. maas. aliyuncs. com/ apps/ anthropic
- Singapore
- Notes
- Endpoint is POST {base}/v1/messages. Coding Plan and Token Plan keys use their own base URLs (from the Claude Code guide).
From the docs
SDKbase_url:https://{WorkspaceId}.ap-southeast-1.maas.aliyuncs.com/apps/anthropic... Authentication: Pass your Model Studio API key in either thex-api-keyheader or theAuthorization: Bearerheader.
Documented limitations
Parameters, content types and features Alibaba Cloud Model Studio (Qwen)'s docs say its compatibility layers ignore, reject or change, each with the line it comes from. A layer with nothing listed may still differ in ways the docs do not spell out.
OpenAI-compatible layer2
Qwen-Audio not available via OpenAI-compatible protocol
Qwen-Audio does not support the OpenAI compatible protocol. Use the DashScope protocol instead.
www.alibabacloud.com/help/en/model-studio/compatibility-of-openai-with-dashscope system_fingerprint not supported
system_fingerprint | string | The configuration version used by the model runtime. Currently not supported; returns an empty string.
www.alibabacloud.com/help/en/model-studio/compatibility-of-openai-with-dashscope
Anthropic-compatible layer3
glm-5.3 ignores thinking.budget_tokens
glm-5.3 ignores the
thinking.budget_tokensparameter.www.alibabacloud.com/help/en/model-studio/anthropic-api-messages effort max/high mapped to xhigh
max, high are mapped to xhigh.
www.alibabacloud.com/help/en/model-studio/anthropic-api-messages structured outputs: schema not enforced outside qwen3.8/qwen3.7/deepseek/glm
For all other models, schema field constraints are not enforced ... the API automatically falls back to a plain JSON mode (only guaranteeing that the output is a valid JSON string).
www.alibabacloud.com/help/en/model-studio/anthropic-api-messages
More on Alibaba Cloud Model Studio (Qwen)
Newsletter
Know when a provider changes its API
One email per week. New models, new endpoints and the compatibility changes that break a base URL, and what they mean for your stack.