The Quick Creator (QC) API can fill a site's image placeholder with AI-generated images whenever stock images do not cover them. Before the site is created, you get an image plan with an editable prompt per image, so you stay in control of what is generated.

How it works

When a QC site is created, every image slot in the template is filled in this order:

  1. Your uploaded images that match the site's business type and image type.

  2. Mono stock images or Mono AI stock images (depending on your usage terms) that match the site’s business and image type.

  3. New AI-generated images for any slot still empty.

There are three main steps:

  1. Enable AI images for your organisation (one-time setup).

  2. Generate content and review the image plan using /generate-content.

  3. Create the site with your (edited) image plan using /sites.

Quick Creator API: API Documentation


1. Enable AI images

AI image settings are configured per organisation in your reseller settings (RCS). Contact your Mono account manager or support contact to change them.

Setting

What it controls

Default

/generate-content

Uses Mono's curated AI stock images for global business types.

[Off]

quickCreatorV2.aiImage

Generates an image plan in generate-content and AI images for slots that stock images cannot fill.

[Off]

quickCreatorV2.enableAiGeneratedImages

Search and reuse the shared pool of already generated images in the AI library. Does not trigger new generation.

[On]

Mono AI stock image catalogue can be provided upon request. Browse the AI stock images available per global business type and image type.


2. Generate content and review the image plan

Call generate-contentas usual. When <>quickCreatorV2.aiImage is enabled, every image slot in the template is included, and the response contains three extra objects.

Field

What it is

When to edit it

imagePrompts

A map of image ID to a short image(wide-shot, full-shot) description (subject and composition). One entry per image slot.

To change what an individual image shows.

visualLock

The shared look and feel for the whole site: place, light, palette, subject, and exterior, interior, and product cues. It is applied to every image so they look like one coherent set.

To change the overall style. Edit here instead of repeating the same detail in every imagePrompts entry.

shotSettings

Per image: exterior, interior, or product. Chooses which part of visualLock applies to that shot. At most one exterior per site is intended.

When you change the type of shot in imagePrompts.

 

Example image plan

 

Image ID

imagePrompts

shotSettings

image_heroImage_322

Street-level exterior of a bakery entrance, red brick facade and tall timber windows

exterior

image_background_43

Interior counter view with white tile walls, pale oak counter, and a glass display of ice cream

interior

image_singleImage_332

Close-up of a waffle topped with ice cream and fruit on pale oak

product

image_galleryImage_46

Close-up of a milkshake in a clear glass, topped with cream and cocoa dust

product

 
 

Editing tips

Keep the three fields consistent. If you change an imagePrompts entry from an interior to a product shot, also set its shotSettings to product. Conflicting values do not return an error, but the image may not match the prompt.

  • Do not add personal data such as names, phone numbers, email addresses or street addresses to prompts. This information from globalData is automatically redacted for image generation.

  • Prompts describe the scene, not text. Avoid asking for logos, signs, or written words in the image.


3. Create the site

Call sites and include imagePrompts, visualLock, and shotSettings in the request body, either as returned or as edited. Whatever you send is what QC uses to generate the images.

When using stock or AI stock images, businessType must be one of Mono’s global business types. Use the business type key (camelCase), not the name.

Site creation runs as a job. Image generation increases its duration, so poll the job status until it completes. A site with six new images typically takes about 4 minutes.

If you retry site creation for the same draft without changing the prompts, QC reuses the images already generated instead of creating new ones.


What happens with AI-generated images

Labelled as AI-generated

Every AI-generated image is labelled so you and your customers can meet transparency requirements, such as the EU AI Act.

  • In the Editor: The image shows an AI generated checkbox, next to the author field. Users can check or uncheck it per image.
  • On the published site: The label is exposed as a data attribute on the image [data-attribute-name].

Privacy

QC never sends the company name, email, phone number, or street addresses to the image provider. Prompts are built only from the rest of globalData such as business type, descriptionShort, descriptionLong, locale, image type, and the image plan.

Content moderation

Prompts are checked for inappropriate content. If a prompt is blocked, QC tries once with a cleaned-up prompt. If that is also blocked, the image is not generated and the site creation job fails with an error message.

Limits

  • A weekly cap on AI-generated images applies, based on your AI usage terms with Mono.

  • The business type must currently exist under your reseller before AI images can be generated. If you use a custom business type, create it first with the HAL API (see QC Reseller Stock Images).


Template/Framework setup (optional)

AI images use the same QC Tags as stock images: row and column backgrounds, Image modules, and Gallery modules. If your templates already work with stock images, no changes are needed.

See Configure AI Tags on templates for setup steps, including multi-language templates.


Troubleshooting

No image plan in the generate-content response

Is quickCreatorV2.aiImage enabled for your organisation?

  • Does the template have QC Tags configured for its image slots?

AI images are not generated

Does the business type exist in HAL, and is the same key used in /sites?

  • Did you include imagePrompts, visualLock,and shotSettings in the <>/sites request?

  • Did the site creation job fail? Check the job status for an error message, for example a moderation block or timeout.

The images look inconsistent with each other

Move shared details (light, palette, setting) into visualLock instead of individual prompts.

  • Check that each shotSettings value matches its prompt.

Was this article helpful?
0 out of 0 found this helpful