Nodes/BizyAirPlus/X AI Grok 2 Image (Channel Edition)
ComfyUI Node

X AI Grok 2 Image (Channel Edition)

XAI's Grok 2 image generation as a single ComfyUI node

By siliconflow·Created 5 months ago·Updated about a month ago· 20
X AI Grok 2 Image (Channel Edition)
  • api_config
  • image
  • request_id
  • urls
prompt
skip_errorfalse

This is the node with the shortest possible explanation: you type a prompt, it calls xAI's Grok 2 image model in the cloud, and an image comes back. There are no other required inputs. That's the entire surface of the Channel Edition of Grok 2 Image in BizyAirPlus - a bare prompt input and three outputs.

Why you'd reach for it

Grok has a specific reputation in this space, and it's the reason you'd pick this node over any local model. The community's consensus on xAI's image generation is that it's the least restrictive mainstream service - the one that'll do the photorealistic and mature-adjacent material other closed APIs flatly refuse. There's also the long-running thread that it's "just FLUX under the hood" with different guardrails, which is part of why the outputs look so strong. If you want that behavior without leaving ComfyUI, this is the on-ramp.

The honest framing: you're getting a closed, cloud-rendered, billed-per-image model with essentially zero local infrastructure cost. There's no VRAM requirement, no checkpoint, no sampler. The trade is that you have no real controls - no resolution picker, no aspect ratio, no negative prompt, no seed on this Channel Edition. What you type is basically all of the leverage you have.

How it works

The mechanism is the same cloud-execution pattern that runs through the whole BizyAirPlus pack. The node takes your prompt, submits it through BizyAir's channel to Grok 2, polls until the render completes, and returns image (IMAGE - wire it to a Save Image or preview node), request_id (STRING - trace ID), and urls (STRING - where the output file lives). Nothing runs locally.

Two optional inputs matter for workflow robustness: api_config (type BIZYAIR_OPENAPI_CONFIG) lets you override base_url and api_key for a single request, and skip_error makes a failed call emit an error placeholder instead of aborting the whole queue. For a node this thin, that's the whole troubleshooting surface.

Install and setup

Same one-time install as every node in this pack:

cd ComfyUI/custom_nodes
git clone https://github.com/siliconflow/BizyAirPlus.git
cd BizyAirPlus
python -m pip install -r requirements.txt

Restart ComfyUI (or install "BizyAirPlus" via ComfyUI Manager). No model downloads - the bizyair-cloudberry and bizytrd pip packages auto-install on startup and contain the node definitions. Then flip the BizyAirPlus button in the action bar to ON, create an account at bizyair.ai, paste in the API key (prompt, Settings > BizyAirPlus > API Key, or the BIZYAIR_API_KEY environment variable), and queue.

Common issues

  • "API Key is missing" - switch is on, no key set. Sort that before anything else.
  • Image doesn't match the prompt - there's no negative prompt or seed to steer with, so the prompt has to carry the whole intent. Be literal, name the style, and iterate on wording.
  • Unexpected guardrail behavior - Grok is the least restrictive, not unrestricted. If a request gets refused, that's the model's filter, and no input on this node will talk it out of it.

Worth saying plainly: this node sends your prompt to a third-party cloud, and BizyAir's auto-install behavior has made the community wary. It's a legitimate SiliconFlow product, but keep the pack switch OFF when you're running local-only workflows and be deliberate about what you send up.

CategoryBizyAirModelServices/BizyTRD/Grok Image

Inputs (3)

NameTypeDefaultDescription
promptSTRINGPrompts
api_configoptBIZYAIR_OPENAPI_CONFIG单次请求覆盖base_url和api_key
skip_erroroptBOOLEANfalse开启后遇到错误不中断工作流,输出对应类型的错误占位符

Outputs (3)

NameTypeDescription
imageIMAGE
request_idSTRING
urlsSTRING