Skip to content
modeldeprecations.dev
xAI grok-imagine-image-pro

Grok Imagine Image Pro (xAI)

Retired

Yes — Grok Imagine Image Pro is retired. xAI shut it down on May 15, 2026; API requests to it now fail. The recommended replacement is Grok Imagine Image Quality.

The premium tier of xAI's image generator, retired in the same wave as seven text models and renamed rather than replaced. Nothing about the model changed on 15 May 2026; the word "pro" was simply swapped for "quality" in the id.

The facts

Provider xAI
Model id grok-imagine-image-pro
Released
Deprecated date not published
Shutdown May 15, 2026 · 80 days ago
Status Retired
Last verified August 3, 2026

What to use instead

xAI Grok Imagine Image Quality grok-imagine-image-quality Provider-recommended Active

A rename. Unlike the text models in this wave there is no price or context change to plan around - just the new string.

What parameters grok-imagine-image-quality accepts on modelparams.dev

Change the id

In most cases the migration is one string. Check the parameter differences before you ship — newer models drop older sampling knobs more often than they add them.

- "model": "grok-imagine-image-pro"
+ "model": "grok-imagine-image-quality"

Frequently asked questions

When did xAI Grok Imagine Image Pro shut down?
xAI Grok Imagine Image Pro shut down on May 15, 2026. API requests to it fail from that date onward.
What replaces xAI Grok Imagine Image Pro?
xAI recommends Grok Imagine Image Quality (`grok-imagine-image-quality`) as the replacement for xAI Grok Imagine Image Pro. A rename. Unlike the text models in this wave there is no price or context change to plan around - just the new string.
Is xAI Grok Imagine Image Pro still available?
No. xAI Grok Imagine Image Pro is retired and no longer served — it was shut down on May 15, 2026. Calls to it return an error.
How do I migrate from xAI Grok Imagine Image Pro to grok-imagine-image-quality?
Swap the model id in your API call: replace "grok-imagine-image-pro" with "grok-imagine-image-quality". A rename. Unlike the text models in this wave there is no price or context change to plan around - just the new string.

Sources

Found something wrong? The data is one YAML file — edit it on GitHub.

This page, for machines

Drop the badge in a README so it turns red the day this model is retired:

[![grok-imagine-image-pro](https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/xai/grok-imagine-image-pro.json)](https://modeldeprecations.dev/xai/grok-imagine-image-pro)

Other xAI models

All xAI deprecations →

How to use this site

The full guide, in Markdown. Copy it and hand it to a coding agent verbatim.

# How to use modeldeprecations.dev

[modeldeprecations.dev](https://modeldeprecations.dev) answers one question per model: is it deprecated,
when does it shut down, and what replaces it. Every date on the site is cited to the
provider's own documentation, with the date we last checked it.

Three lifecycle states are used, matching the providers' own vocabulary:

- **active** — still supported, no deprecation announced.
- **deprecated** — the provider has announced it is going away. It still answers requests.
- **retired** — API access is gone. Requests fail.

A model can be active *and* carry a shutdown date: Anthropic publishes a
"not sooner than" date and Google publishes an earliest shutdown date for models
that are current and fully supported. Those are reported as scheduled shutdowns,
not deprecations, because that is what the provider actually committed to.

## Check one model

```bash
curl https://modeldeprecations.dev/api/v1/models/openai/gpt-4-32k.json
```

Or fetch the page as Markdown, which includes the answer, the dates and the sources:

```bash
curl https://modeldeprecations.dev/openai/gpt-4-32k.md
```

## Full catalog

```bash
curl https://modeldeprecations.dev/api/v1/models.json
```

Ids are `provider/model`. Dated snapshots (`gpt-4-32k-0613`) are listed as aliases of
their canonical entry rather than as separate records.

Each entry carries `computed_status`, the lifecycle state recomputed against the build
date — so a model whose shutdown has passed reads `retired` without anyone editing data.

## Badges

A shields.io endpoint per model, for READMEs that should go red when a model dies:

```
https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/openai/gpt-4-32k.json
```

## Calendar and changelog

- Subscribe to every shutdown date: https://modeldeprecations.dev/calendar.ics
- Changelog RSS: https://modeldeprecations.dev/changelog.xml

## JSON Schema

```bash
curl https://modeldeprecations.dev/api/v1/schema.json
```

## Contribute

Data lives in YAML under `models/{provider}/{model}.yaml` in the
[GitHub repo](https://github.com/mnfst/modeldeprecations.dev). Every lifecycle date needs a source URL; CI rejects a
date without one. Open a PR.

## For agents

- Machine-readable overview: https://modeldeprecations.dev/llms.txt
- This guide plus every model inline: https://modeldeprecations.dev/llms-full.txt
- Any page also exists as Markdown: append `.md` to a model URL.
- In a browser, this site registers a **WebMCP** tool on `navigator.modelContext`:
  `check_model_deprecation`, `list_shutdowns`, `find_replacement`, and `get_usage_guide`.
- Parameters each model accepts are catalogued on the sibling site, https://modelparams.dev.