Select the route from the required source of scene information
Claid's AI Background API provides three approaches: generation from a text prompt, generation using a template image, and a solid or transparent background with product shadows. This route decision precedes detailed scene controls.
A written creative brief belongs to template-free generation. An approved visual reference belongs to template-based generation if its viewpoint and content can support the product. A request that needs only a grounding shadow should avoid generating an unnecessary setting.
Template-free generation uses v1 by default, although Claid recommends starting with v2. For template-free v2, a manually supplied prompt can describe the setting, or scene.prompt.generate can enable Autoprompt AI at an additional 0.5 credits per request.
A template-based request requires a template_url. The template image viewpoint should match the product image viewpoint. Claid also states that non-square template images are scaled and cropped to square, making the selected reference itself a pre-submission consideration.
Keep model and operation-specific controls inside their documented scope
For template-free v2, prompt text has a documented length of 3–2048 characters, and the aspect_ratio default is 1:1. The listed ratios have corresponding output sizes; they are not guarantees of exact product geometry. Autoprompt guidelines referring to humans are supported only with v2.
The v2 preference options are fast, optimal and best. If negative_prompt is specified, Claid's explanatory rule restricts preference to optimal or best. One published JSON example also shows fast alongside negative_prompt, so treat that example as inconsistent with the explicit condition rather than relying on it as a compatible configuration.
For shadows-only, v2 accepts view values auto, top and front, with auto as the default. Omitting both color and aspect_ratio leaves a transparent background with a 1:1 ratio. The v1 shadows route instead requires top or front, excludes auto and does not support aspect_ratio.
Template-mode choices require their own approval decision. The existing guide at https://cartvisual.com/guides/claid-template-mode-approval-contract covers lock, adjust, transform and their unavailable controls. Do not apply template-mode restrictions to unrelated template-free or shadows requests.
{
"scene": {
"effect": "shadows",
"model": "v2",
"view": "front",
"color": "#ffffff",
"aspect_ratio": "1:1"
}
}Reject the wrong route before evaluating creative quality
A successful scene request does not prove that a merchant's product was rendered accurately. Keep the product source authoritative and evaluate the returned output for shape, color, identifying details and suitable grounding.
If a template has the wrong camera viewpoint, obtain an appropriate reference or choose a genuinely different creative route. A prompt is not a documented camera-calibration guarantee.
If the task only needs a transparent cutout rather than new shadows or a generated environment, consider a source-preserving background-removal workflow instead of treating every background requirement as generative.
Illustrative decision: a front-facing coffee kettle
A seller has an approved front-facing photograph of a kettle and a top-down kitchen-countertop reference. The immediate listing requirement is a plain white setting with a natural grounding shadow, not a redesigned kitchen.
Template-based generation is not the first choice: the available reference's top-down viewpoint conflicts with the kettle photograph, and the brief does not actually need that reference. The seller selects v2 shadows-only with view: front, color: #ffffff and aspect_ratio: 1:1.
If the requirement changes to a newly imagined kitchen scene, the next decision becomes template-free generation with a written v2 prompt. If the seller must reproduce a particular approved kitchen reference, they should obtain a compatible front-view template before considering template-based generation.
These branches change the API operation and the preparation task. None establishes that the generated shadow, scene or product has already passed review.
Where CartVisual fits
A relevant separate option when the seller needs a local product cutout rather than generated scenery. It is not a Claid scene or shadow API implementation.
Source and evidence scope
Prepared by the CartVisual editorial team with AI assistance. Competitor behavior is documented rather than independently executed for this guide.
Official source snapshot checked .
Claid's Scene documentation establishes the three background routes, their model-specific parameters, viewpoint constraints and documented defaults. Its preference rule conflicts with one illustrative request fragment. The source does not guarantee product preservation, exact scene reproduction or identical settings across operations.