Skip to main content

​
Overview

A deployment needs nothing from your stack: the browser loads the element with a deployment id, and Tavus runs the conversation. That makes it a fit for two kinds of tools where you do not control the build.
  • AI app builders such as Lovable, Replit, Bolt and v0 write the code for you from a prompt. Give their agent the embed or widget prompt and your deployment id. In an editor that supports MCP, such as Cursor, Claude Code or Codex, connect the Tavus MCP server instead and the agent creates the deployment itself.
  • Website builders such as Webflow, Framer, Wix and Squarespace have no agent and no build step. Paste the script tag and the element into the site’s custom code.
For both, create the deployment first in the PAL Maker and keep its id at hand. The id is safe to expose; access is controlled by the deployment’s allowed origins, call limits and bot protection, all set in the PAL Maker.

​
AI app builders

Get an embed or widget prompt

Open the prompt for your channel, copy its full text, and paste it into your project’s chat.
1

Paste the prompt

Open your project’s chat and paste the embed prompt for a conversation inside the layout, or the widget prompt for a floating launcher. It tells the agent what the element can do, asks what you want to build, and points it at the examples and this documentation. If you already know which shape you want (a section, a card that expands into a modal, a button that starts the call, a kiosk, a launcher the PAL can navigate from), say so in the same message.
2

Answer its questions

The agent asks where the element goes, which stack to keep, for your deployment id, and whether the PAL has tools for acting on the page. Give it the id as text; it is not a secret and does not need an environment variable or a secrets store.
3

Test on the published URL

Previews in these tools run inside an iframe. The call needs camera and microphone access, which some preview frames do not grant. If the preview stalls on permissions, publish the app and test there. Add the published domain to the deployment’s allowed origins in the PAL Maker if you have restricted origins.

​
Website builders

Copy the snippet for your deployment’s channel. Replace YOUR_DEPLOYMENT_ID with your deployment id; no package install is needed.
Where to paste it: Three things apply to all of them:
  • Publish to see it. Custom code runs on the published site, and often not in the editor’s preview.
  • HTTPS is required. Browsers only allow camera, microphone and WebRTC on secure pages. Published sites on these platforms are served over HTTPS.
  • The element fills its wrapper. Give the embed a box with a definite size, usually aspect-ratio: 16 / 9 on desktop and 9 / 16 on phones. The widget positions itself; it needs no wrapper.
Platform menus move. If a path above no longer matches, search the platform’s help for “custom code” or “code injection”; the snippet itself does not change.

​
Next steps

Build with a coding agent

Connect the Tavus MCP server, or copy the embed or widget prompt.

Examples

Six complete pages to read or copy.

Host communication

Start the call from your own button, read a transcript, answer tool calls.