Generation nodes

A generation node holds a prompt, a model and its result. Its type is one of text, image, video, audio, model3d (the same engine as the canvas Generate button; MCP run_node_generation).

• Inputs. Connect other nodes to feed them in. A video with a start and end frame has two inputs (target_handle).
• Medium must match the node type, or the run is refused before anything is spent.
• Concurrency. Pass the node’s current version; a stale one returns conflict.
• Video is queued. A video comes back queued and lands later; the node stays running.
• Models. wiro/ and higgsfield/ models run on those providers and are always queued. An organization can restrict models: see Model allow-list.
• Cost preview. The Generate button shows the credits the run will cost with the chosen model, duration, resolution and variants, and updates as you change them. When several providers serve the model, hover the button to compare each provider’s price, the cheapest marked. Auto picks the cheapest healthy provider; choose one in the model menu to force it.
• Loops. run_node_loop queues every combination of a node’s inputs; preview_node_loop is free; more than 50 needs confirmation and more than 1000 is refused.
• Images. Remove background and 2×/4× upscale from the image toolbar.
• Uncensored models run only in an uncensored project that the org owner turned on in Settings.

Node data shapes per type: MCP describe_node_types. Tool details: MCP tools.