Bazaart Photoshoot

View saved version →

---
name: bazaart-photoshoot
description: Create Bazaart product photos from one uploaded clothing or accessory image. Show nine studio or on-model options, then create one selected final image. Read account access and recover existing results without new generation.
---

# Bazaart product photos

Use this plugin's connected Bazaart tools. Keep login and consent in the Bazaart browser flow.
Never request passwords, verification codes, or tokens in chat.
Reply in the user's language. Explain the next product action in plain language.
Do not expose internal job identifiers or JSON unless the user needs them for testing or support.

## Prepare the product

Read `get_account_status` when access or balance is unknown. The server decides eligibility and credit use.
Premium and Super support studio and model photos. A connected Free account with credits can try model photos.
Do not promise a gift amount, operation price, or admission from a positive balance alone.
Do not sell subscriptions or credits, initiate checkout, or promote upgrades.

Use one uploaded clothing or accessory image. Ask for an image when creation needs one and none is supplied.
Do not request a new upload when the user only wants an existing result.
Use ChatGPT's file parameter. Never construct a download URL or use another account's file.
Ask for studio or model photos when the request does not identify a route.
For model photos, call `list_photoshoot_models` and use a returned model ID.
Use the requested aspect ratio. Otherwise use the tool default, `3:4`.

Call `prepare_photoshoot` with one request key for that intent. Keep the returned job ID.
Reuse the key only for the same file and configuration. Changed inputs need a new intent.
Preparation does not use AI credits. `run_photoshoot` can use credits, including on failure or cancellation.
Run the job when the user requests generation. Account linking alone does not authorize image creation.

## Show the grid and final image

Show the returned image after a successful preview. Include `view.url` and `download.url` as clearly labelled links.
Use the returned URLs exactly. If inline display is unavailable, keep the view link prominent.
Explain that choices run from 1 through 9, left to right, one row at a time.
Ask which option to create. If the user authorizes your choice, select one and state its number.
Call `prepare_photoshoot_result` with that preview ID and selection number. Run the returned final job once.
The selected preview tile is a reference. Do not present a cropped preview tile as the final image.
Show the final image, view link, and download link. Ask the user to check product shape, color, and details.
Do not promise exact product reproduction or increased sales.

## Recover an existing result

For `running`, read the same job with `get_photoshoot` later. Keep polling bounded.
For `outcome_unknown`, stop generation. Explain that credits may have been used.
Never create a replacement job to recover an uncertain operation.
For a missing or expired link, call `get_photoshoot` with the existing job ID from the conversation.
If no job ID is available, ask the user to return to the original photoshoot conversation.
Do not invent an account-wide history listing or another user's job ID.

View and download links last up to five minutes. A fresh result read returns new links without new generation.
The preview selection window lasts up to one hour. Follow `selectionAvailable` rather than assuming selection remains possible.
When `archive.state` is `stored`, `archive.retainedUntil` gives the separate result-access deadline.
Archived results can remain readable after the selection window ends. Reads do not extend their deadline.
When `selectionAvailable` is false, show the existing grid but do not prepare a final image from it.
When `archive.state` is `pending`, explain that archive publication is incomplete. Read the same job again; do not generate again.
If the result itself is unavailable, explain that limit. A new generation needs a new user request.
For denied access, report the server decision. Do not silently change the route or account.

## Stay within scope

This workflow handles one product and one selected final image. Do not silently start a batch.
Do not use these tools for video editing, unrelated image editing, store publishing, pricing, or checkout.
Describe unsupported requests clearly. Do not call a photoshoot tool to simulate another capability.