Skip to main content
A single engine value resolves to the right product based on the avatar look type — mirroring how avatar_iv already serves both photo and video avatars:
Look typeResolves to4K output
digital_twinDigital Twin✓ Supported
photo_avatarPhoto Avatar✗ Not available (1080p max)

​
Supported avatar types

digital_twin, photo_avatar.

​
Unsupported parameters

motion_prompt and expressiveness are not supported with this engine. Include them only with Avatar IV.

​
Checking eligibility

Avatar III is opt-in and only available for looks that support it. Fetch the look and check supported_api_engines before requesting it: 
GET /v3/avatars/looks/{look_id}

{
  "id": "lk_abc123",
  "name": "My Photo Avatar",
  "avatar_type": "photo_avatar",
  "supported_api_engines": ["avatar_iv", "avatar_iii"]
}
Avatar III is only available if "avatar_iii" appears in supported_api_engines.

​
Example

{
  "type": "avatar",
  "avatar_id": "YOUR_PHOTO_AVATAR_LOOK_ID",
  "script": "Hello from Avatar III.",
  "voice_id": "YOUR_VOICE_ID",
  "resolution": "1080p",
  "engine": { "type": "avatar_iii" }
}
For pricing, see Self-Serve Pricing and Enterprise Pricing. To compare engines, see Models.

​
Legacy Avatar III (v1/v2)

A separate, older Avatar III engine remains available to existing customers through the legacy v1 and v2 endpoints (for example, the Studio API). That engine:
  • Is not offered on the new developer platform. It will not be available through POST /v3/videos, and new integrations cannot opt into it.
In short: the legacy Avatar III on the v1/v2 endpoints and the Avatar III engine on the v3 API are two different engines. Existing customers can keep using the legacy engine on v1/v2 at legacy pricing; all new work on the developer platform should use the v3 engines. Legacy Avatar III pricing is unchanged.