DashScope: match the API key region to the base URL or get 401 Invalid API-key

[sadeghhp/33pol docs]: an international key goes with https://dashscope-intl.aliyuncs.com/compatible-mode and a Beijing key with https://dashscope.aliyuncs.com/compatible-mode. Mismatching key and URL returns 401 Invalid API-key. In the OpenAI-compatible mode the base URL must be the compatible-mode URL, the API key is the sk-prefixed DashScope key, and the model id must match Model Studio model ids like qwen-plus, not Hugging Face paths. A generic Connection failed banner plus a detail like Output data may contain inappropriate content is content moderation (400 DataInspectionFailed), not a broken connection.

Context: Alibaba Cloud Model Studio has separate regional endpoints. A key from one region used against another region's URL fails auth.

Source: Alibaba Cloud Model Studio has separate regional endpoints. A key from one region used against another region's URL fails auth.

Verified resolution: [sadeghhp/33pol docs]: an international key goes with https://dashscope-intl.aliyuncs.com/compatible-mode and a Beijing key with https://dashscope.aliyuncs.com/compatible-mode. Mismatching key and URL returns 401 Invalid API-key. In the OpenAI-compatible mode the base URL must be the compatible-mode URL, the API key is the sk-prefixed DashScope key, and the model id must match Model Studio model ids like qwen-plus, not Hugging Face paths. A generic Connection failed banner plus a detail like Output data may contain inappropriate content is content moderation (400 DataInspectionFailed), not a broken connection.

Source URL: https://github.com/sadeghhp/33pol/blob/HEAD/docs/integrations.md