CartVisualCreate account

Should a Store Try-It-On Button Use FASHN Agent or Direct Try-On?

For a shopper-facing one-garment swap, FASHN recommends a direct Try-On endpoint. Agent is an experimental multi-step fashion-content workflow with a different response contract.

Published · By CartVisual editorial team

Specify the shopper action

A fashion store wants a button beside a jacket listing: a shopper provides an authorized model photograph, selects a jacket and receives a garment-swap candidate. That is one bounded transformation, not an open-ended lookbook brief. FASHN’s Agent quickstart recommends direct Try-On Max or the faster v1.6 route for shopping experiences. Agent can interpret a broad instruction and choose several image operations, but that flexibility is not automatically useful for a single shopper action. Confirm actual endpoint lifecycle and account access before designing the interface.

Compare contracts rather than brand names

Direct Try-On has its own image-field names, garment scope and output controls. Agent accepts a natural-language prompt and references, and its response can include several operations, intermediate results and partial completion. A storefront must not mark every Agent completed response as a successful garment swap without checking the intended output. Nor should the team paste an Agent prompt into a direct endpoint and assume schema parity. A generated try-on cannot establish physical fit or size suitability.

Condition or roleDecision or evidenceNext check
One shopper garment swapDirect Try-OnReview single task contract
Several campaign looks and editsAgentInspect all operations
Must retain original model compositionAppropriate direct endpointReview pose and background
Must prove physical fitNeither generated routeRequire actual garment evidence

Fictional storefront versus studio

For shopper action TRY-JACKET-01, the store records the target model source, jacket SKU and one intended swap. The direct route is evaluated for input validity and a single reviewable outcome. For internal campaign LOOKBOOK-JACKET-02, the art director asks for several scenes and coordinated styling; Agent may be appropriate because the task is genuinely multi-step. Neither route was called, and no latency or cost winner was measured. Keep shopper-upload permissions separate from permission to reuse a photograph in advertising.

Use existing guides at the right layer

The v1.6 category-scope guide diagnoses accidental full-outfit replacement after choosing that endpoint. The pose-preservation guide chooses between retaining a photograph and generating a new scene. This article makes the earlier architectural decision: deterministic shopper task or creative multi-operation request. Record request shape, output acceptance, error handling, actual quote and human review. Hold Agent adoption for a simple button unless a distinct requirement justifies its experimental response behavior.

Sources

  • FASHN Agent Quickstart — Current documented provider mechanism and scope; matrices and examples are original hypothetical editorial analysis. Source checked 2026-11-16.
  • FASHN Agent Images API — Current documented provider mechanism and scope; matrices and examples are original hypothetical editorial analysis. Source checked 2026-11-16.

Scope and evidence

Prepared by CartVisual with AI assistance and checked against the listed sources. Third-party rules and availability may change. No generation, API request, account operation, billing observation, publication, performance result or CartVisual integration was executed or measured. Fictional examples do not guarantee product accuracy or fit.

Related decisions

Explore the AI virtual try on workflow