Documentation

Deploy the generated worker once; Sichta serves and refreshes your conformance files from then on. Fails open — never breaks your site.

Merge three rewrites into your vercel.json once; Sichta serves and refreshes your conformance files from then on.

Append three proxy redirects to your netlify.toml once; Sichta serves and refreshes your conformance files from then on.

Add three proxy_pass locations inside your server block and reload; Sichta serves and refreshes your conformance files from then on.

Get every generated file as a zip and host it yourself. Full control, but regenerated files need a re-download and a redeploy.

Sichta opens a pull request against your repository on every regeneration. You review and merge; your CI deploys as usual.

A Cloudflare Worker with the files baked in — no runtime dependency on Sichta at all. Redeploy on each regeneration.

Sichta POSTs signed JSON to your endpoint on every regeneration, with the file list and a signed 24-hour download link.

Upload a month of access logs — nginx, Apache or Cloudflare format — and get a report of which AI agents actually visited.

A public badge page with your live score and last-verified date. It lapses if verification stops — that is what makes it worth showing.

Files are served unchanged for 30 days after cancellation, and the static bundle arrives by email. Then the managed routes step aside.

Agent-readiness is whether an AI agent can find, read and correctly quote your website — a checkable property, not a marketing score.

llms.txt is a markdown file at your site root that tells AI systems what your site is and where its important pages are.

Answering Accept text/markdown with the page's markdown source — the cheapest way to hand an agent clean text instead of a DOM.