Lookio Docs
Lookio websiteOpen Lookio
WidgetWidget troubleshooting
Widget

Widget troubleshooting

What to check when the bubble does not show, the chat refuses to load in a frame, or visitors read that the assistant cannot answer.

Find the symptom, then check each cause in order.

The bubble does not show
  • The chat bubble is off. The browser console says so. In the Install tab, turn Chat bubble on.
  • The domain is not allowed. The browser console says so. Add the domain to Allowed domains, in the Config tab.
  • The widget is paused. Turn Live on.
  • Its assistant reads no resource. The console says nothing. The widget’s sheet says “Not showing: its assistant reads no resource”. Give the assistant resources and wait until they are ready.
  • The script is missing or blocked. Check that the page loads https://widget.lookio.app/v1/widget.js. Check that your content security policy allows https://widget.lookio.app in script-src and frame-src.
The in-page chat or the hosted page says: not found

That format is off. Open the Install tab and turn on In the page or Hosted page. A new widget has the chat bubble only.

The browser says: Refused to display in a frame

The page is not on an allowed domain. Add its host. If you list subdomains one by one, add each one, such as docs. or www..

Visitors read: The assistant cannot answer right now

The widget reached its monthly credit ceiling, the workspace has no credits left, the widget is paused, or its assistant was deleted. Check the Config tab and your credits.

Visitors read: Too many questions

A visitor reached their hourly or daily limit, the widget reached its Answers per minute, all visitors limit, or one network address sent more than 20 questions in a minute. If real visitors meet a limit, raise it in Config. Only the limit per address is fixed.

Answers say the sources do not cover the question

The widget answers only from its assistant’s resources. In Assistants, check what the assistant reads, and that those resources are ready.

Still stuck? Open Help in the app and write to us, with the widget’s id.

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.