> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getclean.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> getclean's own MCP server is at https://mcp.getclean.ai/mcp. The /mcp path of this docs site is Mintlify's search over these pages, not getclean.
> Every answer of the API opens with outcome. A page that could not be read is a record whose outcome says why, never an HTTP error; read outcome before anything else.
> The API's contract is the OpenAPI 3.1 file at https://docs.getclean.ai/openapi.yaml; the SDKs are generated from it.
> The product's name is written getclean, in lower case.

# Why research agents need a data layer

> A data layer gives an agent, as data, what a person sees on a page: which part is the article, which heading a number is under, who the publisher is. Each claim of the agent's report can then be checked at its passage.

Research has 3 jobs: finding the sources, reasoning from them, and checking the work. Who does each job has changed twice. Each change moved work from a person to a machine, and each asked something else of the data.

## Before search engines, a person did all 3 jobs

A researcher found a book through a library's catalog, read it, and took notes with the page number. A reviewer checked the work by opening the book at that page. The citation was the check: an author, a title, and a page were enough for anyone to find the sentence again.

## With search engines, a person still read the page

A search engine took over part of the first job. It returned 10 links, ranked for a person who would open the first one.

The page behind a link was made for a person to look at: a header, a menu, advertising, and somewhere among them the article. The person skipped what surrounds the text without thinking about it. The person saw that a clause was struck through, that one heading of a table spans 3 columns, and that a ministry's page is not a blog. None of this was written down anywhere, because a person's eyes did it.

## With agents, the reader is a program

An agent does the second job, the reasoning, and it does the first one in a loop: it searches, reads, judges what it found, and searches again, many times for one question, with nobody watching most of the steps. This reader differs from a person in 3 ways.

* An agent cannot see. To a model, a menu is text like the article, text hidden in a page is text too, and a table without its structure is a run of numbers.
* An agent cannot read everything. Its context is limited, so a 300-page agreement has to reach it in parts, and it has to choose the parts before it has read them.
* An agent is not the last reader. Its report goes to a person, a client, an auditor, or a court, and that reader has to be able to check a claim without doing the research again.

A page made to be looked at serves none of the 3.

## A data layer returns what a person did without writing it down

What a person did while reading, by looking or by habit, comes to an agent as data.

| What a person did | What getclean returns |
| - | - |
| Tried one wording after another in a search box | One question in up to 20 wordings, in any language, on up to 10 datasources, as one ranked list. |
| Skipped the menu and the advertising | The main content, and a list of what was left out. |
| Leafed through a long document | The outline with the size of each section, and each section by its id. |
| Read a table by its headings | The table cell by cell, with its merged cells, where the source has the table's structure. |
| Noticed a struck clause | The text with its bold, italic, and struck words, where the source has them as formatting. |
| Knew a ministry from a blog | For each source, its publisher's kind, and whether it is primary, independent, and reviewed. |
| Did not see text that a page hides | The hidden text, apart from the content and named as hidden. |
| Looked for the sentence that answers a question | The passages that bear on each question, each with its place. |
| Copied a figure into the notes | Each field of your schema, filled with the words it came from. |
| Wrote down the page number | A place for every passage: the section, the block, the printed page. |
| Remembered what was searched | A receipt of every search: what ran where, and what was not searched. |

## The check has to cost less than the work

A report that cannot be checked has to be believed, and a careful reader does not believe it. So the third job, the check, decides whether the work of an agent can be used at all.

A check is worth having only if it costs much less than the work it checks. For that reason every record is stored, every passage has a place that stays the same, and every value says what it rests on: a quote found word for word, a passage that a model judged, a field that the source does not state, a page that was not read. A second agent, or a person with one call, can open the passage behind a sentence and see whether the words are there.

For the calls that do this, see [From a question to a checked report](https://docs.getclean.ai/start/how-it-fits.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.