Give every visitor an assistant that reads and works on your pages.

How it works

1. Your page loads the widget. The script tag loads embed.js from sites.webbrain.one. It adds the launcher and the chat panel to the page, inside its own shadow root so your styles and its styles don't mix.
2. The visitor asks. The widget reads the page the way the WebBrain browser extension does: as an accessibility tree of headings, text, links, fields and buttons. Visitors install nothing.
3. The server asks the model. The widget sends the question and what it read to sites.webbrain.one, which adds your site's settings and instructions and asks the AI model what to do next.
4. The widget does it, on the page. The model either answers or asks for a tool: read more of the page, scroll, do exact math, or, in Ask and act, type and click. The widget runs the tool in the visitor's browser and sends the result back. A question takes a few of these steps; at most 5 in Ask and 8 in Act.

The widget is built from the extension's own code, so it reads pages and acts on them the same way. Its source is in the WebBrain repository under GPL-3.0, and every copy of embed.js links to the exact commit it was built from.

Add it to your site

1. Sign in at sites.webbrain.one. Enter your email and open the sign-in link we send you. The link works once and expires in 15 minutes. There is no password.
2. Add your site. Give it a name and its address, for example example.com. The address matters: the assistant answers only on that domain (see Limits).
3. Copy the script from the Install tab and paste it before </body> on every page where you want WebBrain, or into your CMS's custom code setting.
4. Publish. The launcher appears in the corner you chose. Later changes in the dashboard reach your site without touching the script.

<!-- WebBrain for websites -->
<script src="https://sites.webbrain.one/embed.js"
        data-site-id="site_…"
        defer></script>

Your site ID is in the dashboard under Settings. It never changes. Deleting a site there stops its script at once.

Ask only, or Ask and act

On the Behavior tab you choose what WebBrain may do on your site. The server enforces it, whatever the page or the visitor asks for, and the widget runs only the tools of the mode it is in.

Act works as the visitor, in their browser, on the page they have open: whatever they could click, it can click. Choose Ask only unless filling forms or walking through steps for visitors is the point.

Behavior settings

Starter questions

On the Starter questions tab, add one-click questions that show when visitors open the assistant. Each has a label (what the button says), a prompt (what is actually asked) and a mode. Act questions are turned off while the site is set to Ask only.

Good starter questions are specific to the page: “Summarize this plan comparison”, “Which plan fits a team of 5?”, “Fill in the demo request for me”.

Appearance

Buttons and the JavaScript API

Any element on a page that loads the script can start a question. Add the attribute to a button or link:

<!-- Asks right away -->
<button data-webbrain-ask="Summarize this page in 3 points">Summarize this page</button>

<!-- Puts the request in the composer; the visitor sends it -->
<button data-webbrain-act="Fill in the contact form for me">Fill it in for me</button>

data-webbrain-act only fills in the composer, because any markup on a page, including comments and posts your users wrote, can carry the attribute. The visitor decides to send it. Clicks made by WebBrain itself never start a run.

From your own code, window.WebBrain is ready once the script has loaded:

WebBrain.open();      // open the panel (also: close(), toggle())
WebBrain.ask('Summarize this page in 3 points');
WebBrain.act('Fill in the contact form for me');   // sites set to Ask and act
WebBrain.clear();     // start a new conversation
WebBrain.reloadConfig();   // pick up dashboard changes without a reload

Limits

WebBrain for websites is free, and the model it runs on is ours, so the chat is guarded:

Normal use stays far below these limits. If your site needs more, tell us on Discord.

Privacy and safety

• What leaves the visitor's browser: their question, the conversation so far, and the parts of the page the assistant read. They go to sites.webbrain.one and on to the AI model provider for that turn.
• What we keep: counts per site (conversations, Ask and Act runs, tool calls) and the day's usage. Not the conversations.
• Passwords stay out. Values of password, hidden and other credential fields are never put in what the assistant reads.
• Pages are untrusted. Page text is passed to the model marked as untrusted content, so text on a page can't pose as instructions. As with any AI agent, this reduces the risk; it doesn't remove it.
• Visitors stay in control. Every Act run shows a glow around the page and a Stop button.

Troubleshooting