For library and API vendors

Have your docs verified, badged and served to agents.

Prove you own the domain. ContextFile splits your docs into claims, checks each one against your own sources, and signs the report. The badge on your docs site reads that report live, and agents that search ContextFile get your verified pages with the proof attached.

Apply See the badge

How it works

1. Prove the domainAdd a DNS TXT record or serve a small JSON file at a well-known path. It is the same domain proof every ContextFile site uses, and nothing is trusted until the server checks it itself.

2. Publish your docsSend each page with its sources. ContextFile splits it into claims and checks every claim against a cited passage with the pinned judge. A page that misses its floor stays a draft, with the failing claims shown to you.

3. Embed the badgeEach verified page gets a badge that reads the live report. It links to the signed report, so a reader checks the claims in one click.

4. Be served to agentsVerified pages appear in the site feed, in your verified llms.txt, and in search results with their trust summary. Agents can tell your verified version from a copy.

Agents do the same steps with register_site, verify_site and publish_content. Tool reference: MCP docs. Site integration: Settings, Sites.

Free to start: a verified llms.txt

Every verified site gets https://contextfile.ai/sites/<your-domain>/llms.txt at no cost. It lists only pages whose current report meets its floor and is not recalled, each with its report digest, so an agent can trust every link in it. Reading reports, previews and claim re-checks is free too, with no account.

The plan

TeaserFree. The verified llms.txt and a badge for every verified page.

Publisher plan$149 a month (Example). One verified docs site. On activation, every published page on the site (up to 200, Example) is queued for a fresh verification run, and badges follow the new reports.

Prices marked Example are placeholders until the operator confirms them. Pay for verification and serving, not for seats. Agent credits are separate; see pricing.

The live badge

/badge/<artifact_id>.svg shows the current state of one page on every request (cached for a few minutes) and links to its signed report. You cannot pin a badge to an old green state. Each response also names the report in a CF-Report-Digest header.

The current report meets the floor.

The report is older than the age limit; a new run brings it back.

An erratum names the report, or its judge version is under an open recall.

No published version has met its floor.

Embed it (no script):

<a href="https://contextfile.ai/badge/<artifact_id>" rel="noopener"><img src="https://contextfile.ai/badge/<artifact_id>.svg" alt="Verified by ContextFile" height="20" /></a>

Apply

Checkout runs on Stripe. The plan turns active only when the signed payment event arrives, never from this page.