Mugshot is a one-tap file, not a prompt you rewrite weekly
/templates/mugshot is a photo in, a clip out. A new generate is a different object.
/templates/mugshot is a photo in, a clip out. A new generate is a different object.
Mugshot swaps your face into a prison mugshot scene and animates it — height marks, camera flash, and all. Input: one photo, required, labelled "Your photo." Estimated cost on the card: about 26 credits (50 at the listed full rate). You do not rewrite a Veo prompt every Friday to chase the same gag. You attach the still the template already knows how to consume. You run it.
A blank generate — "cinematic prison mugshot of me, flash, height chart, 4K" — is a different SKU. Different bill. Different failure mode. The template already chose the stack. Your job is the photo.
One required still, one gag
Run a one-tap AI video template is the named agent job. get_template lists the inputs. start_template_run starts when every required input is a hosted URL, usually a photo attached with the chat + button. A live card tracks the run. get_template_run and cancel_template_run support that card. You do not poll status in most cases. Output is that template's finished video.
Mugshot's image field is required. There is no default face. Starting with a partial inputs object is how you get an error instead of a clip. Attach the still. Then start.
No timeline. No scene list. No "write a three-act booking." The creative choice happened when the template was built. Weekly novelty is a new photo, not a new paragraph. The templates catalog is the rest of that shelf: finger snap, mugshot, the other one-tap formats. Each lists its own estimate before you run.
Rewriting the prison prompt is a different SKU
People open a text-to-video row and paste last week's mugshot prompt with a new adjective. That is a generate. It will invent a face that is not the upload, a height chart that does not match, a flash the still never caught. It will also not be the 26-credit one-tap object. You paid a model to approximate a template you already have.
Forcing Mugshot to be a product ad, a talking brand film, or a multi-scene movie is the other miss. Templates do not take a plot. Create a multi-scene AI movie is a different named job. Cloning a public workflow (recreate_public_template) is a different object again: saved, not auto-run. One-tap is finger-snap / mugshot / red-carpet class: photo in, clip out, no cloned scene graph.
If no template matches, generate. Do not run Mugshot "just to have motion." You will pay the template estimate for a format you will not post.
The stack is already chosen
The template already chose its models. Asking for Veo versus Kling on a one-tap run is how you discover that this job does not expose that switch. If you needed to pick a row per shot, you wanted a generate or a movie, not Mugshot.
Cost is the number on the template card, shown before you run. It is not a per-second cinematic meter you can talk down in the prompt. Cancel an in-flight run with cancel_template_run. Closing the chat is not a cancel.
Use it when the post is the mugshot gag. Skip it when the post is a product, a talker, or a story. Rewrite nothing weekly except the still.
FAQ
Do I have to upload a photo?
Yes. Mugshot's image field is required. Attach one still of the face the gag is about. Defaults are not how this template runs.
Can I change the backdrop or the height marks in the prompt?
Not as a one-tap. The format is fixed. A new generate with a rewritten prompt is a different object — different cost, different face risk, no template card.
Is this the same as saving a workflow I rerun with a new plot?
No. Saved video workflows rewrite a plot around locked characters. Mugshot does not write plots. It applies a format to your photo.
What if I want a different model for the same joke?
Then you are not in this template. Generate, and accept that you are no longer in the one-tap, ~26-credit, photo-in-clip-out path. Pick that on purpose.