60-second talking head: Fabric $6.00 or $11.25, Avatar Standard $11.04

A 60-second talking video costs $6.00 on VEED Fabric 1.0 at 480p, $11.25 at 720p, and on Sume Avatar Video $11.04 Standard, $14.70 Plus or $33.00 Max. Fabric 480p is the cheapest, and Standard Avatar Video is 21 cents cheaper than Fabric 720p.

The five prices

Per second: Fabric $0.10 (480p) or $0.1875 (720p); Avatar Video $0.184, $0.245, $0.55. Pricing page, as of 2026-10-08.

What each includes

Fabric prices the audio you supply: audio_url (Sume-hosted, under 10 MB), a measured duration_seconds, and one visual source, either the image_url of a posed still or an avatar_handle. You pay for the voice track separately wherever you produce it.

Avatar Video takes a script and produces the speech and performance in one job. It also supports product images, scenes and inline captions at no separate caption charge.

• Need a specific recorded voice: Fabric.
• Need a script-to-video presenter: Avatar Video.
• Over 60 seconds: Fabric up to 300 s, or several Avatar jobs.

The honest gap

The prices cover different work, so a 21-cent difference between Fabric 720p and Avatar Standard is less important than whether you already have audio. If you do not, the cost of producing the voiceover has to be added to the Fabric column.

Practical notes

Media inputs. Any media field, whether product_image, scene.image_url or an avatar image_url, must be a fetchable public HTTPS URL. Sume rejects localhost, private-network and non-HTTPS addresses before it submits anything, so a broken link fails fast instead of consuming a render. Host reference images where Sume can fetch them and keep them available until the job finishes.

Reading results. A completed result can include public media.sume.com video artifacts, and for avatar videos also public-safe preview fields such as preview_image_url and scene_previews. You can list or read finished videos with GET /v1/avatar-videos and GET /v1/avatar-videos/{id}. Store the job id and the video id together so a billing line can be traced back to a creative.

Reusable avatars. An avatar is created once, for a flat $0.95, and then referenced by its avatar_handle on every later request. Sume normalizes a leading @ away and stores the handle without it. Treat the handle as a stable identifier in your own system, and keep one record per handle noting who the avatar represents and what it may be used for.

Job lifecycle. Every Sume avatar request is job-backed. You submit, store the job id, and poll GET /v1/jobs/{id}/status until it completes, then read GET /v1/jobs/{id}/result. The shared lifecycle also lets you wait with sync or subscribe mode for a limited time instead of polling, and the result carries Sume-hosted artifacts rather than provider URLs, so you never handle a provider queue id. Plan your client around the job, not around a single blocking response.