Check Agent version delivery

If managed Agent versions are enabled for your workspace, open Content → Delivery. The page answers whether delivery is live and whether its latest verification passed. It concerns Agent versions served alongside your original site pages; Content → Interfaces controls separate customer-domain feeds, indexes, and tool access.

Confirm what is live

Read the status sentence first. It says whether delivery is live, awaiting setup, disabled, or affected by a connection or verification problem. Agent delivery states which requests receive the Agent version. Cloudflare connection shows whether KnitKnot can manage delivery through your connection or Managed Edge. Last verification records the latest checks of both original pages and Agent responses.

If a verification failed and delivery was automatically disabled, the banner names the failing sample when one is available. While disabled, requests receive the original page. If a Cloudflare zone blocks AI crawlers before the Worker runs, a separate warning appears; a live deployment does not override that zone rule.

For customer-owned Cloudflare delivery, Enable, Disable, and, when a previous live deployment exists, Roll back are available according to the current state. The page explains why Enable is unavailable, including missing permissions or a plan requirement. Managed Edge is operated by KnitKnot, so its connection and delivery state are shown without those customer-owned Worker controls. Use Settings → Integrations to connect or reconnect Cloudflare, or choose an available delivery mode.

Read the response counts

The two response tiles cover the last seven days:

• Agent responses were served from Agent versions.
• Original responses passed through to your original pages.

When tracking is available, the daily chart shows how those responses changed during the same window. The section table groups them by URL path prefix. Open a section to see the matching pages in Your Pages. A blank count or an unavailable tracking state is not evidence of zero requests.

These are edge responses, not the number of people who read an AI answer. For verified crawler requests, use Traffic → Agent activity. For citations and answer changes, read a later benchmark.

Diagnose a mismatch

Open Technical details to inspect the Cloudflare resources, verification probes, and deployment history. The probes test original and Agent responses separately. Open a deployment record to see the state associated with that deployment rather than assuming the latest status describes every earlier release.

For example, if Agent responses fall to zero after a change, first check whether delivery is still live and whether verification passed. Then check the response section and verified agent activity. A drop in Agent responses alone cannot tell you whether crawlers stopped visiting, the Worker passed requests through, or delivery was disabled.

If the page says Delivery isn’t enabled for this workspace, the feature is not available there; your original pages remain available. For reviewing the text of a proposed Agent version before publication, use Review a proposed Agent version update.