> ## Documentation Index > Fetch the complete documentation index at: https://docs.threetone.in/llms.txt > Use this file to discover all available pages before exploring further. # Web deployment > Prepare browser session access, interface lifecycle, and hosting requirements before a supported widget release. Web deployment places an agent interface in a website. The website needs a released widget or client contract and a working session path, not just a script bundle. ## Prepare the deployment Keep workspace API keys on your server. Define the browser's session-access scope, expiry, allowed origin, and ownership rules against the released runtime. Review [authentication](/agents-platform/configure/authentication/overview) before exposing the interface. The current dashboard widget preview references a legacy script origin or a separate local script server. Signed-token session initiation is also gated. These facts do not establish a production embed URL that customers should copy. ## Integration checks | Check | Required result | | - | - | | Assets | Documented script/package origin, version, and loading policy. | | Session | Supported creation, authorization, expiry, and conversation ownership. | | Permissions | Appropriate microphone access and clear permission-denied states where voice is supported. | | Lifecycle | No duplicate interface after navigation; cleanup releases owned resources. | | Accessibility | Usable keyboard controls, focus, readable transcript, and error announcements. | Use [website-builder preparation](/agents-platform/guides/no-code/overview) for Webflow and WordPress planning, and [UI resources](/agents-platform/resources/ui-components) for component-release requirements. ## Frequently asked questions A verified end-to-end production widget release is not established here. Add the snippet after the script origin, access design, and runtime have been validated. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.