# Agent delivery

> Agent-readable Markdown, a read-only MCP endpoint, WebMCP declarations, and a signed change feed are views over the same published content and approved fact ledger.

- Canonical: https://knitknot.ai/product/agent-interfaces/
- Part of: Get Agent Ready

## Agent-readable Markdown

Eligible pages receive a published Markdown version. The human path remains unchanged, and an edge failure falls back to the customer's original page. KnitKnot does not claim that an llms.txt file is used by major providers at inference time, and serving Markdown does not promise a citation.

## MCP on the customer's domain

The read-only endpoint can return a published page, search the managed corpus, and return approved facts with receipts. The endpoint is built and capability-gated. Customer-domain rollout remains behind launch gates, so it is not generally available.

## WebMCP for in-browser agents

The WebMCP snippet declares read-only tools through the experimental navigator.modelContext interface in supported Chromium environments. It uses the same tenant-scoped published data and becomes a no-op when the browser interface is absent. The snippet is built and rollout-gated.

## Agent feed and notifications

The signed agent feed records each immutable version publication, including the page and release, plus the cycle when a cycle produced it. It is built and rollout-gated. Outbound publish notifications are still pending; when available, a notification will announce a changed URL without promising a fetch or a changed answer.

## One corpus, several views

The fact ledger and managed content are the durable layer. Each interface answers from that layer rather than maintaining a separate set of claims.