What is an agent feed?

An agent feed is a machine-readable change log for managed content. Each item identifies the changed page, its published version, and the URLs affected by that revision. Stable item identity lets a consumer distinguish a new change from a repeated read of the same item.

The feed is an interface over the same fact ledger and release record that back the human page and its Markdown agent version. It does not become a second place where facts can drift.

What does it prove?

The feed proves that KnitKnot published and recorded a change. It does not prove that an agent fetched the item, that a provider re-indexed the page, or that an AI answer changed.

Those are separate evidence lanes. Verified crawler fetches are labeled as such. Journey-level benchmark movement is measured in a later window and reported beside the revision, with outside changes and insufficient data kept visible.

What about IndexNow?

KnitKnot can build IndexNow ping descriptors for changed host URLs. Sending those pings is a separate deployment concern and is not yet part of the public promise. A ping would report a changed URL; it would not promise a fetch, a re-index, or a changed answer.

Is the feed generally available?

The feed is built and rolling out behind workspace and deployment gates. KnitKnot confirms the active interfaces during launch review rather than presenting every built surface as active on every customer domain.

Next: agent-ready content or agent interfaces.