VEED Avatars is VEED's talking-head & lipsync video model on Versely. This page is its structured prompting reference: the 1 parameters its schema actually exposes, the talking-video technique that applies to it, copy-ready templates.
Everything here is grounded in the same sources Versely's agent reads — the model's input schema. Where a line is general craft advice rather than a documented fact about VEED Avatars, the page says so.
What VEED Avatars wants
The exact input surface, from the same schema the Versely agent fetches with get_model_input_schema before every generation.
| Parameter | What it does | Values |
|---|---|---|
textreq | Script for the avatar to speak | string |
- — Verified against fal.ai/models/veed/avatars/text-to-video — only `avatar_id` and `text` are valid fields; voice_id/language/aspect_ratio are NOT in docs
Technique that applies here
Lipsync/avatar/audio-driven: text or audio input, delivery and framing controls
- Three different input shapes share this family, and figuring out which one your model uses tells you what 'the prompt' even means: text-is-the-script (HeyGen Avatar V3, VEED Avatars — your text becomes the spoken words), audio-drives-it (Kling Avatar Pro, LTX 2.3 Audio to Video, Wan 2.2 Speech to Video — the words come from your uploaded audio_url; any prompt text only shapes the visual scene/motion around it), or pure re-timing with no prompt field at all (Sync Lipsync 2.0, VEED Lipsync, VEED Fabric 1.0, Sync React 1).
- Kling Avatar Pro's input.prompt is required (max 5000 chars), but the schema describes it as a 'Motion/scene description,' not dialogue — writing your script into it does nothing, since input.audio_url is what the avatar actually lip-syncs to. Wan 2.2 Speech to Video has the same audio-drives-it shape but makes its equivalent prompt field optional.
- VEED Avatars' schema is narrower than sibling avatar products: only avatar_id and text are valid fields, per the schema's own constraint note — voice_id, language, and aspect_ratio are explicitly documented as not supported, even though HeyGen Avatar V3 does expose a separate voice ID and resolution control.
Copy-ready templates
Replace the bracketed slots; each template says when it's the right shape.
voice.prompt: "[SCRIPT — what the avatar says, written as natural spoken sentences]" · character.avatar: [AVATAR ID], voice.voice: [VOICE ID], resolution: [720p/1080p], output_language: [LANGUAGE CODE if dubbing]
Use when: Scripting a HeyGen Avatar V3 talking head from text — no separate audio file needed, HeyGen generates the voice.
text: "[SCRIPT — what the avatar says]" · avatar_id: [PRESET AVATAR ID]
Use when: Scripting VEED Avatars — remember only avatar_id and text exist here; there's no separate voice, language, or aspect_ratio field to set.
How the Versely agent does this automatically
You can use this page by hand, or let the agent apply the same knowledge. Four real mechanisms — no more, no less:
get_model_input_schema— before generating, the agent looks up VEED Avatars's exact input fields, required fields, allowed values, defaults, and min/max bounds. The parameter table above is that same surface.- The prompt enhancer's family rules — 12 per-family rewrite rules (this model's family isn't one of the 12, so only general enhancement applies) shape how a rough prompt gets rewritten.
- The per-provider speech guide — for TTS scripts, the agent follows a provider-specific tag scheme — not relevant to this model, but it's why voiceover scripts come out marked up correctly.
expand_movie_scene— in movie flows, brief scene ideas are rewritten into detailed cinematic descriptions before generation.
Mistakes that waste generations
- Typing your script into Kling Avatar Pro's or Wan 2.2 Speech to Video's prompt field and expecting the avatar to say it — both prompts are scene/motion descriptions; the spoken words come only from audio_url.
- Writing a phrase like 'a little sad but trying to smile' into Sync React 1's emotion field — the schema requires exactly one word from a fixed 6-value enum (happy/angry/sad/neutral/disgusted/surprised); anything else is invalid.
- Assuming VEED Avatars supports a separate voice or language selector the way HeyGen Avatar V3 does — its schema is explicitly limited to avatar_id and text; voice_id, language, and aspect_ratio are documented as not valid fields.
Frequently asked questions
Does VEED Avatars support negative prompts?+
No — VEED Avatars's published schema has no negative_prompt parameter. Exclusions have to be phrased positively inside the main prompt, or dropped.
How does the Versely agent know VEED Avatars's parameters?+
Before generating, the agent calls its get_model_input_schema tool, which looks up the exact input fields, required fields, allowed values, defaults, and min/max bounds for the model. Nothing on this page is guessed — it is the same schema surface those tools read.
Related prompting guides
Generate with VEED Avatars
VEED Avatars is live in Versely — paste a template above, or just describe what you want and let the agent map it onto the schema for you.