Issue Station
Sign In
Tools hereToolbox

litellm - ✅(Solved) Fix Bug: Z.AI (zai) provider missing from UI dropdown despite being in /public/providers API [1 pull requests, 1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#25482•Fetched 2026-04-11 06:14:04
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
syabrosyabro
Participants
guanyu-gerry-taoguanyu-gerry-taosyabrosyabro
Timeline (top)
commented ×1cross-referenced ×1labeled ×1referenced ×1

Root Cause

The UI frontend appears to hardcode the provider list rather than fetching it from /public/providers endpoint. New providers added to the backend don't appear in the UI automatically.

Fix Action

Fixed

PR fix notes

PR #25485: feat: add Z.AI provider to UI dashboard

Description (problem / solution / changelog)

Relevant issues

Fixes #25482

Pre-Submission checklist

  • I have Added testing in the tests/test_litellm/ directory, Adding at least 1 test is a hard requirement - see details
  • My PR passes all unit tests on make test-unit
  • My PR's scope is as isolated as possible, it only solves 1 specific problem
  • I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

Type

New Feature

Changes

Summary

Registers Z.AI (Zhipu AI) in the LiteLLM dashboard's provider dropdown so users can configure Z.AI models from the UI without editing config.yaml. Backend support for the zai/ provider prefix already exists in litellm/llms/zai/; this PR only adds the UI-layer registration.

Follows the pattern established by the MiniMax provider PR #18496.

What was added

1. Backend metadata (provider_create_fields.json)

  • Added ZAI provider entry with:
    • api_key — required password field. Tooltip links to https://z.ai/manage-apikey/apikey-list (where users create API keys).
    • api_base — optional text field. Default: https://api.z.ai/api/paas/v4. Tooltip also documents the alternative GLM Coding Plan endpoint https://api.z.ai/api/coding/paas/v4 for Coding Plan subscribers (per the Z.AI API reference).
    • default_model_placeholder: zai/glm-4.6 (Z.AI's documented flagship model).

2. Frontend (provider_info_helpers.tsx)

  • Added ZAI = "Z.AI" to the Providers enum.
  • Registered ZAI: "zai" in provider_map.
  • Added [Providers.ZAI]: \${asset_logos_folder}zai.svg`inproviderLogoMap`.

3. Assets

Files modified

  • litellm/proxy/public_endpoints/provider_create_fields.json (+28 lines)
  • ui/litellm-dashboard/src/components/provider_info_helpers.tsx (+3 lines)
  • ui/litellm-dashboard/public/assets/logos/zai.svg (new, 319 bytes)

Verification

  • npm run build passes (TypeScript compile + Next.js static page generation succeed).
  • Both modified files pass npx prettier --check.
  • Dev server confirmed the logo file is served correctly at /assets/logos/zai.svg.
  • No backend code is modified; existing zai/ provider routing in litellm/llms/zai/ is unaffected.

Changed files

  • litellm/proxy/public_endpoints/provider_create_fields.json (modified, +28/-0)
  • ui/litellm-dashboard/public/assets/logos/zai.svg (added, +1/-0)
  • ui/litellm-dashboard/src/components/provider_info_helpers.tsx (modified, +3/-0)
RAW_BUFFERClick to expand / collapse

Bug

The zai (Z.AI / Zhipu AI) provider is missing from the UI provider dropdown when adding a new model, even though:

  1. Backend API /public/providers returns zai in the list
  2. provider_endpoints_support.json includes zai with full endpoint support
  3. Backend supports zai/glm-5 model routing correctly
  4. LiteLLM docs have a dedicated page: https://docs.litellm.ai/docs/providers/zai
<img width="1970" height="830" alt="Image" src="https://github.com/user-attachments/assets/8b628dd6-a662-4ebf-bd39-30e9ac0c451b" />

Repro

  1. LiteLLM v1.83.4, litellm-proxy-extras v0.4.65
  2. Go to UI → Models → Add Model
  3. Open "Select a provider" dropdown
  4. Search for "zai" or "z" — not found
  5. Scroll through entire list — zai is not present

Expected

zai should appear in the dropdown like other providers (anthropic, openai, gemini, etc.), since it's returned by /public/providers API.

Root cause

The UI frontend appears to hardcode the provider list rather than fetching it from /public/providers endpoint. New providers added to the backend don't appear in the UI automatically.

Environment

  • LiteLLM: v1.83.4
  • litellm-proxy-extras: v0.4.65
  • Installed via pip/uv (not Docker)

extent analysis

TL;DR

Update the UI frontend to fetch the provider list from the /public/providers endpoint instead of hardcoding it.

Guidance

  • Verify that the /public/providers endpoint is correctly returning the zai provider by checking the API response.
  • Check the UI frontend code for any hardcoded provider lists and update them to fetch from the /public/providers endpoint.
  • Test the UI after updating the code to ensure that the zai provider appears in the dropdown list.
  • Consider implementing a caching mechanism to ensure that the provider list is updated in real-time.

Example

No code snippet is provided as it is not explicitly stated in the issue, but an example of how to fetch the provider list from the endpoint might look like a simple API call to /public/providers and then populating the dropdown list with the response.

Notes

The issue seems to be specific to the UI frontend not updating the provider list dynamically. The backend API and other components appear to be working correctly.

Recommendation

Apply workaround: Update the UI frontend code to fetch the provider list from the /public/providers endpoint. This is because the issue is specific to the UI frontend and updating the code will ensure that new providers are added dynamically.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#configuration error#environment variable#network issue#logging issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING