Integrate website text verification

Capture, review and publish

1. Create a scoped API key with publications:write. Read operations require publications:read.
2. Prepare and verify the supplied ownership file on the exact HTTPS origin.
3. Capture the section by its unique ID. Review the returned text before publication.
4. Publish the capture with publicConsent=true and a persistent requestId UUID. For an update, include documentId and expectedVersion.

The hosted workflow uses CheckThisFile storage and its operational worker. It performs bounded HTTPS requests to your site, with no external archive, timestamping provider or embedded remote script. Automatic observations are scheduled every six hours.

Add a simple HTML link

<a href="YOUR_VERSION_VERIFICATION_URL">View registered version</a>

Place it outside the registered section, or mark its container data-checkthisfile-exclude. Keep the ownership file online. HTTP redirects, private network addresses, cookies and browser-rendered content are not supported.

Offline library

Version 0.1.4 adds checkthisfile/web-text for local extraction, hashing and evidence verification. It never contacts our servers. Download the prepared package; the npm registry release is a separate publication.

npm install ./checkthisfile-0.1.4.tgz

import { extractWebText, hashWebText, verifyWebPublicationEvidence }
  from 'checkthisfile/web-text';
const { text } = extractWebText(html, { elementId: 'main-content' });
const hash = await hashWebText(text);
const check = await verifyWebPublicationEvidence(evidence, trustedKey);

Supply the trusted key independently. Offline verification establishes the exported signature and text hash; it does not establish current website content, key revocation or the full version chain.