> ## 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.

# Repeatable output and model steps

> The content, the outline, and the places of a source are the same on every read. A model works only in steps that each response names, and one switch turns all of them off.

A check is possible only if the thing checked stays the same. If the same page gave another text on each read, no citation could be opened again and no comparison would mean anything. So a response says which of its parts are the same on every read and which a model wrote.

## These parts are the same on every read

Under one version and one configuration of getclean, the same page or the same file gives the same output in each of these parts.

| Part | What repeats |
| - | - |
| The content | The same text, in every format. |
| The outline and the ids | The same sections and blocks, with the same ids. |
| The fingerprint | The same hash, because the text is the same. |
| An `exact` or `near` highlight | The same places, found by matching words, without a model. |
| A comparison | The same changes, found block by block and cell by cell, without a model. |
| Text recognized from a scan | The same text, because recognition is a fixed step under one version. |

## A model works in named steps only

A model works in these steps, and in no others.

| Step | Where it runs | Runs by default |
| - | - | - |
| A summary | In a fetch or on a stored record, if you ask. | No |
| A filled schema | In a fetch or on a stored record, if you ask. | No |
| A `judged` highlight | Only for a string that is not in the text word for word. | Yes, unless turned off |
| The ranking of a search | In every search. | Yes, unless turned off |
| The choice of datasources | In a search that names no datasource. | Yes, unless turned off |
| The kind of a publisher that is not yet known | In a fetch or a search. | Yes, unless turned off |

The output of a model step is not promised to be the same on a second call. For that reason, each such output is marked: a highlight says `judged`, a filled field comes with the words of the source, and a summary is named as a model's text.

## Every response names its steps

`execution` in a response has the version and the configuration of getclean, and one entry for each model step that ran, with the version of that step.

```json Part of a response theme={"theme":"css-variables"}
{
  "execution": {
    "version": "1.0.0",
    "configuration": "cfg-2026-11",
    "models": [
      { "step": "highlights", "version": "hl-2026-10" },
      { "step": "summary", "version": "sum-2026-10" }
    ]
  }
}
```

The list also names the recognition of a scan, as `recognition`, which is a fixed step that repeats under one version. An empty `models` list means that no model and no recognition took part in the response.

## One switch turns every model step off

A request that sends `deterministic_only` as `true` runs no step whose output could differ between 2 runs. Highlights are found word for word only, and a publisher's kind comes only from what is already known. A search returns its results in the merged order of the datasources and searches the web alone unless you name datasources. A request for a summary or a schema is refused. Every part of a fetch's response then repeats, except what belongs to the call itself, such as its time and its id. A search still returns what its datasources have on the day it runs.

The policy of a key can set this for every call. A regulated team can then give its agents a key that no model step can run under.

## A pinned version reads a page the same way after a change

The text and the ids repeat under one version and its configuration. A later version of getclean can read a page differently. To get the same reading across such a change, send the version as `pinned_version`, and the call runs under that version and its configuration.

`get_limits` lists the versions that are served. A version is served for at least `version_minimum_days` days after its change is announced. During its last `version_notice_days` days, each response that has notices has the notice `version_retiring`.

A fingerprint can be compared only within one view, one version, one configuration, and one kind of source. A report that will be checked later should store these 4 facts beside each fingerprint, because the check has to run under the same ones.


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