Lookio Docs
Lookio websiteOpen Lookio
WidgetInstall a widget
Widget

Install a widget

Create a widget, choose its formats, allow your domain, and paste the bubble snippet, the in-page snippet, an iframe or the hosted link.

Create the widget

Name it

Open Widgets, then Create a widget. Only you see the name.

Choose the assistant

A widget has one assistant, with its context and its knowledge.

Allow your domains

Type the sites where the widget may show, for example help.billowfin.com. Separate them with commas. Browsers refuse to show the widget on other sites.

Create it

Select Create widget. The widget is live at once and opens on its Install tab. To pause it, turn Live off. The code can stay on your site.

Choose the formats

The Install tab lists the three formats: Chat bubble, In the page and Hosted page. Each has its own switch. Select a format to see how to install it.

  • A new widget has the chat bubble on and the other two off.
  • A format that is off does not show. The in-page chat and the hosted page answer “not found”. Only the preview in the app shows them.

In the API, the CLI and MCP, the three switches are bubble, embed and hosted_page.

Chat bubble

Paste this line before the closing </body> tag on every page, or in the custom code setting of your site builder (Webflow, Framer, WordPress, Shopify, Softr):

HTML
<script src="https://widget.lookio.app/v1/widget.js" data-lookio-widget="YOUR_WIDGET_ID" async></script>

The Install tab shows the line with your widget’s id.

The Install tab of the Help center bubble widget: Chat bubble on, In the page off, Hosted page on, and the script tag to paste, circled

Install: the three formats with their switches, then the line to paste.

In a page

Turn on In the page. Put an element where the chat goes, give it a height, and add the script once:

HTML
<div data-lookio-embed="YOUR_WIDGET_ID" style="height: 600px"></div>
<script src="https://widget.lookio.app/v1/widget.js" async></script>

The chat fills the element. One script serves several embeds and one bubble on a page.

Without scripts

Some builders refuse scripts but accept iframes. The iframe is the in-page format, so In the page must be on:

HTML
<iframe src="https://widget.lookio.app/w/YOUR_WIDGET_ID?embed=1" style="width: 100%; height: 600px; border: 0" title="Chat"></iframe>

Hosted page

Turn on Hosted page, then share https://widget.lookio.app/w/YOUR_WIDGET_ID. Anyone with the link can chat, within the visitor limits. When you turn it off, the link answers “not found”.

If nothing shows

Check these three things, in order:

  1. The format is on, in the Install tab.
  2. Your domain is allowed, in Allowed domains of the Config tab.
  3. The widget is live: the Live switch at the top of its sheet.

The browser console of your site says which one. More causes in Widget troubleshooting. With no allowed domain, only the hosted page works.

From the API, the CLI or an agent

Each widget returns its snippets, ready to paste.

Create a widget, Update a widget, List widgets.

Terminal
lookio widgets create --assistant ASSISTANT_ID --domain help.billowfin.com --mode flash

create_widget, update_widget, list_widgets.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Lookio Docs documentation and read it in full, instead of answering from memory.

https://lookio.app/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://lookio.app/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.