Skip to main content
Design an avatar as a presentation layer around a conversation. Decide who produces speech, who renders video, and who owns each session before selecting a vendor mode.
Threetone has no verified native avatar adapter or working avatar conversation runtime. Vendor session APIs do not remove Threetone’s execution gate. This cookbook produces an integration design and independent media test plan.

​
Before you begin

Have permission to use the selected avatar assets, an approved vendor account, a backend owner, and a clear policy for audio, video, and transcript handling. Use synthetic text or approved sample audio for preparation.
1

Assign media and conversation responsibilities

Record which service owns recognition, responses, speech generation, rendering, and playback. As one vendor example, LiveAvatar’s LITE lifecycle expects an external speech pipeline and renders its audio as video. That mode’s contract is not a Threetone integration.
2

Separate credentials and session identifiers

Review the vendor’s session-token contract. Keep the vendor API key on your backend. Authorize each user before issuing permitted session access, and map application and vendor session IDs explicitly. Never substitute a vendor token for a Threetone credential.
3

Review audio and interruption behavior

Verify the vendor’s required encoding, sample rate, and chunk limits rather than forwarding arbitrary audio. Define how cancellation stops both speech generation and queued playback. Correlate utterances so late chunks from a previous response cannot make the avatar speak after interruption.
4

Plan disconnect and cleanup

Distinguish transport reconnection from creating another billable session. Inspect uncertain start outcomes before repeating them. On user exit or unrecoverable failure, stop the vendor session through its documented lifecycle, release media resources, and clear pending audio.
Keep a text alternative and visible disconnected state. Review privacy boundaries for every service receiving media. Threetone’s stored retention settings do not guarantee deletion of vendor copies.

​
Frequently asked questions

There is no verified avatar configuration field or adapter. The integration needs a released transport and an implemented application boundary.
No. It verifies the tested vendor media path. Threetone session initiation and the complete conversation path require separate release and verification.