1. Preparing the profile
Set the avatar name and description, then choose a style. For a team kit, organise the members’ profiles before generating. These steps prepare the image; they do not train a model on a person’s face.
The 4avatars workflow covers avatar profiles, styles and image variants, team kits and displaying the image on a website. Below is what you can check in the panel and what depends on an external provider.
Set the avatar name and description, then choose a style. For a team kit, organise the members’ profiles before generating. These steps prepare the image; they do not train a model on a person’s face.
Check which provider will run the request. The local one demonstrates the workflow with a geometric illustration. An AI result requires an external image provider and its credentials to be configured.
Check the prompt, the dimensions and the number of variants requested, follow the run status and pick the image you want from the available results. A request can fail; there is no guaranteed generation time.
Issue an embed token for a profile or kit, allow the website origin and add the HTML snippet to your page. Check the image on mobile and desktop. Revoking the token stops access through that embed.
The local provider creates a geometric illustration, not a photorealistic AI portrait. External image generation depends on provider configuration, credentials and availability. Animation and voice rendering are unavailable in the current workflow; there is no verified script-to-video, lip-sync or SCORM export.
Yes. The HTML snippet has to be added to the page, and the website origin must be allowed for the token. A CMS or a security policy can restrict scripts; test the embed on the real site.
Not in the image workflow described here. The animation endpoint responds that rendering is not implemented. It does not include video generation, lip-sync, dubbing or SCORM export.
Product scope checked on .
Check the workflow with us