Lookio Docs
Lookio websiteOpen Lookio
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. Any assistant can read it. Resources lists them all. Filter by tag, type or status, and open a resource to edit it.

The Resources page with Ready, Indexing, Words stored and Pages counters, filters, and a table of resources with PDF, DOC, XLS, URL, TEXT and SITE icons

Resources: the counters at the top, then one row per resource with its format, tags and status.

Add a resource

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

The Add a resource dialog: Files, Web page, Sitemap and Text tabs, a drop zone, Tags and Source fields

You addWhat happensGuide
Text tabLookio indexes what you paste.Below
Files tabEach file becomes a resource. Lookio reads it with a reader for its format.File formats
Web page tabEach address becomes a resource. Lookio reads it as a visitor sees it.Websites
Sitemap tabOne resource. Lookio reads its pages and keeps them in sync.Websites

Text

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

The title is part of every passage that Lookio indexes. Write a clear title: “Refund policy 2026” is found more easily 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”. Lookio shows it with every citation of the resource. An empty value clears it. See Citations.

Statuses

Lookio creates the resource at once, then reads and indexes it in the background. A page or a short file takes seconds. A site takes minutes.

stateDiagram-v2 direction LR [*] --> queued queued --> processing processing --> ready processing --> failed ready --> stale: the source changed stale --> processing: re-index failed --> processing: re-index ready --> processing: re-index or sync
The life of a resource
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, then stop.

The sheet of a failed web page resource, with the reason circled: The page answered 404 Not Found. Check the address, then re-read the page.

A failed resource says why, under its status.

An assistant answers only from ready resources. It skips a resource that is not ready, without an error. A question asked too early can get no answer.

Re-index

Open a resource, then its ⋯ menu. The re-index action is named after the type of the resource.

The menu of a resource sheet: Re-index, See indexing logs, Documentation and Delete resource

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.
WebsiteSyncs the site. Lookio adds new pages, reads changed pages again and removes pages that are gone. The action is called Sync now.

Re-indexing is free. During a re-index, assistants keep searching the current version. The new version replaces it only when it is complete.

Lookio also re-indexes a text when you edit it, and a file when you rename it, because the title is part of every passage.

Re-index after a failure, or when the source changed. A website that syncs each week rarely needs it.

Read what was indexed

Open a resource, then View the text. You see the text in Markdown, as assistants search it, up to 200,000 characters. You also see what Lookio could not read, such as pages without readable text. Check an import this way before you rely on it.

The sheet of the PDF resource Pricing and plans 2026: status Ready, type File, file name with 6 pages, tags and dates

The sheet of a file: its status, file name and number of pages.

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. A word is a run of letters or digits. In a CSV over 2 MB, a row that holds only figures and codes counts as one word, because it is computed but not stored for search. At the limit, Lookio refuses to add or re-index, 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.

If a resource passes the limit during indexing, it fails with the same message in status_detail. Delete resources you do not need, or change plan. See Credits and plans.

Pages read each month

Each plan also includes a number of pages read per calendar month (UTC).

PlanPages per month
Free200
Starter1,500
Pro15,000
CustomNo fixed limit

A page is one PDF page, one image or slide that OCR reads, or one web page, at import or during a site sync. Text, Markdown, CSV, spreadsheets and Word files never count. Only new or changed content counts. A page that did not change since the last sync is not read again.

Past the limit, an admin buys extra pages on Billing, by 1,000. They never expire. Lookio uses the plan’s pages first. The Pages this month counter on the Resources page shows your use.

From the API, the CLI and MCP

List resources, Create a resource, Add a file, Get a resource’s content, Re-index.

Terminal
lookio resources list --tag billing
lookio resources add-file ./handbook.pdf --tags hr
lookio resources reindex RESOURCE_ID

See CLI commands.

add_text_resource, add_web_page, get_resource and more. See MCP tools.

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.