KnitKnot

# Read the Agent Ledger

Check which owned pages have an Agent version, its current state, version number, fact references, and publication date.

## At a glance

  1. 1. **Open the ledger**: Go to Content → Agent Ledger in an eligible workspace.
  2. 2. **Narrow the pages**: Search a URL or choose a status tile to filter the list.
  3. 3. **Check readiness**: Read the state, version, fact references, and published date before checking delivery.

If your workspace has Agent publishing, open [Content → Agent Ledger](https://app.knitknot.ai/content/agent-ledger). The list tracks Agent versions for owned pages. It shows the page URL, **Agent version** state, version number, number of **Fact references**, and **Published** date when one exists.

## Find a page and read its state

Search by published page URL, or choose a status tile to filter the ledger. Choose the same tile again to clear that filter. You can also filter the **Agent version** column and sort the table. The five tiles group the underlying states as follows:

| Tile | Meaning | | --- | --- | | Live | A validated version is available to agents. | | Needs review | The version failed validation. | | Outdated | The version is stale and needs refreshing. | | Building | A draft is being prepared or waiting. | | Paused | Agent-version delivery is disabled for that page. |

The **Version** column identifies the stored revision. **Fact references** counts fact links included in that revision; a count is not a review of whether each fact is current. **Published** records when a version was published, if applicable. A blank publication date should not be read as a failed delivery check.

For example, when a page is **Live** but Agent responses have fallen, check [Content → Delivery](/docs/check-agent-delivery/) for the effective delivery state and recent verification. A valid stored version and a live edge response are separate conditions. To inspect the original page, its citations, access, and claims, use [Content → Your Pages](/docs/review-your-pages/).

If the ledger says **No Agent versions yet**, entries appear after an owned page has a validated Agent version. [Content → Interfaces](/docs/manage-agent-interfaces/) shows whether feeds, indexes, and customer-domain MCP are effectively available for the published corpus.

Docs navigation
Docs › Guides

Read the Agent Ledger

Check which owned pages have an Agent version, its current state, version number, fact references, and publication date.

Updated

At a glance

  1. Open the ledger

    Go to Content → Agent Ledger in an eligible workspace.

  2. Narrow the pages

    Search a URL or choose a status tile to filter the list.

  3. Check readiness

    Read the state, version, fact references, and published date before checking delivery.

If your workspace has Agent publishing, open Content → Agent Ledger. The list tracks Agent versions for owned pages. It shows the page URL, Agent version state, version number, number of Fact references, and Published date when one exists.

Find a page and read its state

Search by published page URL, or choose a status tile to filter the ledger. Choose the same tile again to clear that filter. You can also filter the Agent version column and sort the table. The five tiles group the underlying states as follows:

TileMeaning
LiveA validated version is available to agents.
Needs reviewThe version failed validation.
OutdatedThe version is stale and needs refreshing.
BuildingA draft is being prepared or waiting.
PausedAgent-version delivery is disabled for that page.

The Version column identifies the stored revision. Fact references counts fact links included in that revision; a count is not a review of whether each fact is current. Published records when a version was published, if applicable. A blank publication date should not be read as a failed delivery check.

For example, when a page is Live but Agent responses have fallen, check Content → Delivery for the effective delivery state and recent verification. A valid stored version and a live edge response are separate conditions. To inspect the original page, its citations, access, and claims, use Content → Your Pages.

If the ledger says No Agent versions yet, entries appear after an owned page has a validated Agent version. Content → Interfaces shows whether feeds, indexes, and customer-domain MCP are effectively available for the published corpus.