xAI
grok-2-latest model retirement
Stopped workingSubscribe to xAIShare
Calls to the model grok-2-latest on xAI stopped working on October 14, 2026.
The error you get
What xAI answers a call to grok-2-latest once the model is gone, as recorded from real responses:
{"code":"invalid-argument","error":"Model not found: grok-2-latest"}What to use instead of grok-2-latest
Move to grok-4.3. Our suggestion, not xAI's - xAI removed the model's page rather than publishing a migration target for it.
Facts
- API
- xAI
api.x.ai - Model
grok-2-latest- Kind
- Model retirement
- Takes effect
- October 14, 2026
- Calls after that day
- Fail
- Source
- models.dev
- Last updated
- Verified
- , against xAI's own pages
Questions
When does grok-2-latest shut down?
Calls to the model grok-2-latest on xAI stopped working on October 14, 2026.
What happens to calls after October 14, 2026?
They have failed since October 14, 2026.
What error does grok-2-latest return once it is shut down?
xAI answers HTTP 400: "Model not found: grok-2-latest". Send another model to fix it.
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.
More from xAI 10
-
grok-3Model retirement Redirected -
grok-4Model retirement Stopped working -
grok-4-0709Model retirement Redirected -
grok-2Model retirement Stopped working -
grok-2-1212Model retirement Stopped working -
grok-2-image-1212Model retirement Stopped working -
grok-2-vision-1212Model retirement Stopped working -
grok-3-miniModel retirement Stopped working -
grok-betaModel retirement Stopped working -
grok-vision-betaModel 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.