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

TL;DR

An international key goes with https://dashscope-intl.aliyuncs.com/compatible-mode and a Beijing key with https://dashscope.aliyuncs.com/compatible-mode.

The error

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

Fix

1. An international key goes with https://dashscope-intl.aliyuncs.com/compatible-mode and a Beijing key with https://dashscope.aliyuncs.com/compatible-mode. Expected: you can confirm this matches your situation.

2. Re-run the original operation and confirm the error is gone. Expected: no error, normal output.

When to use

• You hit this exact error with DashScope.
• The symptom matches: match the API key region to the base URL or get 401 Invalid API-key.

When NOT to use

• A different error message from DashScope; the cause here is specific to this error.
• Unrelated DashScope issues (different feature, different failure).
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against DashScope. Source: https://github.com/sadeghhp/33pol/blob/HEAD/docs/integrations.md.

Variant phrasings

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

Why it happens

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

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Source

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

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