Every other page here is about a category of garment. This one is about you: a brand with its own storefront, its own catalogue and a decision about whether to put try-on on your product pages.
Three ways in
One script tag. A publishable key, an origin allowlist, and the interface renders in a shadow root so your CSS and ours cannot collide. No build step and no framework requirement.
A platform app. Shopify installs through OAuth with catalogue sync and no key in the page at all — requests go through Shopify's app proxy. WooCommerce installs with a one-time code and routes through your own site's REST endpoint. Same widget file in every case.
The API directly. For a custom storefront or an app. The shopper-facing endpoint is synchronous, because a shopper waiting on a product page is a different problem from a backend integration.
What it costs
Credits, bought in packs, one per successful try-on regardless of how many garments compose the outfit. A failed or refused generation costs nothing. Current rates are on the pricing page.
The things worth knowing before you commit
Latency is around 50 seconds on the current model, not the ten that this kind of product is usually marketed with. It is being worked on and it is the honest number today.
Fine detail is approximate. Silhouette, proportion, colour and cut are the strengths. Logos, text, lace, beading and precise print repeats are not. Try-on belongs beside your photography.
It is not a fit or sizing tool, and your storefront should not present it as one.
Shopper consent is not configurable. The widget will not accept a photograph until the shopper has agreed, and that cannot be switched off. If your conversion model depends on removing that step, this is not the right product.