Vertex AI
glm-5-maas model retirement
Stopped workingSubscribe to Vertex AIShare
Google retired model glm-5-maas on October 21, 2026, following its deprecation on July 21, 2026. Calls to model glm-5-maas fail since that day. This shutdown directly affects any requests sent to this specific model.
The error you get
What Vertex AI answers a call to glm-5-maas once the model is gone, as recorded from real responses:
{"error":{"code":404,"message":"Publisher model `projects/{project}/locations/{region}/publishers/google/models/glm-5-maas` was not found or your project does not have access to it. Ensure you are using a valid model name and that the model is available in the specified region.","status":"NOT_FOUND"}}What to use instead of glm-5-maas
Google recommends to self-deploy GLM 5 on Model Garden as the replacement.
In Vertex AI's words
Model ID: glm-5-maas; Deprecation date: July 21, 2026; Retirement date: October 21, 2026; Self-deploy alternative: Self-deploy GLM 5 on Model Garden
Facts
- API
- Vertex AI
aiplatform.googleapis.com - Model
glm-5-maas- Released
- February 12, 2026 (models.dev)
- Kind
- Model retirement
- Announced
- July 21, 2026
- Takes effect
- October 21, 2026
- Calls after that day
- Fail
- Source
- Deprecations page
- Last updated
- Verified
- , against Vertex AI's own pages
Questions
When does glm-5-maas shut down?
Calls to the model glm-5-maas on Vertex AI stopped working on October 21, 2026.
What happens to calls after October 21, 2026?
They have failed since October 21, 2026.
What error does glm-5-maas return once it is shut down?
Vertex AI answers HTTP 404: "Publisher model `projects/{project}/locations/{region}/publishers/google/models/glm-5-maas` was not found or your project does not have access to it. Ensure you are using a valid model name and that the model is available in the specified region.". Send another model to fix it.
When was glm-5-maas released?
glm-5-maas was released on February 12, 2026, according to models.dev.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
glm-5-maas on other APIs 1
-
No date
Vertex AI
zai-org/glm-5-maasModel retirement Deprecated, no date
More from Vertex AI 10
-
deepseek-ocr-maasModel retirement Stopped working -
deepseek-r1-0528-maasModel retirement Stopped working -
deepseek-v3.1-maasModel retirement Stopped working -
deepseek-v3.2-maasModel retirement Stopped working -
glm-4.7-maasModel retirement Stopped working -
gpt-oss-20b-maasModel retirement Stopped working -
kimi-k2-thinking-maasModel retirement Stopped working -
llama-3.3-70b-instruct-maasModel retirement Stopped working -
minimax-m2-maasModel retirement Stopped working -
multilingual-e5-large-instruct-maasModel retirement Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.