Product · Batch Workflows

Submit one batch. Generate at any scale.

Kick off a run from Studio, the agent, the API, or MCP. Uwear generates thousands of on-brand images in a single pass and hands them back reviewed, scaling to whatever volume your catalog needs.

See it run

Watch a run of thousands generate in Studio.

One batch, submitted once, producing image after image. This is a real ten thousand image run moving through the Studio interface, no re-prompting between shots.

Four ways in

Kick off a batch from wherever you work.

Studio, the agent, the API, and the MCP all reach the same batch engine. The run is identical, whether you point and click, ask in chat, or call it from your own systems.

01 · Studio

Point and click in Studio.

Select inputs, choose a template, add to the batch, and watch every row complete.

Explore Studio
The Uwear Studio batch builder
02 · the agent

Describe it to Mouza.

Tell the Uwear agent what to shoot and it plans the whole run, then confirms before spending.

Explore the agent
MMouzabatch agent
Shoot our 180 new-arrival styles on Clara, studio, front and back.
That is 180 styles by front and back, so 360 shots on Clara. I will queue the run, retry anything that misses QA, and hand back the approved set.
Describe the run…
03 · the API

Call it from your pipeline.

POST one job per row with a bearer key, then poll for status or receive webhooks. Snake_case in and out.

Explore the API
curl https://api.uwear.ai/generation \
  -H "Authorization: Bearer $UWEAR_API_KEY" \
  -d '{
    "clothing_item_id": 18967,
    "avatar_id": 290,
    "model_slug": "nano-banana-2",
    "camera": "full_body_front",
    "aspect_ratio": "3:4",
    "num_images": 1
  }'

# one job per row, poll GET /generation/{id} or use webhooks

04 · MCP

Run it from your AI tools.

Connect Uwear as an MCP server and drive batches from Claude, Cursor, or any client, in plain language.

Explore MCP
UUwear MCPconnected
Run my summer PDP batch template on this week's new arrivals.
Queued 240 images from the summer PDP template. I will report back when the run is done and reviewed.

uwear.create_batch(template: "summer-pdp")

One job

The full matrix runs as one job.

A new collection of 10 tops and 10 bottoms in 6 colours is 3,600 combinations. Submit it once: every pairing generates in parallel, with QA on each image.

See Shop the Look

One batch run

10 tops × 6 colours
60
10 bottoms × 6 colours
60

Every pairing

3,600looks

Generated in parallel · QA on every image

Batch templates

Save a run once. Rerun it every drop.

Turn a working batch into a saved template: the models, garments, art direction, camera plan, and output settings, kept together. Reuse it for the next collection instead of rebuilding the run, and reach the same template from Studio, the agent, the API, or the MCP.

Reviewed at scale

Volume without losing control of quality.

A big run is only useful if the output is usable. Enable automatic QA on a batch and Uwear reviews every image, retries what misses, and returns the run traceable, so scale never means shipping unchecked images.

  1. 01

    Generate at volume

    Every row runs in parallel and scales to whatever the batch needs, a few hundred images or the whole catalog.

  2. 02

    Automatic QA

    Turn on QA and each image is checked against your brief and product record before it counts as done.

  3. 03

    Retry the misses

    Anything that fails is flagged and retried, so you are not hand-fixing images across a giant run.

  4. 04

    Hand off with trace

    Approved results carry their QA state, tags, and full input trace, ready to download or push downstream.

A row of generated fashion results from a single batch run

Bring one catalog run and generate it at scale.

Run your catalog

Existing customer? Log in to Studio

White cropped jacket and washed-blue trousers against the Noir Chrome wall
Black velvet-floral midi dress in profile under the Noir Chrome rim light
Brown strapless mini dress beside a chrome chair on the glossy black floor