fix: use correct ZAI_API_KEY for Zhipu/GLM models
LiteLLM's zai provider reads ZAI_API_KEY, not ZHIPUAI_API_KEY. This fixes authentication errors when using Zhipu/GLM models.
This commit is contained in:
parent
7965af723c
commit
fea4a6bba8
@ -52,7 +52,7 @@ class LiteLLMProvider(LLMProvider):
|
||||
elif "gemini" in default_model.lower():
|
||||
os.environ.setdefault("GEMINI_API_KEY", api_key)
|
||||
elif "zhipu" in default_model or "glm" in default_model or "zai" in default_model:
|
||||
os.environ.setdefault("ZHIPUAI_API_KEY", api_key)
|
||||
os.environ.setdefault("ZAI_API_KEY", api_key)
|
||||
elif "groq" in default_model:
|
||||
os.environ.setdefault("GROQ_API_KEY", api_key)
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user