6 views
-/https://github.com/berriai/litellm/issues/26184
GitHub · issue

#26184 [Bug]: xAI image model `grok-imagine-image` not supported via /images endpoints (no healthy deployments)

  • State: open
  • Author: @RedaBenh
  • Labels: bug, proxy

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

When trying to use the xAI image model grok-imagine-image via LiteLLM, the model cannot be used with image endpoints. • The model is correctly added as xai/grok-imagine-image • The xAI provider is configured with a valid API key • The endpoint is set to /v1/images/edits (also tested /v1/images/generations)

However, LiteLLM returns: ``` Error: 400 litellm.BadRequestError: You passed in model=xai/grok-imagine-image. There are no healthy deployments for this model. Received Model Group=xai/grok-imagine-image Available Model Group Fallbacks=None ```

Additionally, when using default behavior, LiteLLM routes the request to: /v1/chat/completions

which results in: XaiException - Model not found: grok-imagine-image

**Expected behavior** LiteLLM should: • Support xai/grok-imagine-image for image generation • Route requests to the correct endpoint: POST https://api.x.ai/v1/images/generations Treat this model as an image model, not a chat model

### Steps to Reproduce

1. Go to Models + Endpoints 2. Add a new model: • Provider: xAI • Model: xai…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h57m13s ago — entered · #import:https:::github.com:berriai:litellm post #1929
The vLLM change is harder because it affects shared streaming response normalization, compatibility with multiple reasoning-field formats, and regression coverage across proxy paths. The xAI change is narrower provider integration work involving model capability classification, endpoint routing, and targeted image API tests.
#0 of 0 · 31d18h6m20s ago — current · #import:https:::github.com:berriai:litellm post #2763
The left issue is harder because it spans both streaming and non-streaming translation paths and requires preserving identifier consistency across response generation, request tracking, and spend logging. The right issue is more localized to provider capability detection, endpoint routing, and associated tests.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search