HeyGen
Avatar video from a script - HeyGen's stock avatars, a photo avatar, or a digital twin of a real person - through a self-serve API key (X-Api-Key) billed to a prepaid API wallet, plus voices, translation and lipsync. A SHAI-native adapter (avatars.read, voices.read, video.create, video.status, video.fetch) behind the likeness-consent gate: no render before a `likeness` row in the client's rights.md and the consent sentence on this connection; every output lands with aigc: true. Also an OAuth MCP server (trial-scale). On the owner's integrations list (entry 1484), so it keeps its /integrations page.
connectable today
How SHAI connects to it
SHAI talks to it directly, with the key you paste. It is one of the tools SHAI has written up — what it costs, why it matters, what breaks without it — as `heygen` in the tool guide.
What it needs
a key you paste, in Setup or on /connections
Nothing else. It is connectable on this deployment as it stands.
Route read from docs/tools/tools.json (heygen) · verified 2026-09-16 · entry 1484 of the integrations list
Whatever a run does with this tool goes through one door and one approval row: reading is allowed by default, anything that writes, sends or spends stops and asks first, and you can set that per tool on Connections. Plain text for this page: /integrations/heygen/index.md.