You can generate item images from a text prompt inside the collection flow, and save the result as an item or as the collection cover.
What it costs
Each generation is charged in satoshis, calculated from a fixed price and the exchange rate at that moment. Subscribers pay half.
The amount is shown before you generate. It is charged per generation, not per saved image — a prompt you do not like still cost something, which is the honest way round: the model ran either way.
Saving what you generated
Save as item or Save as cover. The modal stays open so you can generate and save several in a row, and closing it is your decision.
Two behaviours worth knowing, because they were built on purpose:
- The button shows a progress indicator and locks while saving. Do not click twice: the same image would be uploaded twice.
- If saving fails, the modal stays open and tells you. You can retry without paying for another generation — the image you already paid for is still there.
What is behind the modal does not refresh by itself. The success message is your confirmation; reload when you are done if you want to see it in place.
The collection is flagged as AI, publicly
Using a single generated image marks the whole collection, and an AI-generated badge shows on it wherever it appears — in the mint zone, on the card, to everybody.
That is not a penalty and it is not hidden from you: collectors get to know how what they are buying was made. Declare it honestly in step 1 as well; the badge appears either way.
The copyright check
You can run an advisory copyright check on an image. It sends the image to a model that gives a verdict — fine, doubtful, or risky — with a reason and a confidence level, and the result is stored with the item.
It costs 10% of a generation, so it is cheap enough to use on anything you are unsure about.
Advisory means advisory. It is one model's opinion, not a legal clearance and not a guarantee. A green verdict does not make an image yours to publish, and it will not defend you if it is not. Use it to catch the obvious, not to outsource the decision.
What can and cannot be checked
The check works by looking at the image, so it is only offered for images. For video, 3D or HTML the button is disabled with the reason rather than hidden — a button that disappears reads as a bug, while a disabled one tells you something.
HTML items get a security check instead, and it is the more important of the two: an HTML piece runs in a frame on a page where people have their wallet unlocked. The check is deliberately strict and what it looks for is not published — publishing the list would be publishing the way around it. If you write HTML pieces, count on it: a piece that fails is rejected, and guessing at its limits is not a good use of your time.