Generate images from text prompts
🤖/image/generate generates images from text prompts using AI.

Usage example
Inpaint an image by uploading an original image and a mask image, then use both files in /image/generate:
{
"steps": {
":original": {
"robot": "/upload/handle"
},
"inpainted": {
"format": "png",
"model": "google/nano-banana-pro",
"prompt": "Replace the masked area with a breaching whale. Keep the rest of the image unchanged.",
"robot": "/image/generate",
"use": [
{
"as": "image",
"name": ":original"
},
{
"as": "mask",
"name": ":original"
}
]
}
}
}Parameters
interpolateboolean | Record<string, boolean>Controls whether Assembly Variables are interpolated for individual instruction fields.
By default, most Robot instruction fields interpolate Assembly Variables. Set this to
falseto treat every instruction field as literal text, or set an individual field path tofalseto treat only that field as literal text. For Robot-specific fields that are literal by default, set this totrueor set that field path totrueto opt back into interpolation.Use field names such as
path, or dotted paths such asffmpeg.vffor nested objects.output_metaRecord<string, boolean> | boolean | Array<string>Allows you to specify a set of metadata that is more expensive on CPU power to calculate, and thus is disabled by default to keep your Assemblies processing fast.
For images, you can add
"has_transparency": truein this object to extract if the image contains transparent parts and"dominant_colors": trueto extract an array of hexadecimal color codes from the image.For images, you can also add
"blurhash": trueto extract a BlurHash string — a compact representation of a placeholder for the image, useful for showing a blurred preview while the full image loads.For videos, you can add the
"colorspace": trueparameter to extract the colorspace of the output video.For videos, you can also add
"interlaced": trueto detect whether the video is interlaced. This combines the cheap ffprobefield_orderflag with a boundedidetsampling pass over the first frames of the source, exposinginterlaced,field_order, and a diagnosticinterlace_detectionobject underfile.meta. This is computationally expensive and billed accordingly.For audio, you can add
"mean_volume": trueto get a single value representing the mean average volume of the audio file.You can also set this to
falseto skip metadata extraction and speed up transcoding.user_metaRecord<string, any>(default:{})Adds custom JSON metadata to each emitted file without changing its contents. Nested objects and arrays are supported.
Inheritance depends on the Robot. Values merge with existing
user_metaon the output file; the current Step replaces matching top-level keys. Assign required keys explicitly when a Robot creates fresh outputs.In processing Steps,
${file.*}refers to the first input and${result.*}to the emitted file. Values are evaluated per output after the Robot runs, before subsequent metadata extraction and temporary storage. On:original, values are evaluated per upload before metadata extraction.Downstream Steps read
${file.user_meta.key}. See Custom metadata for a complete example and inheritance rules.resultboolean(default:false)Whether the results of this Step should be present in the Assembly Status JSON
queuebatchSetting the queue to 'batch', manually downgrades the priority of jobs for this step to avoid consuming Priority job slots for jobs that don't need zero queue waiting times
force_acceptboolean(default:false)Force a Robot to accept a file type it would have ignored.
By default, Robots ignore files they are not familiar with. 🤖/video/encode, for example, will happily ignore input images.
With the
force_acceptparameter set totrue, you can force Robots to accept all files thrown at them. This will typically lead to errors and should only be used for debugging or combatting edge cases.ignore_errorsboolean | Array<meta | execute>(default:[])Ignore errors during specific phases of processing.
Setting this to
["meta"]will cause the Robot to ignore errors during metadata extraction.Setting this to
["execute"]will cause the Robot to ignore errors during the main execution phase.Setting this to
trueis equivalent to["meta", "execute"]and will ignore errors in both phases.usestring | Array<string> | Array<object> | objectSpecifies which Step(s) to use as input.
For inpainting, provide both the source image and mask through
use, typically with:{ "use": [ { "name": ":original", "as": "image" }, { "name": ":original", "as": "mask" } ] }Best practice:
- Tag source and mask inputs explicitly using
as(or semantic upload field names) - Keep the prompt focused on what should change in the masked/transparent region
- Leave the model choice to the robot defaults unless you have a specific need
- Tag source and mask inputs explicitly using
modelstringThe AI model to use. Defaults to
google/nano-banana. Supported models includeflux-1.1-pro-ultra,flux-schnell,recraft-v3,google/nano-banana,google/nano-banana-2,google/nano-banana-pro,openai/gpt-image-2, andstability-ai/stable-diffusion-inpainting. The legacy aliasgpt-image-2is also accepted for backwards compatibility.prompt— requiredstringPrompt describing the desired image. For inpainting, describe what should appear in the masked/transparent region and that the rest should stay unchanged.
formatjpeg | jpg | png | gif | webp | svgOutput format. Defaults depend on model: png for Google models and openai/gpt-image-2, svg for recraft-v3, jpeg for others. Google models currently return PNG only.
seedstring | numberSeed for the random number generator.
aspect_ratiostringRequested output aspect ratio. For Google models, width/height can also be used and orientation is derived automatically when aspect_ratio is omitted.
heightstring | numberRequested output height in pixels (mainly used by Google image models and openai/gpt-image-2).
widthstring | numberRequested output width in pixels (mainly used by Google image models and openai/gpt-image-2).
stylestringStyle of the generated image.
num_outputsstring | numberNumber of output variants to generate (1-10).