mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-22 01:55:27 -04:00
Unable to use international Model Studio Embedding API in Dify #505
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @davidygp on GitHub (Aug 1, 2025).
Self Checks
Dify version
1.71
Cloud or Self Hosted
Cloud
Steps to reproduce
Issue: Invalid API key when using international Model Studio in Dify Knowledge Base
API key is taken from Model Studio international console:

Key works when calling it directly with the international endpoint:

text-embedding-v3 is selected:

I believe it's because the endpoint is pointing towards the domestic Bailian embedding endpoint.
-> #NOTE: the URL pointing to the wrong endpoint was also there for the Tongyi plugin (we had to provide a button to select international or domestic endponts.)
-> #NOTE2: haven't been able to test any re-ranker model, might have the same issue
✔️ Expected Behavior
Expected it to smoothly call the embedding API and embed the chunks into the knowledge base.
(I tested it with an API key created from domestic Bailian and there's no issue. But it doesn't work with API key from international Model Studio.)
❌ Actual Behavior
@crazywoola commented on GitHub (Aug 1, 2025):
Please confirm your API key is accquired from the international aliyun platform.
@davidygp commented on GitHub (Aug 3, 2025):
Yes it was, see the above screenshot showing it comes from International Model Studio.
I also used the following endpoint in the local vscode screenshot above:
https://dashscope-intl.aliyuncs.com/compatible-mode/v1
It comes from this documentation:
https://www.alibabacloud.com/help/en/model-studio/text-embedding-synchronous-api
@dosubot[bot] commented on GitHub (Aug 20, 2025):
Hi, @davidygp. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.
Issue Summary:
Next Steps:
Thank you for your understanding and contribution!