Approve the micro-drama lead's first frame, then render

Create an Avatar video preview, review the first-frame stills, regenerate if needed, then call generate-video. Quality can change at the final step.

5 min readSume
All posts

How do you check how a recurring AI character looks before paying for the full video? Create an Avatar video preview: it generates only the first-frame still stage, you review it, and you call generate-video on the preview id once it is right. The final render tier can still be changed at that last call without a new preview.

This matters for micro-dramas because the lead has to look the same in every episode, and a wrong framing found after the render is a full render wasted.

The four calls

The preview resource has four routes: POST /v1/avatar-video-previews to create, GET /v1/avatar-video-previews/:id to read, POST .../regenerate to refresh stills, and POST .../generate-video to start the real render. The create body is the same as Avatar Video: a script or video_inputs, plus optional product_image, scene, quality, aspect_ratio, title and captions.

When the preview is ready, preview_image_url carries the primary still and scene_previews[] carries one still per input scene. For multi-scene previews with a shared scene, later stills are pose-anchored continuations of the first frame, which is what you want for a lead who must not drift between scenes.

What needs a new preview

Regenerate reuses the stored request and refreshes only the first-frame stills. Structural edits cannot be patched in at generate time.

Preview rules (read 2026-10-07)
ChangeWhat to call
Another take of the same framingregenerate (same avatar_preview id)
Different quality tier for the final rendergenerate-video with quality
Edit script or video_inputsnew preview
Different avatar_handle, scene or aspect_rationew preview

Captions and quality

Caption intent is stored on preview create and applied only at generate-video time; Sume never burns captions into preview stills. An empty body (or {}) keeps the quality you chose at create, and the optional quality field overrides only the final render. Admission, pre-spend, ledger reservation and provider submit all use the effective tier.

The window is the same as direct Avatar Video: an estimated 4-60 seconds inclusive. Media inputs are public HTTPS URLs.

A practical loop

Create the preview while you settle the lead's outfit, background prompt and framing (preview stills do not depend on the quality tier). Regenerate until the still is right. Then call generate-video with quality plus or max for the episode that ships. Read the finished resource with GET /v1/avatar-videos/:id and keep the job id next to the episode number so a later re-render is traceable.

Why the preview step pays

A preview exists so you can reject a face before the expensive render. The first-frame stills show how the lead, framing and any product look, and you can regenerate until they are right. Only then do you call generate-video on the preview id.

Because captions are stored when the preview is created and applied when the video is generated, decide the caption style up front. Changing the quality tier at the last call affects the final render only, not the stills you approved.

  • Reject a bad frame at preview time, not after rendering.
  • Use regenerate for edits that keep the same preview; start a new preview when the script or avatar changes.
  • Record the approved preview id next to the episode.

Cost shape

The final render is billed at the talking-video rate for the chosen tier, and the quality override on generate-video changes only that last step. The docs do not publish a separate preview price here, so read the live number in GET /v1/catalog before budgeting a season.

Sources

Related posts

More in Sume Avatar 1.0

All Sume Avatar 1.0 posts

Written by Sume