The check that runs before your credits do.
A failed render already costs nothing — that's handled. The expensive case is the render that succeeds technically and still underperforms, because the actor was wrong for the product. That one bills the full ~2,000 credits for a finished 15s ad. Fit Check scores the pairing first, from the actual pixels of your product image, and gets sharper every time someone logs what really happened.
That last one is the important nuance: the credit refund covers technical failure. A render that completes cleanly but pairs the wrong actor with the product is a success by the system's definition — and still bills in full. Fit Check aims squarely at that gap.
Where this would live
Fit Check isn't a separate product — it's a pre-flight step in front of the tools that already spend credits.
Run it — this part is real
Everything below actually computes. Your image is read pixel by pixel; the score blends a live heuristic with whatever outcomes you log.
Every top model. One check.
Fit Check’s affinity table is built to generalize across whichever model ends up rendering — Seedance, Kling, Veo, or whatever’s next.
Vendor marks are plain lettered placeholders, not the real logos.
Two signals, side by side
Today, actors rank by how often they're used. Fit Check adds a second signal: how well they actually convert per category.
Volume-based ranking rewards whoever is already being picked, which is self-reinforcing — the busy stay busy. An outcome-based score is a second ladder: an actor who converts unusually well for skincare can surface for skincare briefs without first winning on raw volume. For licensed actors paid per use, that's a route to being cast on evidence rather than on incumbency.
70+ languages, one affinity table.
The category × actor-type affinity signal is language-agnostic today — in production it would need to account for regional performance differences too.
What's real vs what's a stand-in
A prototype is only useful if it's clear which parts would survive contact with production.
getImageData and averaged into an HSL color — genuine computation, not decoration.- Free failed renders — wasted spend is already treated as a problem worth solving. Just not this kind of waste.
- Informal per-actor fit tags on the casting site — actor-category fit is already in the product's vocabulary, only unmeasured.
- API access on Team and Scale — exactly where a pre-flight scoring call would sit.