What this error usually means
Diagnose Zhipu AI (GLM) model not found (404) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.
- Provider: Zhipu AI (GLM)
- Error type: model not found
- Status code: 404
Key error diagnosis
Zhipu AI (GLM) | model not found
Diagnose Zhipu AI (GLM) model not found (404) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.
Provider
Zhipu AI (GLM)
China provider route
Error type
model not found
high
Status code
404
model-not-found
Sample models
13
GLM 4 32B · GLM 4.5 · GLM 4.5 Air
Error route summary
Error type
model-not-found
high
Provider
Zhipu AI (GLM)
Status code
404
Read-only check. Detection data burns after 5 minutes.
Read-only check. Detection data burns after 5 minutes.
How to prove it during checking
Read-only check. Detection data burns after 5 minutes.
- Run read-only identity first: confirm whether the key really belongs to Zhipu AI (GLM), not just a compatible protocol.
- Then list models or run a lightweight probe: check whether models like GLM 4 32B · GLM 4.5 · GLM 4.5 Air are visible and return stable evidence.
- Finally record 404, error body, latency, egress IP, and reproducibility to separate balance, permission, route, or upstream issues.
Next action
model not found should not only show failed. The console should return the next move: refill balance, change Base URL, switch model, add permission, change egress IP, hold listing, or monitor.
- Read-only check. Detection data burns after 5 minutes.
- China provider route
- GLM 4 32B · GLM 4.5 · GLM 4.5 Air