Grok Imagine Image 2.0 is xAI’s image-generation and editing model. It takes a written description, or a description together with source images, and returns an image result. The producer’s named 2.0 profile covers creating a scene, changing an existing image, combining subjects from references and transforming visual style. Start by choosing whether you need a new composition or a specific change to material you already have.
Describe the main subject, its setting, the composition, lighting and visual treatment. Identify what the viewer should notice first and where the image will be used. For a product concept, an illustrative brief can describe a ceramic desk lamp on a pale stone table, soft window light, a close view of the material and open space for a separate headline. For an illustration, specify the characters, action and intended aesthetic instead of expecting a single style word to define the entire scene.
The producer documents one to ten output images from a generation request, with one as the default. Several results from the same brief provide alternatives to review; they do not guarantee an identical subject across every variation. Check the subject, composition and important details, then retain the version that best fits the brief. Keep the brief and selected variation together so later edits use the intended composition.
The generation guide documents automatic aspect-ratio selection or an explicit ratio. Its listed choices include 1:1, 16:9, 9:16, 4:3, 3:4, 3:2, 2:3, 2:1, 1:2, 19.5:9, 9:19.5, 20:9, 9:20, 21:9 and 5:2. Choose the shape around the intended placement: square for a compact tile, portrait for a vertical composition, or landscape for a wide scene. Specify the crop-sensitive subject and the space that the layout needs rather than relying on the aspect ratio alone.
The documented generation-resolution settings are 1k and 2k, with 1k as the default. Quality is a separate control with low, medium and auto choices. In xAI’s current guide, auto is the default and uses low for generation and medium for editing; an explicit low or medium setting pins that choice. Resolution and quality therefore describe different controls. State the visual details that matter and inspect them in the returned image rather than treating either setting as a guarantee of exact lettering, geometry or subject preservation.
Supply the image to change and describe the requested change in relation to its visible content. A focused edit might ask to replace a dark wall with a light plaster surface while preserving the furniture arrangement, camera viewpoint and warm illumination. If the intent is a stylistic transformation, specify the desired treatment: the producer demonstrates photography, anime, oil painting, watercolor, pop art and pencil-sketch styles. Identify which elements should retain their appearance and which may change with the treatment.
The maker’s editing workflow accepts a source-image reference, encoded image data or a file identifier. For stored references, use fully uploaded PNG, JPEG or WebP images. Its guide also documents successive edits: use the result of one edit as the input to the next. This can turn a base composition into a more specific result through a furniture change followed by a lighting adjustment. Keep the original and the chosen intermediate image associated with each brief so that a later refinement can be checked against the intended composition.
The current multi-image guide allows up to five source images in one edit. Refer to them in their supplied order and give each a clear role, such as the subject from the first image and the environment from the second. The output ratio follows the first input image by default, with an explicit ratio available to override it. For a product-in-room concept, describe the product’s position, size and contact with the room’s surfaces, then ask to preserve the details that identify it. Review how the sources were combined instead of assuming that every element was copied without alteration.
The producer returns a temporary image address by default and also documents encoded-image output. Retain the actual image promptly when it is needed as an asset. Its optional deferred workflow separates request acknowledgment from completion: a request identifier is followed by pending, done or failed status, and deferred results use the address response format with a documented 24-hour retention period. A submitted request or a pending status is not a finished image. Retain the completed image with its brief and chosen settings for later reuse.
A useful final artifact is an image that fits a defined scene, layout or edit brief. Inspect the full composition and its small details, especially the source subject, object boundaries, proportions and any lettering that carries meaning. For iterative work, change the instruction associated with the visible issue and use the selected result as the next reference. Keep the desired modification and preservation instructions concrete so that each result can be assessed against a specific creative purpose.
", "aboutText": "Grok Imagine Image 2.0 is xAI’s image-generation and editing model. It takes a written description, or a description together with source images, and returns an image result. The producer’s named 2.0 profile covers creating a scene, changing an existing image, combining subjects from references and transforming visual style. Start by choosing whether you need a new composition or a specific change to material you already have.\n\n### Creating an image from a brief\n\nDescribe the main subject, its setting, the composition, lighting and visual treatment. Identify what the viewer should notice first and where the image will be used. For a product concept, an illustrative brief can describe a ceramic desk lamp on a pale stone table, soft window light, a close view of the material and open space for a separate headline. For an illustration, specify the characters, action and intended aesthetic instead of expecting a single style word to define the entire scene.\n\nThe producer documents one to ten output images from a generation request, with one as the default. Several results from the same brief provide alternatives to review; they do not guarantee an identical subject across every variation. Check the subject, composition and important details, then retain the version that best fits the brief. Keep the brief and selected variation together so later edits use the intended composition.\n\n### Composition, resolution and quality\n\nThe generation guide documents automatic aspect-ratio selection or an explicit ratio. Its listed choices include 1:1, 16:9, 9:16, 4:3, 3:4, 3:2, 2:3, 2:1, 1:2, 19.5:9, 9:19.5, 20:9, 9:20, 21:9 and 5:2. Choose the shape around the intended placement: square for a compact tile, portrait for a vertical composition, or landscape for a wide scene. Specify the crop-sensitive subject and the space that the layout needs rather than relying on the aspect ratio alone.\n\nThe documented generation-resolution settings are 1k and 2k, with 1k as the default. Quality is a separate control with low, medium and auto choices. In xAI’s current guide, auto is the default and uses low for generation and medium for editing; an explicit low or medium setting pins that choice. Resolution and quality therefore describe different controls. State the visual details that matter and inspect them in the returned image rather than treating either setting as a guarantee of exact lettering, geometry or subject preservation.\n\n### Editing and transferring visual style\n\nSupply the image to change and describe the requested change in relation to its visible content. A focused edit might ask to replace a dark wall with a light plaster surface while preserving the furniture arrangement, camera viewpoint and warm illumination. If the intent is a stylistic transformation, specify the desired treatment: the producer demonstrates photography, anime, oil painting, watercolor, pop art and pencil-sketch styles. Identify which elements should retain their appearance and which may change with the treatment.\n\nThe maker’s editing workflow accepts a source-image reference, encoded image data or a file identifier. For stored references, use fully uploaded PNG, JPEG or WebP images. Its guide also documents successive edits: use the result of one edit as the input to the next. This can turn a base composition into a more specific result through a furniture change followed by a lighting adjustment. Keep the original and the chosen intermediate image associated with each brief so that a later refinement can be checked against the intended composition.\n\n### Combining multiple references\n\nThe current multi-image guide allows up to five source images in one edit. Refer to them in their supplied order and give each a clear role, such as the subject from the first image and the environment from the second. The output ratio follows the first input image by default, with an explicit ratio available to override it. For a product-in-room concept, describe the product’s position, size and contact with the room’s surfaces, then ask to preserve the details that identify it. Review how the sources were combined instead of assuming that every element was copied without alteration.\n\n### Receiving and retaining the image\n\nThe producer returns a temporary image address by default and also documents encoded-image output. Retain the actual image promptly when it is needed as an asset. Its optional deferred workflow separates request acknowledgment from completion: a request identifier is followed by pending, done or failed status, and deferred results use the address response format with a documented 24-hour retention period. A submitted request or a pending status is not a finished image. Retain the completed image with its brief and chosen settings for later reuse.\n\nA useful final artifact is an image that fits a defined scene, layout or edit brief. Inspect the full composition and its small details, especially the source subject, object boundaries, proportions and any lettering that carries meaning. For iterative work, change the instruction associated with the visible issue and use the selected result as the next reference. Keep the desired modification and preservation instructions concrete so that each result can be assessed against a specific creative purpose.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "97837f0db333aa0408feade952146d3f5ac1ea3f7115f54e86a040aac8f9274e", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "x-ai/grok-imagine-image-2.0Grok Imagine Image 2.0 creates images from written briefs and edits existing images through natural-language instructions. xAI documents configurable quality, resolution and composition, multi-image references, style transfer and iterative refinement.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
Grok Imagine Image 2.0 is xAI’s image-generation and editing model. It takes a written description, or a description together with source images, and returns an image result. The producer’s named 2.0 profile covers creating a scene, changing an existing image, combining subjects from references and transforming visual style. Start by choosing whether you need a new composition or a specific change to material you already have.
Describe the main subject, its setting, the composition, lighting and visual treatment. Identify what the viewer should notice first and where the image will be used. For a product concept, an illustrative brief can describe a ceramic desk lamp on a pale stone table, soft window light, a close view of the material and open space for a separate headline. For an illustration, specify the characters, action and intended aesthetic instead of expecting a single style word to define the entire scene.
The producer documents one to ten output images from a generation request, with one as the default. Several results from the same brief provide alternatives to review; they do not guarantee an identical subject across every variation. Check the subject, composition and important details, then retain the version that best fits the brief. Keep the brief and selected variation together so later edits use the intended composition.
The generation guide documents automatic aspect-ratio selection or an explicit ratio. Its listed choices include 1:1, 16:9, 9:16, 4:3, 3:4, 3:2, 2:3, 2:1, 1:2, 19.5:9, 9:19.5, 20:9, 9:20, 21:9 and 5:2. Choose the shape around the intended placement: square for a compact tile, portrait for a vertical composition, or landscape for a wide scene. Specify the crop-sensitive subject and the space that the layout needs rather than relying on the aspect ratio alone.
The documented generation-resolution settings are 1k and 2k, with 1k as the default. Quality is a separate control with low, medium and auto choices. In xAI’s current guide, auto is the default and uses low for generation and medium for editing; an explicit low or medium setting pins that choice. Resolution and quality therefore describe different controls. State the visual details that matter and inspect them in the returned image rather than treating either setting as a guarantee of exact lettering, geometry or subject preservation.
Supply the image to change and describe the requested change in relation to its visible content. A focused edit might ask to replace a dark wall with a light plaster surface while preserving the furniture arrangement, camera viewpoint and warm illumination. If the intent is a stylistic transformation, specify the desired treatment: the producer demonstrates photography, anime, oil painting, watercolor, pop art and pencil-sketch styles. Identify which elements should retain their appearance and which may change with the treatment.
The maker’s editing workflow accepts a source-image reference, encoded image data or a file identifier. For stored references, use fully uploaded PNG, JPEG or WebP images. Its guide also documents successive edits: use the result of one edit as the input to the next. This can turn a base composition into a more specific result through a furniture change followed by a lighting adjustment. Keep the original and the chosen intermediate image associated with each brief so that a later refinement can be checked against the intended composition.
The current multi-image guide allows up to five source images in one edit. Refer to them in their supplied order and give each a clear role, such as the subject from the first image and the environment from the second. The output ratio follows the first input image by default, with an explicit ratio available to override it. For a product-in-room concept, describe the product’s position, size and contact with the room’s surfaces, then ask to preserve the details that identify it. Review how the sources were combined instead of assuming that every element was copied without alteration.
The producer returns a temporary image address by default and also documents encoded-image output. Retain the actual image promptly when it is needed as an asset. Its optional deferred workflow separates request acknowledgment from completion: a request identifier is followed by pending, done or failed status, and deferred results use the address response format with a documented 24-hour retention period. A submitted request or a pending status is not a finished image. Retain the completed image with its brief and chosen settings for later reuse.
A useful final artifact is an image that fits a defined scene, layout or edit brief. Inspect the full composition and its small details, especially the source subject, object boundaries, proportions and any lettering that carries meaning. For iterative work, change the instruction associated with the visible issue and use the selected result as the next reference. Keep the desired modification and preservation instructions concrete so that each result can be assessed against a specific creative purpose.
POST /v1/images/generationstext, imageimage| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits x-ai/grok-imagine-image-2.0 | Default— |
Fieldprompt | Typestring | RequirementRequired | Values & limits Minimum length: 1 | Default— |
Fieldresolution | Typestring | RequirementOptional | Values & limits 1K, 2K | Default— |
Fieldaspect_ratio | Typestring | RequirementOptional | Values & limits 1:1, 3:4, 4:3, 9:16, 16:9, 2:3, 3:2, 9:19.5, 19.5:9, 9:20, 20:9, 1:2, 2:1, auto | Default— |
Fieldquality | Typestring | RequirementOptional | Values & limits low, medium | Default— |
Fieldn | Typeinteger | RequirementOptional | Values & limits Minimum: 1 Maximum: 1 | Default— |
Fieldinput_references | Typearray | RequirementOptional | Values & limits Minimum items: 0 Maximum items: 3 | Default— |
Fieldprovider | Typeobject | RequirementOptional | Values & limits | Default— |
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, prompt |
Parametermaterial_types | Contracttext, image |
Lifecycle: synchronous_result_then_owned_library
GET /v1/media/tasks/{task_id} · actual returned task_id or media library record
GET /v1/media/assets/{asset_id}/content
GET /v1/media/assets
GET /v1/media/assets/{asset_id}
The displayed rates estimate the cost before generation. The final charge is calculated from the cost recorded for the original generation. Measured output duration and forecast quantities are not the final billable quantity.
Tariff references do not add request options. Supported parameters are listed for the selected method.
Match each charge to the conditions shown. Use one rate for each set of alternative configurations.
| Configuration | Rate schedule | Forecast quantity | Billing unit | Charge |
|---|---|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Forecast quantity— | Billing unit— | Charge Input · Input tokens · Estimate for comparison only — / 1K tokens Output · Output tokens · Estimate for comparison only — / 1K tokens Input · Cache read · Estimate for comparison only — / 1K tokens Input · Cache write · Estimate for comparison only — / 1K tokens Input · Cache write, 1 hour · Estimate for comparison only — / 1K tokens |
| Configurationinput image | Rate schedule— | Forecast quantity— | Billing unitper input image | Charge Input · input image · Estimate for comparison only $0.02 per input image |
| ConfigurationEstimated generation cost | Rate schedule— | Forecast quantityone generation estimate | Billing unit— | Charge Output · Estimated generation cost · Estimate for comparison only $0.08 estimate before generation This estimate is not an additional charge or a fixed rate for the completed generation. |
Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →
set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\nexport AILOOT_API_KEY\npython3 - <<'PY_REQUEST'\nimport json,os\nfrom pathlib import Path\np={'model': 'x-ai/grok-imagine-image-2.0', 'prompt': 'a red panda astronaut floating in space, studio lighting'}\n\nPath("request.json").write_text(json.dumps(p,ensure_ascii=False))\nPY_REQUEST\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/images/generations \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \\\n --data-binary @request.json -D response-headers.txt -o result.json\npython3 - <<'PY_RESULT'\nimport base64, json, os, subprocess\nfrom pathlib import Path\nfrom urllib.parse import urlsplit, urljoin\n\ndef save_images(items):\n if not items: raise SystemExit("No completed images; retain the full response")\n for index, item in enumerate(items):\n encoded=item.get("b64_json")\n uri=item.get("url", "")\n if not encoded and uri.startswith("data:image/"):\n header, separator, encoded=uri.partition(",")\n if not separator or ";base64" not in header: raise SystemExit("Unsupported image data URI")\n if encoded:\n raw=base64.b64decode(encoded,validate=True)\n elif uri:\n uri=urljoin("https://api.ailoot.ai",uri)\n parsed=urlsplit(uri)\n if parsed.scheme!="https" or not parsed.netloc or parsed.username or parsed.password:\n raise SystemExit("Invalid returned image URL")\n owned=parsed.netloc=="api.ailoot.ai" and parsed.path.startswith("/v1/media/assets/") and parsed.path.endswith("/content")\n args=["curl","--fail-with-body","--silent","--show-error",uri]\n if owned: args += ["-H","Authorization: Bearer "+os.environ["AILOOT_API_KEY"]]\n temporary=Path(f"image-{index}.bin")\n subprocess.run(args+["-o",str(temporary)],check=True)\n raw=temporary.read_bytes()\n temporary.unlink()\n else: raise SystemExit("Image has neither bytes nor URL")\n if not raw: raise SystemExit("Empty image result")\n ext="png" if raw.startswith(b"\\x89PNG") else "jpg" if raw.startswith(b"\\xff\\xd8") else "webp" if raw[:4]==b"RIFF" and raw[8:12]==b"WEBP" else "svg" if raw.lstrip().startswith((b"<svg",b"<?xml")) else "bin"\n Path(f"image-{index}.{ext}").write_bytes(raw)\n print("Every returned image saved; complete response metadata retained")\nsave_images(json.loads(Path("result.json").read_text())["data"])\nPY_RESULT\nDownload each returned image or save its Base64 contents
GET /v1/media/tasks/{task_id}GET /v1/media/assets/{asset_id}/contentGET /v1/media/assetsGET /v1/media/assets/{asset_id}set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/media/assets \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -o owned-assets.json\n# Preserve every returned asset and follow its exact signed content URL. Do not construct a signed token.\nSave every completed image; retrieve each returned URL or decode its Base64 contents.
Retain the complete response and headers, every actual output, original returned identifiers and all usage fields. Recover the original operation without submitting creation again.
Keep the returned X-Client-Request-ID for reconciliation. Read only actual returned task_id/asset_id values or the owned media library; never build a task URL from the operation ID and never resubmit creation.
| Field | Type |
|---|---|
Fieldcreated | Type |
Fielddata[].url | Type |
Fielddata[].b64_json | Type |
Fieldusage | Type |
Ailoot Ultra x-ai/grok-imagine-image-2.0
/v1/images