Lookio Docs
Lookio websiteOpen Lookio
GuidesAssistants

Assistants

Create an assistant, write its context and answer guidelines, and choose what it reads with the all, selected or tags knowledge modes.

An assistant answers questions from the resources you give it. Open Assistants, then Create an assistant. The form opens with a name, a context and answer guidelines. Keep them or change them. To let Lookio AI write them, choose Create with AI.

The Assistants page with three assistants: Support assistant, Sales assistant and Onboarding buddy, each with its colored orb

Open an assistant to edit it. Its sheet has three tabs: Settings, Knowledge and Public. Make your changes, then select Save at the bottom of the sheet.

Settings

SettingWhat it isLimit
NameHow you recognise it.120 characters
ContextWhat the assistant is and who it talks to.12,000 characters
Answer guidelinesHow answers are written: language, format, level of detail.12,000 characters
Answers fromWhat it reads. See below.

Context

Write what the assistant is and who it talks to, in plain words. You do not need to tell it to answer only from the resources. It always does.

Example
You answer Billowfin customers: freelancers and small businesses who send invoices with Billowfin. They write from the help widget or from inside the app.

Answer guidelines

Say how the answer should look.

Example
Answer in the customer's language. Give the steps first, then the why. If the answer is not in the sources, say so and offer to reach a person at support@billowfin.com.

Keep the two apart. The context says who the assistant is. The guidelines say how its answers look.

The Settings tab of the Support assistant with its context and answer guidelines filled in

The Settings tab: context and answer guidelines.

What an assistant reads

An assistant has one knowledge mode at a time.

ModeIt readsUse it when
All resourcesEvery resource of the workspace, including those added later.You have one knowledge base.
Chosen resourcesOnly the resources you pick, up to 200.An assistant has a narrow job.
Resources with tagsEvery resource with a tag it follows, now or later.Resources change often, and you sort them with tags.

When you change the mode, Lookio keeps your list for the other modes. Go from Chosen resources to Resources with tags and back: your picks are still there.

The Knowledge tab with three modes: All resources, Chosen resources and Resources with tags

An assistant answers only from resources that are ready. See Resources.

If you create an assistant through the API without knowledge, Lookio uses tags when you give only tags, and selected in all other cases. Send all to read every resource.

Who can use an assistant

On the Free and Starter plans, every member can use every assistant. On the Pro and Custom plans, an admin chooses which assistants each member may use. See Members and permissions.

You can limit an API key to a list of assistants. Such a key cannot create assistants.

Change or delete an assistant

Edit any field at any time. The next question uses the new settings.

When you delete an assistant, its resources stay. Its conversations stay readable, marked as from a deleted assistant. Nobody can continue them. You cannot delete an assistant that a widget uses. First delete the widget or move it to another assistant. See Deleting things.

Call it from your code

The API button on the sheet gives the call for this assistant, in curl, the CLI or JavaScript.

The Call this assistant from your code dialog with cURL, CLI and JavaScript tabs, a curl command and the assistant id

Create an assistant, Update an assistant, Ask an assistant.

Terminal
lookio assistants create --name "Support assistant" --follow-tags support,billing
lookio ask ASSISTANT_ID "How do I issue a credit note?"

list_assistants, get_assistant, create_assistant, update_assistant, ask_assistant.

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.