> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/plugins-and-integrations/web-plugins/convai-embody.md). # Convai Embody Find the setup guides, API reference, and design notes for Convai Embody, which renders a talking 3D body for a Convai character on the web. Convai Embody renders a Convai character as a 3D body in a web page and drives its lip sync, gaze, breathing, and blinking while the character talks. It is built on the [Convai Web SDK](/api-docs/plugins-and-integrations/web-plugins/convai-web-sdk.md) and uses one connection for both, so a page needs a credential and a character ID and nothing else. The current release is space.vars.embody\_version.
Add a 3D character to a React app
Install the package, render a character, and confirm that it speaks with lip sync.		Add a 3D character to a React app
Add a 3D character to a three.js scene
Use the framework-free API in an existing three.js renderer and render loop.		Add a 3D character to a three.js scene
Add a chat widget to a character
Let users type and talk to the character through the same connection.		Add a chat widget to a character
React API reference
Props, defaults, and return values for the React components and hooks.		React API reference
createCharacter reference
Options and the returned character handle for the framework-free API.		createCharacter reference
How Convai Embody works
How a character ID becomes a body, and why motion runs in a fixed order.		How Convai Embody works
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.convai.com/api-docs/plugins-and-integrations/web-plugins/convai-embody.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.