Install the widget
One script tag puts a character on your website, in a corner of every page, ready to talk face to face.
The website widget is a character in the corner of your site, like a support chat, except visitors talk to it out loud and see its face. One tag installs it; everything else (which character, its look, its words) comes from the deployment, so you change it without touching your site again.
The tag
Paste it before </body>, or in <head>, on every page where the character should appear (or once, in your site's layout):
<script async src="https://talk.madein10.com/widget.js" data-key="pk_live_…"></script>That's all a site needs. data-key is the deployment's publishable key; the tag's other attributes are optional and listed in Attributes.
Names that will change
The product has no name yet. talk.madein10.com and the widget's global, TalkWidget, are placeholders that work today; they will change when the product has its name.
Get a key: make a deployment
A deployment puts one character on 1 to 20 sites. Make one on the dashboard's Deployments page (or ask your assistant through the MCP server); it answers the tag with the key in it. The key is shown once: if you lose it, give the deployment a new key. The old one keeps working for a grace time you choose (up to a week), so you can update the site first.
- Sites. Each is an origin, like
https://example.com. A site served both with and withoutwwwneeds both. On any other site the widget stays hidden. - Caps. Visitors' calls are charged like any call, so every deployment has limits. You can change them; anything you leave out takes its default.
| Cap | Default | What it limits |
|---|---|---|
max_call_seconds | 180 | The longest call from the website |
per_visitor_per_day | 3 | Calls one visitor may start in a day |
at_once | 2 | Calls through this deployment at the same time |
per_day | 50 | Calls a day through this deployment, all visitors together |
daily_spend_usd | none | Stop taking calls for the day once this much was charged |
- Busy message. When a cap or one of our limits is reached, the widget says your deployment's busy message (up to 200 characters of plain text), or ours: "busy right now".
- A note for your team. A deployment can carry a description (up to 500 characters). Visitors never see it.
Let visitors choose a character
A deployment shows one character, but it can also let visitors pick who to talk to: on the dashboard, open the deployment's Settings and tick Characters visitors can choose. The deployment's own character stays the default and comes first; the others are any of your characters, up to 20 more.
The widget's panel then shows their faces with their names above the language. The visitor's pick changes the face, the name on the call button and the panel's header, and the widget remembers it for the visit. Everything else about the deployment stays the same:
- The limits are the deployment's. Calls at once, calls a day per visitor, calls a day in all and the daily spending cap count every call through it, whichever character it's with. Offering five characters doesn't give a visitor five times the calls.
- Each call is the chosen character's own: its face, voice, instructions and knowledge, and it's billed like any call with that character. The longest call is the deployment's cap or the character's own, whichever is shorter.
- Only your characters, only the ones you listed. The widget can only start the deployment's own character or one on its list; a deleted character drops out of the list by itself.
/v1 has no deployments endpoint yet: deployments are made and changed in the dashboard or through the MCP server. Their look and words can also be set over /v1 (see Appearance).
Test deployments
A test deployment (pk_test_…) works like a live one, but its calls are test calls: at most 60 seconds each, 20 a day for your organization, never charged. Try your site with one first, then make the live deployment.
What it is
- Plain JavaScript, no dependencies, about 8.9 KB gzipped with all six launcher styles and the icons.
- One shadow root under one element at the end of
<body>, fixed to the window. Your site's CSS can't reach it and it never moves your page: no layout shift, no long tasks, about 0.6 ms of script on your page. - One global,
TalkWidget, for the JavaScript API. - Its styles are a constructed stylesheet, which a Content-Security-Policy without
'unsafe-inline'allows (Security).
What it loads, and when
Before anyone clicks, the page loads three things: the loader, the deployment's settings, and the launcher's picture (about 12 KB).
- The idle video (about 300 KB) loads only when the teaser pops up or a mouse points at the launcher. Never on Save-Data, a 2G connection or with reduced motion; paused in a hidden tab and while the panel is open.
- A preconnect to our address when the teaser shows or on hover.
- The call's page loads in an iframe the first time the panel opens (
allow="microphone; camera; display-capture; fullscreen; autoplay"). Closing the panel removes it, which ends the call. - A font for Arabic script (46 KB) only when the widget's language is Persian or Arabic.
- Your own launcher icon only for a style that shows an icon (Icons).
What visitors see
- The launcher, in one of six styles:
face(the character's face in a circle, the default),face_label(the face and a label),card(a small video card with the name and a Talk button),pill(an icon and a label),icon(a round icon button) ortab(a slim tab on the window's edge that slides out on hover). Phones can have their own style; a card shows as a face on a phone unless you choose otherwise. - The teaser: a speech bubble that pops up over the launcher after a few seconds (4 by default), rotates its messages, and closes with a small ×. You choose how often it comes back and on which pages.
- The panel: on a desktop, a 400 × 680 panel over the launcher's corner (shorter in short windows). On a phone (640 px wide or less, or a short touch screen), a full-screen sheet that respects the safe areas, locks the page behind it, and fits what the keyboard leaves visible. It closes with its ×, Esc, the back button, or a swipe down on its header.
- Keyboard and focus: focus moves into the open panel and stays there, and comes back to the launcher when it closes.
- Before a call: the face, then a short step: the language (searchable, each in its own name and script, the page's language first), a first name (optional), and Call. The call itself starts only from the visitor's click inside the panel.
Every style, colour, word and rule is yours to set: see Appearance.
Sites that change pages without reloading
Nothing to do. On sites built with client-side navigation (Next.js, React Router and the like), the widget checks the address and its place in the page every second. The panel and its call survive a route change, and the tag running twice still makes one widget.
It always says it's an AI
Visitors are told they're talking to an AI when the conversation starts: the open panel shows "AI" next to the character's name, the call page says the character is an AI and not a person, and the character says so in its first sentence. See AI disclosure.