Developer API comparison
TryOnCloud vs FASHN AI: Virtual Try-On API Comparison for Developers
By Naveen Allem, Founder of TryOnCloud. Competitor details checked on their own websites on 17 November 2026. We make TryOnCloud, so read this as a vendor's comparison and run your own test.
FASHN and TryOnCloud both sell a virtual try-on API to developers, and both are serious, production APIs. They are built around different ideas. FASHN offers a family of models with fine control over mode, resolution and output count, delivered asynchronously. TryOnCloud offers one managed pipeline behind one synchronous call, priced flat per try-on, with rights to resell it under your own brand and particular strength in Indian ethnic wear. This page compares them for developers, section by section, using only what each company publishes.
The short answer
Developer API compared: architecture, auth and experience
The biggest difference is the shape of the API. FASHN's try-on endpoints are asynchronous. You send a request to POST /v1/run with a model name and inputs, receive an id, and then either poll the status endpoint until the job reaches completed or give FASHN a webhook URL to call when it is done. The finished images come back as URLs on FASHN's CDN, or as base64 if you ask. This is a well-tested pattern and it scales to long jobs: a 4K render in quality mode, or an agent request that chains several steps, can take minutes, and an asynchronous API handles that gracefully.
TryOnCloud's virtual try-on API is synchronous. You call POST /api/v1/generate with the garment and the person, and the response body is the finished PNG. There is no job id, no status endpoint, no webhook and no separate download. For the most common integration, a shopper taps "Try it on" and waits for one image, that removes a whole layer of code: no polling loop, no webhook receiver to secure, no state to store between the request and the result. Your server makes one request with a 120 second timeout and passes the image to the browser.
| TryOnCloud | FASHN | |
|---|---|---|
| Request model | One synchronous POST, image in the response body | Asynchronous: POST /v1/run returns an id, then poll /v1/status or receive a webhook |
| Auth | X-API-KEY header, up to 5 named keys | Authorization: Bearer key |
| Inputs | Garment as file, URL or base64; person as file or base64; up to 15MB | Product and model image; up to 30 MiB (Try-On Max) |
| Models | One managed try-on pipeline | Try-On Max (Preview), Try-On v1.6 (Stable), Agent Images (Experimental), plus model and image tools |
| Output | One PNG per request, about 1K | 1 to 4 images, PNG or JPEG, 1K, 2K or 4K on Try-On Max |
| Prompt control | No | Optional prompt on Try-On Max, e.g. tuck in a shirt |
| Test mode | Free mock mode, no charge | Not stated on the pages we read |
| SDKs | TypeScript SDK; REST from any language | TypeScript and Python SDKs |
| AI coding assistants | MCP server plus Markdown docs and llms-full.txt | Agent skill for Claude Code, Codex, Cursor and others; docs in Markdown |
Authentication and keys
Both use a secret key that must stay on your server. FASHN uses a standard bearer token. TryOnCloud uses an X-API-KEY header and lets you keep up to five named keys active at once, so an agency can give each client its own key, see when it was last used and revoke it without touching the others.
Models versus a managed pipeline
FASHN exposes its models by name. Try-On v1.6 is the stable, fast model for tops, bottoms and one-pieces; Try-On Max is the newer, more capable model in preview; Agent Images is experimental. You choose a model, a mode and a resolution, and the price follows your choice. That is powerful when you want control, and it means you also own the decision of which model to use for which garment.
TryOnCloud makes that decision for you. Behind the one endpoint is our own try-on pipeline: input checks by file content, garment preparation that lifts the garment off the model or mannequin it was photographed on, moderation, generation that keeps the shopper's face and body, and framing that keeps the whole person in the picture. You do not pick a model or a mode, and every request costs the same single credit.
Documentation and developer experience
Both companies publish clear documentation with request examples in several languages, and both cater to AI coding assistants: FASHN offers an agent skill for Claude Code, Codex, Cursor and others, and TryOnCloud offers an MCP server that lets an assistant read our docs, check your credits and run real try-ons while it writes your integration, plus a ready-made contract to paste into CLAUDE.md or AGENTS.md. TryOnCloud also has a free test mode: add mock=true and the request is fully validated without generating or charging, which keeps development and CI free.
REST API, white-label rights and scalability
For SaaS builders and agencies, three questions matter more than the model: how much traffic the API accepts, what happens when something fails, and whether you are allowed to sell it on.
| TryOnCloud | FASHN | |
|---|---|---|
| Request rate | 300 per minute per key, 600 per account | 100 per 60 seconds on /v1/run (the product FAQ says 50 per minute) |
| Concurrency | No separate concurrency cap; capacity planned with you for sustained volume | Default 6, raised on request |
| Webhooks | Not needed: synchronous | Yes, retried up to 5 times over about 5 minutes |
| Failed requests | Refunded automatically | Never charged |
| White-label resale | Allowed under your own brand, named key per client | Commercial-use licence for images; reseller terms not published |
| Uptime | 99.5% monthly target for paid plans | Status page referenced; no figure on the pages we read |
Requests per minute, concurrency and completed try-ons are different numbers
These three are easy to confuse. Requests per minute is how many new requests the API accepts in a minute. Concurrency is how many can be running at the same moment. Completed try-ons per minute is what actually comes out, and it is limited by both, plus generation time. FASHN documents 100 requests per 60 seconds on its run endpoint with a default concurrency of 6. With six jobs running at once and a job that takes 10 seconds, the steady output is about 36 try-ons a minute until FASHN raises your concurrency, which it offers to do on request.
TryOnCloud documents 300 requests per minute per key and 600 per account. That is a safety ceiling against leaked keys and runaway loops, not a promise of 300 finished images every minute: at a median of about 19 seconds per try-on, sustaining 300 a minute means roughly 95 requests in flight. Real storefronts and apps sit far below that. If you expect sustained volume near it, for a large catalogue batch or a big launch, tell us before you start and we plan capacity with you.
White-label virtual try-on API
TryOnCloud's reseller terms are published in our docs: you may build TryOnCloud try-on into your own product and sell it to your clients under your own brand, with no TryOnCloud branding anywhere and no TryOnCloud account needed by your clients. FASHN grants a commercial-use licence for the images it generates and allows them in your products and marketing; on the pages we read it does not publish white-label or reseller terms, so if you plan to resell, ask FASHN directly and get the answer in writing.
Errors, retries and reliability
Both refuse to charge for failures: FASHN never charges failed requests, and TryOnCloud refunds the credit before the error reaches you. TryOnCloud errors are JSON with a stable code such as NO_CREDITS or a content code, so your app can show the right message. Because the call is synchronous, your retry rule is simple: retry server errors once after a short wait, never retry content or input errors. TryOnCloud targets 99.5% monthly uptime on paid plans, as written in our Terms of Service; FASHN references a status page.
Indian ethnic wear and global garment coverage
Most try-on models are trained and marketed on Western clothing: tops, trousers, dresses. FASHN's documentation describes Try-On v1.6 in exactly those terms, with categories for tops, bottoms and one-pieces, and Try-On Max as covering clothing, shoes, hats, jewellery, bags and other wearable items. Its public pages do not mention sarees, lehengas, kurtas or other Indian ethnic wear. That does not prove it cannot render them; it means that if your catalogue is ethnic wear, you are testing an undocumented case.
Ethnic garments are hard for a reason. A saree is not a shape, it is six yards of fabric that takes its shape from how it is draped: pleats at the waist, a border running along the hem, a pallu over the shoulder with its own pattern. A Banarasi or Kanjeevaram saree carries zari work that must stay sharp. A lehenga has a heavy, flared skirt and a separate dupatta. A dhoti, veshti or pancha is wrapped, not worn. A try-on that flattens the pleats, loses the border or drops the pallu sells a garment the customer will not receive.
TryOnCloud's pipeline is tuned for Indian as well as Western wear, and the same engine runs our in-store try-on kiosks in India. We are explicit about what works best. Stitched garments come through from an ordinary product photo. Draped garments come through best when the product photo shows them draped, on a model or a mannequin, because a flat-folded saree simply does not contain the information about how it falls. Categories we have not tested at scale are listed separately, so you know where to run your own images first.
Works well from a normal product photo
Stitched garments with a clear structure, the category our pipeline handles most reliably: cut, colour, print and embroidery carry through.
- Kurta
- Kurti
- Anarkali suit
- Salwar kameez
- Churidar set
- Patiala suit
- Punjabi suit
- Palazzo suit
- Sharara suit
- Gharara suit
- Lehenga choli
- Bridal lehenga
- Jacket lehenga
- Half saree set
- Langa voni
- Sherwani
- Achkan
- Bandhgala
- Jodhpuri suit
- Pathani suit
- Nehru jacket
- Indo-Western outfit
- Embroidered ethnic gown
- Phiran
- Phulkari kurta
- Bandhani kurta
- Kutch embroidered top
Works best when the product photo shows the garment draped
Draped garments carry pleats, borders and a pallu that a flat lay cannot show. Send the garment worn or on a mannequin.
- Saree
- Kanjeevaram saree
- Banarasi saree
- Pochampally saree
- Paithani saree
- Chanderi saree
- Bandhani saree
- Organza saree
- Silk saree
- Cotton saree
- Kasavu saree
- Mekhela chador
- Nauvari saree
- Dupatta
- Dhoti
- Veshti
- Mundu
- Pancha
- Lungi
Supported, test with your own catalogue first
The same pipeline accepts these, but we have not tested them at scale. Construction varies a lot between makers, so run your own images before launch.
- Abaya
- Kaftan
- Jalabiya
- Thobe
- Dishdasha
- Kandura
- Bisht
- Modest dress with hijab styling
- Kimono
- Yukata
- Hanbok
- Cheongsam
- Qipao
- Dashiki
- Kente cloth outfit
- Scottish kilt
- Traditional tribal and regional dress
- Ceremonial robes
Western and European wear
- T-shirts
- Shirts
- Polos
- Jeans
- Trousers
- Chinos
- Shorts
- Dresses
- Skirts
- Blazers
- Suits
- Waistcoats
- Coats
- Trench coats
- Jackets
- Hoodies
- Sweaters
- Cardigans
- Jumpsuits
- Co-ord sets
- Evening gowns
- Wedding dresses
- Bridal gowns
- Italian tailoring
- French couture-style eveningwear
- Formal wear
- Casual wear
- Activewear
- Kidswear (with consent rules)
Festivals and occasions drive ethnic wear traffic
Ethnic and occasion wear sells in waves around festivals and weddings, which is exactly when a try-on button earns its keep, and exactly when an API must hold up under load.
| Occasion | Garments shoppers try on |
|---|---|
| Diwali, Dussehra, Navratri, Durga Puja | Sarees, lehengas, chaniya cholis, kurtas, sherwanis and festive sets |
| Holi, Ugadi, Sankranti, Pongal, Onam | White and pastel kurtas, kasavu sarees, veshtis, mundus and half sarees |
| Ganesh Chaturthi | Nauvari sarees, Paithani sarees, kurtas and dhotis |
| Eid and Ramadan | Kurta pyjamas, Pathani suits, abayas, kaftans, jalabiyas, thobes, sharara and anarkali sets |
| Christmas and Easter | Dresses, suits, blazers, coats and partywear |
| Weddings and bridal ceremonies | Bridal lehengas and sarees, sherwanis, bridal gowns, suits and guest outfits |
| Cultural and religious festivals worldwide | Kimonos, hanboks, qipaos, dashikis, kilts and ceremonial dress |
FASHN's clear advantage in this section is accessories: Try-On Max documents shoes, hats, jewellery and bags, which TryOnCloud does not focus on. If your catalogue is mainly footwear or jewellery, that weighs in FASHN's favour.
Pricing, integration and developer support
The two price lists use different units, so compare them by the cost of a finished try-on. FASHN sells on-demand API credits at $0.075 each, from a minimum purchase of $7.50 for 100 credits. A Try-On v1.6 image costs 1 credit. A Try-On Max image costs 1 to 5 credits by mode and resolution: 1 credit in fast mode at 1K, 2 in balanced mode at 1K (the default mode), up to 5 in quality mode at 4K. FASHN's FAQ says on-demand credits expire 12 months after purchase and unused purchases are non-refundable.
TryOnCloud charges one credit per try-on, always, at a rate set by the size of your pack: $0.11 from 50 credits, $0.10 from 300, $0.09 from 1,000 and $0.07 from 5,000. Buyers in India pay ₹9 to ₹6.50 in rupees, by card or UPI. Credits never expire and there is no subscription.
| Volume | TryOnCloud | FASHN v1.6 (1 credit) | FASHN Try-On Max balanced 1K (2 credits) |
|---|---|---|---|
| 1,000 try-ons | $90 | $75 | $150 |
| 10,000 try-ons | $700 | $750 | $1,500 |
| 100,000 try-ons | $7,000 | $7,500 | $15,000 |
FASHN at its published on-demand rate of $0.075 per credit; it says higher volumes can contact it. TryOnCloud at the pack rate each volume reaches.
At small volumes FASHN v1.6 is cheaper per image than TryOnCloud's entry pack ($0.075 against $0.11). From 1,000 try-ons the gap closes, and from 5,000 TryOnCloud is cheaper than v1.6 and half the price of Try-On Max at its default mode. The total cost of ownership also includes engineering time: an asynchronous integration needs a polling loop or a secured webhook receiver and somewhere to keep job state, and credits that expire turn a quiet season into lost money.
Support and integration help
FASHN offers email support and a help centre. TryOnCloud offers live chat on the website, WhatsApp, email, and free help with your integration from the team that builds the API. We publish step-by-step guides for Node.js, Python, PHP, Next.js and Shopify Hydrogen, and a no-code Shopify app for merchants who do not need the API at all.
| TryOnCloud Developer API | |
|---|---|
| Endpoint | POST https://www.tryoncloud.com/api/v1/generate, one synchronous call; the finished PNG is the response body |
| Auth | X-API-KEY header, up to 5 named keys per account, each revocable on its own |
| Inputs | Garment as a file, public https URL or base64; person as a file or base64. JPEG, PNG, WebP or HEIC up to 15MB, checked by content |
| Price | $0.11 per try-on from 50 credits, $0.10 from 300, $0.09 from 1,000, $0.07 from 5,000. India: ₹9, ₹8, ₹7.50, ₹6.50 |
| Billing | Prepaid credits, no subscription, credits never expire, failed try-ons refunded, test mode free |
| Rate limit | 300 requests per minute per key, 600 per account (a safety ceiling, not a throughput promise) |
| Speed | Median about 19 seconds, 90% within about 24 seconds (our docs, last 30 days); 120 second maximum |
| Uptime | 99.5% monthly uptime target for paid plans (Terms of Service, section 10) |
| Tooling | TypeScript SDK, MCP server, Markdown docs, llms-full.txt, a contract you can paste into Claude Code, Codex or Cursor |
| Data | Person and garment photos processed in memory, not stored; results not stored unless you enable 7-day storage; never used for training |
| Resale | Build it into your product and sell it under your own brand, no TryOnCloud branding, one named key per client |
| Support | Live chat on the site, WhatsApp (+91 79972 00506), email, and free help with your integration |
Reliability, use cases and the verdict
Choose TryOnCloud when
- You want a shopper-facing try-on button live quickly, with one call and no job handling.
- Your catalogue includes sarees, lehengas, kurtas, sherwanis, dhotis or other Indian and modest wear.
- You are an agency or SaaS reselling try-on under your own brand and need that right in writing.
- You want a flat, predictable price per try-on and credits that never expire.
- You sell in India and want to pay in rupees, or you want chat and WhatsApp support.
- You also need an in-store kiosk or a Shopify app on the same engine and account.
Choose FASHN when
- You need 2K or 4K output, several images per request, or prompt edits such as tucking in a shirt.
- Your catalogue is mainly shoes, bags, hats or jewellery.
- You want model creation, model swap, reframing and other image tools from the same vendor.
- You prefer an asynchronous, webhook-driven architecture for long jobs.
Both are reasonable choices, and the honest way to decide is to run the same ten garments and five phone photos through both and score the results blind. Our guide to choosing the best virtual try-on API has a one-day test plan and scorecard, and the virtual try-on API pricing guide shows how to work out your real cost per try-on. If you are also weighing other providers, see TryOnCloud vs Genlook and TryOnCloud vs fal.ai.
Frequently asked questions
Is TryOnCloud a good FASHN alternative?
Yes, for teams that want one synchronous call that returns the finished image, a flat price per try-on whatever the settings, credits that never expire, explicit rights to resell under their own brand, and strong support for Indian ethnic wear. FASHN is the stronger choice if you need 4K output, several images per request, prompt-based edits or try-on for shoes, bags and jewellery.
How does TryOnCloud pricing compare with FASHN?
FASHN charges $0.075 per credit on demand, and a try-on costs 1 credit on Try-On v1.6 or 1 to 5 credits on Try-On Max depending on mode and resolution. Credits expire after 12 months. TryOnCloud charges $0.07 to $0.11 per try-on by pack size, one credit per try-on, and credits never expire. At 10,000 try-ons TryOnCloud costs $700; FASHN costs $750 on v1.6 or $1,500 on Try-On Max balanced at 1K.
Which API is faster, FASHN or TryOnCloud?
FASHN publishes about 5 to 17 seconds for Try-On v1.6 and about 10 to 55 seconds for Try-On Max depending on mode and resolution. TryOnCloud's docs report a median of about 19 seconds and 90% within about 24 seconds. FASHN v1.6 is faster; TryOnCloud returns the image in the same request, so you do not add polling time on top.
Does FASHN support sarees and Indian ethnic wear?
FASHN's public documentation does not mention sarees, lehengas or Indian ethnic wear; its v1.6 categories are tops, bottoms and one-pieces, and Try-On Max covers clothing, shoes, hats, jewellery and bags. That does not mean it cannot render them, only that it is not documented. TryOnCloud is tuned for Indian and Western wear and documents how to send draped garments.
What rate limits do FASHN and TryOnCloud have?
FASHN documents 100 requests per 60 seconds on its run endpoint with a default concurrency of 6, raised on request. TryOnCloud allows 300 requests per minute per key and 600 per account; for sustained high volume we plan capacity with you before launch.
Can I white-label TryOnCloud or FASHN?
TryOnCloud's terms let you build try-on into your own product and sell it to clients under your own brand with no TryOnCloud branding. FASHN grants a commercial-use licence for generated images; we could not find published white-label or reseller terms on its site, so ask FASHN directly.
Does TryOnCloud have webhooks like FASHN?
No. TryOnCloud's generate endpoint is synchronous: the response is the finished image, so there is nothing to poll and no webhook to receive. FASHN is asynchronous with polling or webhooks, which suits long jobs such as 4K renders and multi-step agent requests.
Build your integration free, then pay per try-on
Test mode costs nothing. From $0.07 (₹6.50) per try-on, credits never expire, failed try-ons refunded.