Lookio Docs
Lookio websiteOpen Lookio
Platform guidesResources

Resources

Add texts, files, web pages and websites, follow their import status, re-index them and stay within your plan's word allowance.

A resource is a piece of knowledge, stored once and reusable by any assistant. Open Resources in the app to see them all, filter by type, tag or status, and open one to edit it.

Add a resource

Choose Add a resource, then pick a tab: Text, Files, Web page or Sitemap (a whole website).

You addWhat happensGuide
Text tabLookio indexes what you paste.Below
Files tabEach file becomes a resource, read by the right tool for its format.File formats
Web page tabEach address becomes a resource, read as a visitor sees it.Websites
Sitemap tabOne resource whose pages are read and kept in sync.Websites

Text

Paste text or Markdown, up to 100,000 characters. Lines starting with # become the sections that answers cite, so give a long text real headings.

The title is part of every passage Lookio indexes. Write a descriptive one: “Refund policy 2026” retrieves better than “Notes”.

Fields on every resource

  • Title. Up to 200 characters.
  • Tags. Up to 30, each up to 60 characters. See Tags.
  • Source. Optional, up to 500 characters. A URL or a mention such as “Employee handbook, 2026 edition”. It is shown with every citation of the resource. An empty value clears it. See Citations.

Statuses

Every import is asynchronous. The resource is created at once with a status, and Lookio reads and indexes it in the background: seconds for a page or a short file, minutes for a site.

Status in the APIShown in the appMeaning
queuedIndexingWaiting to be read.
processingIndexingBeing read and indexed.
readyReadySearchable. Assistants can answer from it.
failedFailedCould not be read. status_detail says why.
staleNeeds re-indexingOut of date. Re-index it.

ready and failed are final. Poll until one of them appears and stop there.

An assistant answers only from ready resources. A resource that is still queued is skipped without an error, so a question asked too early can come back with no answer.

On a development deployment without the live engine, a resource shows ready_simulated. You only meet this status when you run Lookio locally.

Re-index

Open a resource and choose Re-index. What it does depends on the type, and the action is named after it.

TypeRe-index
TextIndexes the current text again.
FileReads the stored original again. Nothing is uploaded twice.
Web pageFetches the page again. The action is called Re-read page.
WebsiteSynchronises the site: new pages are added, changed pages are read again and pages that are gone are removed. The action is called Sync now.

Re-indexing costs no credits. While a new version is being built, the resource stays searchable on its current version, and the new one replaces it only when it is complete.

Editing a text, or renaming a file, re-indexes it for the same reason: the title is part of every passage.

Use re-index after a failure, or when the source changed. For a website that syncs weekly you rarely need it.

Read what was indexed

Open a resource to see its extracted text, exactly as assistants search it, in Markdown. It also lists what Lookio could not read, such as pages without readable text. Check an import this way before you rely on it. The text is shown up to 200,000 characters.

Word allowance

Your plan caps the number of words Lookio stores for the workspace.

PlanWords stored
Free125,000
Starter1,000,000
Pro10,000,000
CustomNo fixed limit

Lookio counts the words of every ready resource, as runs of letters or digits. When the limit is reached, adding or re-indexing is refused with this message: “Your plan’s limit of 125,000 words stored is reached. Delete resources or upgrade your plan to add more.” The API error code is request_too_large_for_plan.

A resource that would pass the limit while it is being indexed fails with the same message in status_detail. Delete resources you no longer need, or change plan. See Credits and plans.

From the API, the CLI and MCP

Everything on this page is available outside the app.

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.