Grok Imagine Image

AI Image Editing Model

Image $$ · 2¢

An image generation model by xAI designed to generate highly aesthetic images from text descriptions.

grok-imagine API OpenAI-compatible

Integrate Grok Imagine Image into your workflow via the Lumenfall OpenAI-compatible API to programmatically generate high-fidelity images and perform precise image edits. Use a single endpoint to access xAI's image generation technology using standard text-to-image parameters.

Base URL
https://api.lumenfall.ai/openai/v1
Model
grok-imagine-image

Code Examples

Image Edit

/v1/images/edits
curl -X POST \
  https://api.lumenfall.ai/openai/v1/images/edits \
  -H "Authorization: Bearer $LUMENFALL_API_KEY" \
  -F "model=grok-imagine-image" \
  -F "[email protected]" \
  -F "prompt=Add a starry night sky to this image" \
  -F "size=1024x1024"
# Response:
# { "created": 1234567890, "data": [{ "url": "https://...", "revised_prompt": "..." }] }

Parameter Reference

Required Supported Not available

Core Parameters

Parameter Type Description Modes
prompt string Required. Text prompt for image generation
T2I Edit

Size & Layout

Parameter Type Description Modes
size string Image dimensions as WxH pixels (e.g. "1024x1024") or aspect ratio (e.g. "16:9")
WxH determines both shape and scale (aspect_ratio and resolution are ignored when size is provided). W:H format is equivalent to aspect_ratio.
T2I Edit
aspect_ratio string Aspect ratio of the output image (e.g. "16:9", "1:1")
Controls shape independently of scale. Use with resolution to control both. If size is also provided, size takes precedence. Any ratio is accepted and mapped to the nearest supported value.
T2I Edit
resolution string Output resolution tier (e.g. "1K", "4K")
auto 1k 1K 2k 2K
Controls scale independently of shape. Higher tiers produce larger images and cost more. If size is also provided, size takes precedence for scale. Any tier is accepted and mapped to the nearest supported value.
T2I Edit
Output size aspect_ratio + resolution
Flexible
Auto "auto" Model chooses optimal dimensions
1K 13 sizes
Output size aspect_ratio + resolution
1508 × 696 "1508x696" or "19.5:9" + "1K"
1183 × 887 "1183x887" or "4:3" + "1K"
1527 × 687 "1527x687" or "20:9" + "1K"
696 × 1507 "696x1507" or "9:19.5" + "1K"
1024 × 1024 "1024x1024" or "1:1" + "1K"
887 × 1182 "887x1182" or "3:4" + "1K"
687 × 1526 "687x1526" or "9:20" + "1K"
724 × 1448 "724x1448" or "1:2" + "1K"
1448 × 724 "1448x724" or "2:1" + "1K"
836 × 1254 "836x1254" or "2:3" + "1K"
1254 × 836 "1254x836" or "3:2" + "1K"
768 × 1365 "768x1365" or "9:16" + "1K"
1365 × 768 "1365x768" or "16:9" + "1K"
2K 13 sizes
Output size aspect_ratio + resolution
1392 × 3015 "1392x3015" or "9:19.5" + "2K"
1774 × 2365 "1774x2365" or "3:4" + "2K"
2365 × 1774 "2365x1774" or "4:3" + "2K"
1374 × 3053 "1374x3053" or "9:20" + "2K"
3053 × 1374 "3053x1374" or "20:9" + "2K"
1536 × 2731 "1536x2731" or "9:16" + "2K"
2731 × 1536 "2731x1536" or "16:9" + "2K"
2048 × 2048 "2048x2048" or "1:1" + "2K"
1448 × 2896 "1448x2896" or "1:2" + "2K"
2896 × 1448 "2896x1448" or "2:1" + "2K"
1672 × 2508 "1672x2508" or "2:3" + "2K"
2508 × 1672 "2508x1672" or "3:2" + "2K"
3014 × 1391 "3014x1391" or "19.5:9" + "2K"

How these parameters work

size

Exact pixel dimensions

"1920x1080"
aspect_ratio

Shape only, default scale

"16:9"
resolution

Scale tier, preserves shape

"1K"

Priority when combined

size aspect_ratio + resolution aspect_ratio resolution

size is most specific and always wins. aspect_ratio and resolution control shape and scale independently.

How matching works

Shape matching – we pick the closest supported ratio. Ask for 7:1 on a model with 4:1 and 8:1, you get 8:1.
Scale matching – providers use different tier formats: K tiers (0.5K 1K 2K 4K) or megapixel tiers (0.25 1). If the exact tier isn't available, you get the nearest one.
Dimension clamping – if a model has pixel limits, we clamp dimensions to fit and keep the aspect ratio intact.

Media Inputs

Parameter Type Description Modes
image file Required. Input image(s) to edit
Supports PNG, JPEG, WebP.
T2I Edit

Output & Format

Parameter Type Description Modes
response_format xai string Response format for generated images. If omitted, xAI returns URLs.
b64_json url
Default: "url"
T2I Edit
output_format string Output image format
png jpeg gif webp avif
Gateway converts to requested format if provider doesn't support it natively.
T2I Edit
output_compression integer Compression level for lossy formats (JPEG, WebP, AVIF)
T2I Edit
n integer Number of images to generate
Default: 1
Gateway generates multiple images in parallel even if provider only supports 1.
T2I Edit

Additional Parameters

Provider-specific passthrough fields, available only when the request is routed to the listed provider.

Parameter Type Description Modes
fal
sync_mode boolean If `True`, the media will be returned as a data URI and the output data won't be available in the request history.
T2I Edit
xai
images array Optional list of input images for multi-reference image editing. This field cannot be set together with `image`.
T2I Edit
storage_options object Options for storing generated output in the xAI Files API.
T2I Edit
user ["string", "null"] Unique end-user identifier that can help xAI monitor and detect abuse.
T2I Edit

Parameter Normalization

How we handle parameters across different providers

Not every provider speaks the same language. When you send a parameter, we handle it in one of four ways depending on what the model supports:

Behavior What happens Example
passthrough Sent as-is to the provider style, quality
renamed Same value, mapped to the field name the provider expects prompt
converted Transformed to the provider's native format size
emulated Works even if the provider has no concept of it n, response_format

Parameters we don't recognize pass straight through to the upstream API, so provider-specific options still work.