Virtual try-on API pricing & credits

How billing works: you buy credits, then spend them per successful generation. Credits are drawn from one unified balance that works across every provider the gateway routes to. Billing top-ups are handled by Stripe on the Billing page.

Credit basics (from product docs)

• Unit: 1 credit ≈ $0.001 (as stated on Billing).
• Charge: per successful request, in credits.
• Typical costs: most models cost 1 credit per request; gpt-image-1 costs 2 (see homepage FAQ / Models catalog for live slugs).
• Balance check: GET /api/v1/credits or the Credits console.

Where to see exact per-model costs

Model slugs and credit pricing live on the Models page and in the API docs. Use "auto" when you want the gateway to pick any capable model. Rankings at /rankings/clothing help you compare quality on shared inputs before you lock a default slug.

Buying credits

1. Sign in (GitHub or email magic link).
2. Open Billing — Stripe pricing table loads for your session.
3. Confirm balance on Credits.

Buying credits ties the purchase to your account, so a browser session is required for Stripe checkout. API usage itself uses the Bearer tryon_ key.

What this page is not

This is an overview that links the live billing and docs surfaces. Pack amounts and the Stripe table can change; always confirm on Billing and Models rather than hard-coding prices into your app.

Frequently asked questions

How is pricing calculated?

Per successful request, in credits, drawn from one unified balance across every provider. Most models cost 1 credit per request; gpt-image-1 costs 2. Check your balance at GET /api/v1/credits.

What does 1 credit equal in USD?

On the Billing page, TryOn-API.com states 1 credit ≈ $0.001. Confirm current packs on Billing via Stripe.

Do I need a separate bill per provider?

No. The gateway unifies credits so you are not maintaining separate Kling, Gemini, OpenAI, and FAL billing relationships for try-on traffic.

---

See also the machine-readable llms.txt and full API reference.