Lookio Docs
Lookio websiteOpen Lookio
Platform guidesCitations

Citations

How an answer cites its sources, what a citation contains and how the source field of a resource appears in it.

Every answer is written from passages of your resources, and it cites them. In the text, a citation is a number in square brackets: [1], [2]. They are numbered 1, 2, 3 in the order the answer cites them, so the first source the answer uses is always [1].

What a citation contains

FieldMeaning
nThe number the answer cites it by.
resource_id and titleThe resource the passage comes from.
textThe passage itself, as indexed.
sectionThe headings above the passage, outermost first.
pageThe page, for PDFs, slides and other paged files.
urlThe address, for a web page or a page of a site.
sourceThe resource’s Source field, when it has one.

In the app, open the sources under an answer to read each passage, with its path (title, headings, page) and its address or source.

Make citations useful

  • Give long texts real headings. Section paths come from Markdown headings, so # Refunds and ## Digital goods give a citation a path.
  • Fill the Source field. Set it to the address or reference a reader should look up, such as “Employee handbook, 2026 edition”. It appears with every citation of the resource, and an empty value clears it.
  • Use descriptive titles. The title is part of every passage and of every citation.

How an answer is built

Lookio searches the resources an assistant reads, by meaning and by keywords. It keeps the best passages (up to 12, up to 16 in Deep mode) and gives them to the model with the question, the assistant’s context and guidelines and the last turns of the conversation. The model must answer only from those passages and cite them. Only the passages it actually cited are returned as citations, so what you see is what the answer used.

What to rely on

A citation shows the passage the answer used, so you can verify a claim in seconds. Quote citations when you pass an answer on, and read the passage when the stakes are high.

When the sources do not answer a question, the assistant says so rather than guessing, and no citation is returned.

In the API

An answer carries citations next to answer. The exact fields come from the Ask an assistant reference. A stored conversation returns the citations of every answer: see Retrieve a conversation.

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.