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

# Contract review that tells a missing clause from an unread page

> Review 300 supplier contracts against one checklist. A clause that is found comes with its words and its page. A clause that is not found says whether the contract lacks it or a page could not be read.

A manufacturer has 300 supplier contracts and a new rule: each must give the buyer a right to audit. A review tool listed the contracts without such a clause. Some of them had it, on a scanned schedule that the tool could not read. The list said "no clause" where the truth was "not read", and the company wrote to suppliers whose contracts were in order. This page builds a review in which those 2 cases never look alike.

## The run in 5 steps

### Upload each contract with the checklist

Send each file once, with your checklist as a template and your open questions as highlights. A scanned contract is recognized page by page, and a long one runs as a job.

```json Fields sent with each file to upload_contents theme={"theme":"css-variables"}
{
  "json_schema": {
    "type": "object",
    "properties": {
      "audit_rights": {
        "type": "string",
        "description": "The clause that lets the buyer audit the supplier"
      },
      "termination_notice_days": {
        "type": "integer",
        "description": "Days of notice to end the contract without cause"
      },
      "liability_cap": {
        "type": "string",
        "description": "The limit of the supplier's liability, with its currency"
      },
      "governing_law": { "type": "string" },
      "price_adjustment": { "type": "string", "description": "How and when prices can change" },
      "subcontracting_consent": {
        "type": "boolean",
        "description": "Whether subcontracting needs the buyer's consent"
      }
    }
  },
  "highlights": [
    "Can the buyer audit the supplier's premises and records?",
    "What happens if a delivery is late?",
    "limitation of liability",
    "force majeure",
    "Which party owns the tooling?"
  ],
  "max_characters": 0
}
```

One call returns the outline of the contract, the filled checklist, and the place of each passage that bears on a question.

### Read each item of the checklist

Each field comes back with a status. This response is for one contract, cut to the status, the words, and the printed page of each field.

```json Part of the response theme={"theme":"css-variables"}
{
  "schema_statuses": {
    "/governing_law":           { "status": "found", "text": "This Agreement is governed by the laws of France.", "page_label": "18" },
    "/termination_notice_days": { "status": "found", "text": "on not less than 90 days' written notice", "page_label": "16" },
    "/liability_cap":           { "status": "found", "text": "shall not exceed the fees paid in the 12 months before the claim", "page_label": "14" },
    "/price_adjustment":        { "status": "absent" },
    "/subcontracting_consent":  { "status": "absent" },
    "/audit_rights":            { "status": "unread" }
  }
}
```

The contract has no clause on price changes and none on subcontracting: both are `absent`, and that is a finding. The audit right is `unread`: a part of the contract was not read well enough to say that the clause is missing. This contract goes to a person, and not onto the list of contracts without the clause.

### Count the pages that were read

`pages` in the record says how the read went: how many pages the file has, how many were read, which failed, and for each scanned page how sure the recognition is, from 0 to 1. This part of the record is cut to 2 of its 10 scanned pages.

```json Part of the response theme={"theme":"css-variables"}
{
  "pages": {
    "count": 31,
    "parsed_count": 31,
    "failed_pages": [],
    "recognized": [
      { "page_number": 22, "confidence": 0.97 },
      { "page_number": 23, "confidence": 0.58 }
    ]
  }
}
```

Page 23 was recognized with a confidence of 0.58. The notice `recognition_uncertain` names every such page, and that page is why the audit right is `unread`. In a contract whose pages were all read with high confidence, `absent` means that the clause is not there.

### Send one page to a person, not one contract

Each scanned page comes with a picture of the page. The reviewer opens the picture of page 23, reads the schedule, and fills in the one open field. Of 300 contracts, a person looks only at the pages that need a person.

### Read the schedules as tables

A price list in a schedule is a table, and the link between a product and its price is the row. From a Word file or a PDF with structure, the table comes cell by cell, so a price cannot slide to the product in the next row.

## What the general counsel can check

| The general counsel asks | What the review has |
| - | - |
| Where is the clause? | Its words, with the printed page. |
| Is the clause really missing? | `absent`, with every page read, or `unread`, with a notice that names the pages read with low confidence. |
| Which pages did nobody read well? | Each page with its number for how sure the reading is. |
| Was the file a clean copy? | A notice if the file had tracked changes, with their count. |

## Know the limits

A model fills the checklist, and each value is bound to words of the contract. Treat a `found` field as a passage to read, and quote the words, not the model.

Handwriting on a scan comes as flat text or not at all, so a handwritten amendment can be missed without a notice. Tracked changes in a Word file are shown as accepted. A strikethrough that is only a line drawn over the text is not detected.

For the calls, see [Fill your fields, each with the words it came from](https://docs.getclean.ai/read/extract-fields-with-citations.md) and [Turn PDFs, Office files, and scans into evidence you can cite by page](https://docs.getclean.ai/read/pdfs-scans-and-documents.md).


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