Make the Clothing Decision
Claid accepts flat-lay or mannequin garment photos and allows up to five clothing URLs. Its default interprets the submitted clothing as a full outfit; missing parts trigger documented auto-completion, while a complete outfit receives no defaults. Therefore, the number of references is a production decision, not merely an upload detail.
Use complete references for every garment that must match a SKU, variant, coordinated set, or merchandising brief. Use a partial request only when the omitted categories are intentionally generic. Label each gap as either permitted styling or a blocker. If an omitted item is sold, featured, or needed to support a catalog claim, obtain its approved reference before generation.
The model is a separate choice: Claid can select a random suitable model by default or accept a model image URL. Do not let model selection obscure the clothing contract.
- Required product garments: include each approved garment reference.
- Permitted styling gap: document the category and the level of variation allowed.
- Unclear or commercially important gap: stop and obtain the missing reference.
Translate the Brief Into a Review State
Claid documents three useful partial-input outcomes: bottoms only add a plain white T-shirt, a top only adds neutral blue jeans, and no shoes generates matching shoes. Treat these as expected generated styling, not as evidence about a specific brand, material, colorway, or SKU. The source does not establish that the additions will match a seller’s catalog.
Before submission, create a small state record: submitted categories, missing categories, allowed defaults, and disallowed product claims. After generation, compare each required garment against its approved reference. Review generated additions only for whether they fit the creative brief; do not approve them as merchandise unless separately sourced and verified.
This guide concerns Claid’s documented request behavior. CartVisual’s /virtual-try-on route can support concept model imagery and planning, but it does not execute Claid requests or verify Claid-specific completion.
- Complete set: expected state is no documented default garments.
- Partial set: expected state includes only the documented additions that correspond to the gaps.
- Approval state: required garments pass product review; generated additions remain styling unless separately approved.
Budget Candidates and Destination
Choose the candidate count according to review capacity. Claid supports one to four output images, defaults to one, and charges two credits per output image. Thus, two candidates are four credits and four candidates are eight credits. This is a calculation from the documented rate, not an account quote.
Output configuration is optional. Without it, Claid stores the result in a temporary bucket for 24 hours and provides a public image URL. A connected AWS S3 or Google Cloud Storage destination can be configured instead. Record the destination and format with the request; output supports JPEG and PNG, with PNG as the default. The documented limits are one generation per second and 60 generations per minute, so batch scheduling should account for request count as well as candidates.
CartVisual does not perform or test this workflow. Confirm current account access, pricing, and storage configuration before production.
- Multiply candidates by two credits per output image.
- Choose one to four candidates and reserve review capacity for all of them.
- Use the temporary result only when its documented lifespan fits the handoff; otherwise configure a connected destination.
- Preserve garment references, request settings, output identifiers, and the final review decision.
Worked Example: Top-Only Styling
Hypothetical example, not an executed Claid generation: a seller has an approved red knit top, does not sell the accompanying jeans, and accepts neutral styling. The seller submits the top alone, records the permitted jeans and shoes as generated styling, requests two PNG candidates, and chooses temporary retrieval for same-day review. The budget is 2 candidates x 2 credits = 4 credits.
Approval is limited to the red top’s depiction. The jeans and shoes may be judged for visual suitability, but they are not described as separate approved products. If the seller later wants a particular denim SKU shown, the denim reference must be added before a new request.
Where CartVisual fits
CartVisual’s virtual try-on route is the closest available workspace for concept model imagery and model-reference planning. It is not a Claid API integration and does not execute or validate Claid completion behavior.
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 .
Official Claid AI Fashion Models I/O documentation supplied by the user, checked 2026-11-17 UTC. The article uses documented input, completion, output, storage, cost, and limit behavior only. CartVisual capabilities are separately stated and do not verify or execute Claid operations.