[Feature]: OutfitAnyone-Plus and Photoroom Virtual Try-On / Virtual Model

[kailashahirwar]

Problem Statement

OpenTryOn already had dedicated cloud VTON (FLUX VTO, Vertex google-vton, Kling, FASHN, and others) and Qwen-Image composition try-on, but not Alibaba OutfitAnyone-Plus (aitryon-plus) or Photoroom Image Editing API for shopper try-on and catalog virtual models. Fitting-room and D2C/marketplace workflows need those first-party APIs.

Proposed Solution

Add Path A adapters and registry ids:

• outfitanyone-plus — DashScope aitryon-plus (Beijing-region DASHSCOPE_API_KEY). Person plus flat-lay top/bottoms/dress; async create and poll. Local files upload to DashScope temp OSS.
• photoroom-vton — Photoroom POST /v2/edit shopper try-on (PHOTOROOM_API_KEY). Person plus product required.
• photoroom-virtual-model — same API, flat-lay to on-model catalog shot. Person optional (preset avery by default).

Wire CLI, MCP tools (vton_outfitanyone_plus, vton_photoroom_vton, vton_photoroom_virtual_model), planner aliases, Studio Connect catalog (Photoroom as a new provider; OutfitAnyone-Plus under DashScope), docs, and dry-run tests.

Feature Category

New Virtual Try-On Provider

Suggested API / Interface

from tryon.api import OutfitAnyonePlusAdapter, PhotoroomVTONAdapter

oa = OutfitAnyonePlusAdapter()  # DASHSCOPE_API_KEY (Beijing)
oa.generate_and_decode(person="person.jpg", garment="top.jpeg")

pr = PhotoroomVTONAdapter()  # PHOTOROOM_API_KEY
pr.generate_and_decode(person="selfie.jpg", garment="dress.jpg", mode="try-on")
pr.generate_virtual_model(garment="flatlay.jpg", preset_model="avery")

CLI:

opentryon vton --model outfitanyone-plus --person-image person.jpg --garment-image top.jpeg
opentryon vton --model photoroom-vton --person-image selfie.jpg --garment-image dress.jpg
opentryon vton --model photoroom-virtual-model --garment-image flatlay.jpg --preset-model avery

Alternatives Considered

• Qwen-Image composition (--model qwen-image) is not a dedicated garment-fit model; OutfitAnyone-Plus is the first-party try-on API.
• Fal / Replicate wrappers skipped because first-party DashScope and Photoroom APIs exist.
• Photoroom Virtual Model is catalog (no shopper photo), so it is a second registry id on the same adapter rather than a generate-service fork.

Willing to Contribute

Yes, I'd like to implement this

Additional Context

• OutfitAnyone-Plus docs: https://www.alibabacloud.com/help/en/model-studio/aitryon-plus-api (China Beijing only).
• Photoroom API: https://docs.photoroom.com/image-editing-api-plus-plan/virtual-try-on and https://docs.photoroom.com/image-editing-api-plus-plan/virtual-model
• Distinct from Vertex google-vton (already shipped, Fixes [Feature]: Google Vertex Virtual Try-On (virtual-try-on-001) #92 / PR Add Google Vertex Virtual Try-On (google-vton) #93).
• Dedicated local VTON weights (Leffa / CatVTON) are out of scope for this change.