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

# Tenders and the addenda that move their deadlines

> Follow a tender page to every file it links to, and read each file. When an addendum appears, your agent knows that it is new, reads it, and finds the sentence that moves the closing date.

A bid team prepares an offer for a public tender. The tender page is 10 lines long and links to 6 files. The buyer posts a seventh file, "Addendum 2", 9 days before the closing date. It moves the closing date a week earlier and adds a certificate to the list of required documents. Nothing on the page itself changed but one link. The team learns of it when its offer is rejected. This page builds a watch on a tender that reads what the page links to.

## The run in 5 steps

### List the files of the tender page

Fetch the page, then ask its record for the links of the kind `file`. Each link has its address, its text, and the section of the page it is in. The list has the links of the page's main content, so the menu and the footer of the site are not in it.

### Read each file

Fetch the files in one batch. Each comes back as a record with its outline, so your agent knows which file is the terms of reference and which is the price schedule before it reads either.

### Check the page again each morning

Fetch the tender page with the fingerprint of its last record. If the page is `unchanged`, no link was added. If it changed, list its links again and compare them with the list you have. An address that is new is a new file.

### Read the new file with your questions

Send the old files with their fingerprints and the new file with the questions that decide a bid.

```json Request body of fetch_contents_batch theme={"theme":"css-variables"}
{
  "items": [
    {
      "label": "terms-of-reference",
      "url": "TERMS_FILE_URL",
      "baseline_fingerprint": "TERMS_FINGERPRINT",
      "highlights": [
        "closing date for submission of tenders",
        "Which documents must a bidder submit?"
      ]
    },
    {
      "label": "price-schedule",
      "url": "PRICE_SCHEDULE_URL",
      "baseline_fingerprint": "PRICE_SCHEDULE_FINGERPRINT"
    },
    {
      "label": "addendum-2",
      "url": "ADDENDUM_URL",
      "highlights": ["closing date for submission of tenders", "What does this addendum change?"]
    }
  ],
  "max_characters": 0
}
```

Replace each placeholder that ends in `_URL` with the address of a file, and each that ends in `_FINGERPRINT` with the fingerprint of that file's last record.

A file whose bytes are the same comes back as `unchanged`, and no page of it is parsed. The new addendum comes back with the places of its highlights.

```json Part of the response, cut to the highlights of the addendum theme={"theme":"css-variables"}
{
  "highlights": [
    {
      "query_index": 0,
      "basis": "near",
      "text": "The closing date for submission of tenders is amended to 21 November 2026, 12:00 local time.",
      "page_label": "1"
    },
    {
      "query_index": 1,
      "basis": "judged",
      "text": "Clause 7.2 is amended to require a valid tax clearance certificate with each tender.",
      "page_label": "2"
    }
  ]
}
```

The first highlight was found by its words, and the second was picked by a model as bearing on the question. Both are the buyer's own sentences, with their page.

### Compare a replaced file

A buyer can also replace a file under the same address. Then the fingerprint differs, and the file comes back in full. Compare its record with the earlier one, and the comparison lists each clause and each cell of the price schedule that changed.

## What the bid manager can check

| The bid manager asks | What the watch has |
| - | - |
| Is every file of the tender here? | The links of the page, each with its kind, beside the records you fetched. |
| What does the addendum change? | The sentences of the addendum, with their page. |
| Did a file change under the same name? | The fingerprint of each file, and the comparison if it differs. |
| When was the addendum found? | The time of each fetch. |

## Know the limits

A link's kind is read from its address. A file behind an address without a file ending is listed as a page, and its fetch says what it is.

A portal that shows its files only after a sign-in cannot be fetched by its address. A person can download the files and upload them.

An addendum that is a scan is read from its pictures, and the reading has a confidence. A date that was recognized with a low confidence should be read by a person.

A watch runs when your code calls. No call watches a page for you.

For the calls, see [Follow a page to the documents it links to](https://docs.getclean.ai/read/links.md) and [Fetch 20 sources at once and know what came back before you read a word](https://docs.getclean.ai/read/many-pages-at-once.md).


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