-
Notifications
You must be signed in to change notification settings - Fork 619
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How do I connect to DeepSeek supported by Tencent Cloud? #93
Comments
It seems the LiteLLM (the library we currently use for LLM clients) does not support Tencent Cloud. We might consider adding the support if there is enough interests. Potentially Ollama with larger-sized open sourced model is the best option for you at the moment? |
感谢!看起来是腾讯云可以和openAI的API兼容,但没法和LiteLLM的API兼容。我看看有没有什么好的办法hack一下这个。我可能打算开一个单独的branch来对这个support。 |
oh,你会中文,太好了,我就不用翻译又怕英文用的不是专业术语表达不清楚需求了。 是的,在上一个版本,还可以通过环境变量导入 OPENAI_BASE_URL="https://api.deepseek.com/v1" 和 OPENAI_BASE_URL="https://api.lkeap.cloud.tencent.com/v1" 来分别连接 deepseek 和 腾讯云提供的deepseek的, 升级到0.1.5之后,就是用新的LiteLLM 之后,deepseek还可以连,但 腾讯云的deepseek,我也仔细看了 https://docs.litellm.ai/docs/providers 没有找到合适的兼容方式,也乱尝试填过以下: 好像 我觉得那个 api_base:https://api.lkeap.cloud.tencent.com/v1` 并没有正确生效,按我的理解,它应该去连接请求这个地址。而不是继续请求 api.deepseek.com。 |
hello! 我们刚在dev branch更新了一下openai API的方法,这个方法和0.1.4版本的API一样,你可以尝试使用provider=openai, 然后输入api_base, api_key, model来连接。 现在dev branch还没有更新到pypi上,需要自己在local build一下:https://github.com/microsoft/data-formulator/blob/dev/DEVELOPMENT.md |
这个fix已经merge到新的release里面了,可以试一试: |
连接填入项: endpoint :openai api_key:腾讯云处申请的api_key model: deepseek-r1 或 deepseek-v3 |
I want to connect to deepseek-v3 supported by Tencent Cloud
I refer to this https://cloud.tencent.com/document/product/1772/115969
and this https://docs.litellm.ai/docs/providers/openai_compatible
How do I configure this model connection?
I can already connect directly to deepseek,Just insufficient balance。
But how do I connect to DeepSeek supported by Tencent Cloud? How do I configure my endpoint, model, and api_base correctly?
The text was updated successfully, but these errors were encountered: