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

# Policy wordings compared clause by clause

> Put the same 5 questions to the policy wording of each insurer. Each wording returns the clauses that bear on each question, with their section and printed page, so 3 wordings line up question by question.

A broker has to tell a client which of 3 insurers covers a flood in the basement. Each insurer's wording has 60 pages, and each hides the point in another place: one under "Exclusions", one in a definition of "water damage", one in an endorsement at the end. A summary of each wording loses exactly that point. This page builds a comparison in which each wording is asked the same questions and gives back its own clauses, word for word.

## The run in 4 steps

### Upload each wording with the same 5 questions

Send each file once, with the questions of the comparison as highlights. A highlight can be a question or a phrase.

```json Fields sent with each file to upload_contents theme={"theme":"css-variables"}
{
  "highlights": [
    "Is damage from flood or surface water excluded?",
    "What is the deductible for water damage?",
    "Is business interruption covered without physical damage?",
    "Within how many days must a loss be reported?",
    "war and terrorism"
  ],
  "max_characters": 0
}
```

With `max_characters` set to `0`, each wording comes back as its outline and the places of its highlights, without its text.

### Line up the clauses question by question

Each highlight says which of your 5 strings found it, and where the clause is. These highlights are from one wording, for the first question, cut to the fields that this step explains.

```json Part of the response theme={"theme":"css-variables"}
{
  "highlights": [
    {
      "query_index": 0,
      "basis": "judged",
      "text": "This policy does not cover loss or damage caused by flood, meaning the escape of water from the normal confines of any natural or artificial watercourse.",
      "page_label": "14"
    },
    {
      "query_index": 0,
      "basis": "judged",
      "text": "Water damage means damage caused by the escape of water from any fixed tank, apparatus or pipe.",
      "page_label": "3"
    }
  ]
}
```

A question finds the exclusion on page 14 and the definition on page 3 that narrows it. Your product puts the clauses of the 3 insurers side by side under each question, in one color for each question. The words in `text` are the insurer's own, so the client reads the clause and not a retelling of it.

`judged` means that a model picked the clause as bearing on the question. The phrase "war and terrorism" is matched word for word, and its highlights say `exact` or `near`.

### Read a clause with what surrounds it

A clause can depend on the sentence before it. Read the section that a highlight is in, and the reader of your comparison sees the clause in its place. A section of a stored wording is read again at no charge.

### Compare this year's wording with last year's

At renewal the insurer sends a new wording and says that "minor changes" were made. Upload it, and compare its record with last year's wording, which you stored as Markdown with its fingerprint. The comparison lists each clause that was added, removed, or changed, with the text before and after, so the one new exclusion is found without reading 60 pages twice.

## What the client can check

| The client asks | What the comparison has |
| - | - |
| Where does the insurer say that? | The clause in the insurer's words, with its section and its printed page. |
| Did you read the whole wording? | The count of pages read, and each page that could not be read. |
| Which clauses did a model pick? | Each clause is marked `exact`, `near`, or `judged`. |
| What changed at renewal? | Each changed clause, before and after. |

## Know the limits

A question finds the clauses that bear on it. Whether a loss is covered is a judgment about those clauses, and it stays with the broker.

A highlight is one block, which is one paragraph of the wording. One call returns at most 50 highlights.

Bold and struck text comes marked from a Word file, and from a PDF that has the structure for it. Where a PDF does not, a notice says that such marks could not be read, and a clause that is struck out by a line drawn over it is not detected as struck.

A record is stored for 48 hours after its last use and for at most 30 days. For that reason, the comparison at renewal needs the Markdown and the fingerprint that you stored a year before.

For the calls, see [Highlight the evidence for each question](https://docs.getclean.ai/read/highlight-passages-and-answers.md) and [Find the one cell that changed](https://docs.getclean.ai/read/track-what-changed.md).


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