Developer API comparison
TryOnCloud vs Genlook: 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.
Genlook started as a Shopify try-on app and now sells a developer API as well. TryOnCloud did the same in the other direction: a developer API first, with a Shopify app and an in-store kiosk on the same engine. Both are capable, both have mock modes, MCP servers and TypeScript SDKs, and both refund failed try-ons. They differ in how the API is shaped, how far you may take it commercially, where each is strongest on garments, and price. On price and published speed Genlook is ahead, and we say so below. This page is for developers deciding between them.
The short answer
Developer API compared: stateless versus cached
Genlook's virtual try-on API offers two call styles. POST /try-on/sync holds the request open until the result is ready (Genlook says usually about 10 seconds, waiting up to 90), and POST /try-on starts a job you poll at GET /generations/:id or receive through generation.completed and generation.failed webhooks. The shopper photo is uploaded once to POST /images/upload and reused by id, and products are cached by an externalId: Genlook says the first try-on of a product analyses it, and later calls that send only the id skip that step and return faster. Batches of up to 500 try-ons cover catalogue work.
TryOnCloud's API is stateless. POST /api/v1/generate takes the garment (as a file, a public URL or base64) and the person (as a file or base64) in one synchronous request, and the response body is the finished PNG. Nothing is uploaded ahead of time, nothing is cached on our side, and the shopper's photo is never written to storage. There are no image ids or product ids to manage and nothing that expires.
| TryOnCloud | Genlook | |
|---|---|---|
| Call styles | Synchronous: POST /api/v1/generate returns the PNG | Synchronous POST /try-on/sync (waits up to 90s), or async POST /try-on with polling or webhooks; batches of up to 500 |
| State | Stateless: nothing uploaded or cached, photos never stored | Reusable uploaded images (kept 1, 3 or 7 days) and cached products by externalId |
| Auth | X-API-KEY, up to 5 named keys | x-api-key, one key per app or environment, optional monthly credit limit |
| Inputs | Garment file, URL or base64; person file or base64; 15MB | Person as an uploaded image; products inline (images, title, description) or by cached externalId; 10MB; 1 to 4 products |
| Multi-product outfits | One garment per request | Up to 4 products in one try-on (2 credits) |
| Accessories | Focused on clothing | Shoes, glasses, jewellery, watches, bags, hats, wigs and more |
| Output | One PNG, about 1K | Result image URL; 2K for 1 extra credit |
| Retries | Synchronous; failed try-ons refunded | Idempotency-Key header; a retried try-on is never charged twice |
| Test mode | Free mock mode | Free mock mode |
| SDK and AI tooling | TypeScript SDK, MCP server, Markdown docs, llms-full.txt | TypeScript SDK, OpenAPI 3.1 spec, MCP server, example Next.js repo |
Where Genlook's design is ahead
Genlook documents features TryOnCloud does not offer today: an asynchronous mode with webhooks, product caching that speeds up repeat try-ons, batches, multi-product outfits in one generation, accessories from shoes and watches to wigs and coloured contact lenses, an optional 2K result, idempotency keys for safe retries and an OpenAPI 3.1 spec you can generate clients from. If your product needs those, they are real advantages.
Where TryOnCloud's design is ahead
TryOnCloud's advantage is a stateless design with privacy by default. There is no upload step, no image id or product id lifecycle to manage, and no shopper photo stored anywhere, which keeps your privacy notice short and your integration small: one request in, one image out. Our docs also ship a ready-made contract for AI coding assistants, so Claude Code, Codex or Cursor writes a correct integration in one pass, and our MCP server lets the assistant run real try-ons while it works.
REST API, white-label resale and scalability
For SaaS products, agencies and platforms, capacity and commercial rights decide more than the endpoint does.
| TryOnCloud | Genlook | |
|---|---|---|
| Rate limit | 300 requests per minute per key, 600 per account | 429 when more than 20 try-ons run at once on an account |
| Webhooks | Not needed: synchronous | generation.completed and generation.failed |
| White-label | Resell under your own brand, no TryOnCloud branding, named key per client | Your logo on results; EU AI Act label can be turned off; reseller terms not published |
| Data | Photos processed in memory, not stored; results not stored by default | Uploads kept 1, 3 or 7 days; delete all images of one user in one call |
| Uptime | 99.5% monthly target for paid plans | No figure on the pages we read |
| Enterprise | Custom SLA on request; capacity planned with you | Custom plans from $1,000 a month; startup programme |
Requests per minute, concurrency and throughput
These are different limits. Genlook limits concurrency: more than 20 try-ons running at once on one account returns 429 RATE_LIMITED. At its published median of about 8 seconds, 20 concurrent jobs produce roughly 150 finished try-ons a minute. TryOnCloud limits the request rate: 300 requests per minute per key and 600 per account. That is a ceiling against leaked keys and runaway loops, not a promise of 300 finished images a minute; at our median of about 19 seconds, 300 a minute means about 95 requests in flight. For sustained volume at that level, such as a catalogue batch or a national sale, tell us before launch and we plan capacity with you.
White-label and reseller rights
Genlook supports branding on results: you can add your logo, and turn off its EU AI Act label per request. On the pages we read it does not publish terms for reselling the API to your own clients. TryOnCloud's reseller terms are public: you may build try-on into your own product and sell it under your own brand, with no TryOnCloud branding and no TryOnCloud account for your clients. Give each client a named key, see its usage and revoke it without affecting the others. If resale is your business model, get the right in writing from whichever vendor you choose.
Data handling
The two take different approaches. Genlook stores uploads for 1, 3 or 7 days, which makes image reuse possible, and lets you delete every image of one user in a single call. TryOnCloud never writes the person or garment photo to storage: both are processed in memory and the result is returned to you, not kept, unless you ask us to enable 7-day result storage. Neither uses your images to train models.
Indian ethnic wear and global garment coverage
Genlook's product pages list dresses, outerwear, denim and knits, streetwear, swimwear, activewear, bridal, plus size and football kits, and its API covers many accessories. Its benchmark of ten try-on APIs included a silk saree and an abaya, and Genlook reports that nine of the ten handled the saree well. It does not present Indian ethnic wear as a product category of its own.
For an Indian brand, or any store selling to the Indian diaspora, ethnic wear is not one garment in a benchmark, it is most of the catalogue: a Kanjeevaram saree for a wedding, a lehenga for a sangeet, a sherwani for the groom, a veshti for Pongal, a kasavu saree for Onam. Each has structure a generic model can lose: the pleats and pallu of a saree, the zari border of a Paithani, the flare of a lehenga skirt, the wrap of a dhoti or mundu, the embroidery on an Anarkali. TryOnCloud is tuned for these garments, and the same engine runs our try-on kiosks in Indian stores, where shoppers hold up real sarees and lehengas to a camera.
We are specific about what works. Stitched garments come through from an ordinary product photo. Draped garments come through best when the product photo shows them draped, because a folded saree does not contain the drape. Categories we have not tested at scale are listed separately so you test those 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)
Festive peaks
Ethnic, modest and occasion wear sell in waves around festivals, so plan capacity and credits ahead of these dates.
| 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 |
Pricing, integration and developer support
On price, Genlook is cheaper, and the gap is large at volume. Genlook's API is $0.04 per try-on pay as you go, in credit packs from $5 that never expire. Its monthly plans go lower: Starter at $20 a month includes 1,000 try-ons then $0.02 each; Growth at $99 includes 6,000 then $0.018; Scale at $300 includes 20,000 then $0.015. New accounts get 10 free credits. TryOnCloud is $0.11 per try-on from 50 credits, $0.10 from 300, $0.09 from 1,000 and $0.07 from 5,000, with no subscription and credits that never expire.
| Volume in a month | TryOnCloud (packs) | Genlook pay as you go | Genlook cheapest plan |
|---|---|---|---|
| 1,000 try-ons | $90 | $40 | $20 (Starter, 1,000 included) |
| 10,000 try-ons | $700 | $400 | $171 (Growth: $99 + 4,000 × $0.018) |
| 100,000 try-ons | $7,000 | $4,000 | $1,500 (Scale: $300 + 80,000 × $0.015) |
Genlook plan totals include the monthly fee and its published overage rate; plans renew monthly and their allowance resets. Prices before tax.
So why pay more? Price per try-on is one line of the total cost of ownership. TryOnCloud's price buys a simpler integration (one call, no job handling), a higher request ceiling, published resale rights, rupee billing with UPI for Indian businesses, the ethnic wear tuning above, and direct support over live chat and WhatsApp with free help on your integration. If none of those matter to your product, Genlook's price is hard to beat, and you should take it.
Integrations and support
Genlook offers apps for Shopify, WooCommerce and PrestaShop, a Klaviyo integration on its Pro plan, email and in-app chat support and a Discord community. TryOnCloud offers a Shopify app, an in-store try-on kiosk, a Klaviyo integration, signed lead webhooks for any CRM, step-by-step guides for Node.js, Python, PHP, Next.js and Shopify Hydrogen, and support by live chat, WhatsApp and email.
| 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 |
Moving an integration from Genlook to TryOnCloud
If you already call Genlook's sync endpoint, the move is small. The upload step goes away, because TryOnCloud takes the garment and the person in the same request: send the product image as a public URL in garment_url and the shopper photo as a file or base64. Product ids are not needed, since nothing is cached between calls. If you use Genlook's asynchronous jobs or batches, keep that flow for now: TryOnCloud is synchronous only today. Map Genlook's error code values to ours in one switch: a missing or unreadable image, a content rejection, no credits, and rate limiting each have their own code in our error reference. Keep your mock-mode tests, since both APIs support a free mock flag, and run them against TryOnCloud before you switch traffic. Most teams can make the change in an afternoon and run both side by side for a week before turning one off.
Reliability, use cases and the verdict
TryOnCloud targets 99.5% monthly uptime on paid plans, written into our Terms of Service, with custom SLAs for enterprise. Genlook does not state an uptime figure on the pages we read. Both refund failed try-ons, so neither charges you for an outage.
Choose TryOnCloud when
- You want a stateless integration: one call per try-on, no uploads, ids or caches to manage.
- You sell Indian ethnic or modest wear, or serve the Indian diaspora.
- You are an agency or SaaS reselling try-on under your own brand.
- You need a high request ceiling without a concurrency cap of 20.
- You want to pay in rupees with UPI, or want chat and WhatsApp support.
- You also need an in-store kiosk on the same account and engine.
Choose Genlook when
- The lowest price per try-on is the deciding factor, especially above a few thousand a month.
- You need multi-product outfits, accessories, or a 2K option.
- You need asynchronous jobs, webhooks, batches, product caching or idempotency keys.
- You want ready apps for WooCommerce or PrestaShop.
Genlook's benchmark ranks Genlook first, as a vendor benchmark usually does, and ours would too. The answer that counts comes from your own catalogue. Our guide to choosing a virtual try-on API has a one-day test plan and a scorecard. For the Shopify app side of this comparison, see our Genlook alternative guide. Also compare TryOnCloud vs FASHN and TryOnCloud vs fal.ai.
Frequently asked questions
Is TryOnCloud a good Genlook alternative?
Yes, if you value a stateless call with nothing to upload or cache, photos that are never stored, a higher request ceiling (300 per minute per key), explicit rights to resell under your own brand, rupee pricing with UPI in India, and strong Indian ethnic wear support. Genlook is cheaper per try-on on its monthly plans and publishes a faster median time, so if lowest price and speed are all that matter, Genlook is a strong choice.
Which is cheaper, Genlook or TryOnCloud?
Genlook. Its API costs $0.04 per try-on pay as you go, and $0.015 to $0.02 per try-on on monthly plans from $20 a month. TryOnCloud costs $0.07 to $0.11 per try-on with no subscription. Both never expire prepaid credits and both refund failed try-ons.
Which API is faster?
Genlook publishes a median of 8.2 seconds on its developer page (other Genlook pages say about 8 to 10 seconds). TryOnCloud's docs report a median of about 19 seconds. Both offer a synchronous call; Genlook says repeat try-ons of a cached product come back faster.
Does Genlook have a REST API?
Yes. Genlook offers a self-serve REST API with a synchronous try-on endpoint (POST /try-on/sync, waits up to 90 seconds), an asynchronous one with polling or webhooks, reusable image uploads, cached products and batches of up to 500. It has a TypeScript SDK, an OpenAPI spec, idempotency keys, a free mock mode and an MCP server.
Can I resell Genlook or TryOnCloud under my own brand?
TryOnCloud's terms allow building try-on into your product and selling it to clients under your own brand, with no TryOnCloud branding. Genlook lets you add your logo to results and turn off its EU AI Act label per request; we could not find published reseller terms, so ask Genlook directly.
Which is better for sarees and Indian ethnic wear?
Test both with your catalogue. Genlook included a silk saree in its own benchmark of ten APIs and said nine of ten handled it well, without listing Indian wear as a product category. TryOnCloud is tuned for Indian and Western wear, documents how to photograph draped garments, and runs the same engine in in-store kiosks in India.
What are the rate limits?
Genlook returns 429 when an account has more than 20 try-ons running at once. TryOnCloud allows 300 requests per minute per key and 600 per account, and plans capacity with you for sustained high volume.
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.