Live Demos
This content is not available in your language yet.
Every demo below is a real, running application — not a mockup or a recording — built against the exact API documented in this site. Open the source of any of them to see a working reference implementation.
Two of the demos talk to a live agent, so they ask you for an API key (a sk_… key for a tenant you own, created in the Developers section of the Wetel dashboard or with the generateApiKey mutation). Use a key from a test workspace: these pages run in your browser, so they are for trying the API, not for production (a real integration keeps the key on your server — see Getting Started). If you don’t have access yet, the Workflow JSON Visualizer needs nothing at all, and each demo’s page under UI Components & Widgets walks through its source.
Chat Widget
Section titled “Chat Widget”A minimal text-chat UI wired to a live agent: a single HTML file that shows the whole integration (sdkStart, sdkSendMessage, streamed replies) for you to copy into your own app. It is a reference implementation, not a packaged component.
Needs: an API key and the ID of an agent in that workspace.
Try it: play.wetel.dev/tools/chat-widget/
Avatar SDK Demo
Section titled “Avatar SDK Demo”The embeddable <vai-avatar> web component — a full voice/avatar session in a single script tag, no framework required.
Needs: an API key; an agent ID is optional (blank uses the default agent). Voice needs a microphone and browser permission.
Try it: play.wetel.dev/sdk/demo.html
Workflow JSON Visualizer
Section titled “Workflow JSON Visualizer”Paste a workflow’s raw node/edge JSON and see it rendered as an interactive graph — useful for sanity-checking a graph you’re building programmatically against the Workflows node/edge shape.
Needs: nothing — no login, no key, and nothing is sent anywhere. It runs entirely in your browser.
What it shows: every current node type (including await_reply, approval and sub_agent) with its labelled edges, and a findings list that points at common mistakes: a missing start node, unreachable nodes, a condition without both branches, an approval without its three outcomes, and a router with no default target. It reads the workflow JSON exported by the editor. It is a viewer and checker, not the full validator: the node reference and the publish step in the API remain the source of truth.
Try it: play.wetel.dev/tools/json-to-flow-poc/
See also: Getting Started, UI Components & Widgets for what’s coming as packaged, drop-in components rather than standalone demo pages.