KnitKnot
You are reading the agent-optimized layer of this page: the literal markdown we serve to AI crawlers and assistants, shipped in the page source of every visit. Making sure AI reads the right facts about a company is literally what KnitKnot does.

# 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.

## 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.

Raw mirror of this content: https://knitknot.ai/product/agent-interfaces.md. Site-wide summary: /llms.txt · full content: /llms-full.txt

Agent delivery

Give agents a hosted, governed version of every page that matters.

Serve benchmark-linked Agent Versions as clean Markdown today. Each release stays tied to its approved facts and history; customer-domain MCP, WebMCP, and a signed feed expose the same record as their rollout gates open.

Product evidence plate
interface register

Published page view

The approved page, in a format agents can read.

The human page stays unchanged. The Markdown response carries the same supported substance and its release identity.

Contract boundary

Publishing a Markdown view does not promise that a provider fetches or cites it.

customer.com/securitysigned release
accepttext/markdown
output# Security and access
outputRole-scoped access is available on every plan.
receiptcustomer.com/security#access
release024 · published
Shared record

Update the fact once. Every interface reads the same release.

The fact ledger keeps the claim, source, receipt, and approval together. Published interfaces are views of that record.

Approved fact Active

Security · Access controls

Role-scoped access is available on every plan.

Source
customer.com/security
Receipt
access-controls-008
Review
Customer approved

Markdown

In use

# Security and access
Role-scoped access is available...

/mcp

Built, gated

get_facts
receipt: attached

WebMCP

Experimental

get_verified_facts
read-only declaration

Agent feed

Built, gated

fact.updated
release: 024

One approval updates the next published release. The interfaces do not maintain separate claims.

Read-only query

MCP can answer only from what was published.

The customer-domain endpoint reads signed page, search, and fact artifacts. There is no live authoring model in the request path.

$ tools/call get_facts

input
{ "page": "/security" }
page
published version
fact
approved record
receipt
attached

The endpoint cannot add a claim that was not present in the published artifacts.

Failure behavior

A failed edge read returns the original page.

A small active pointer selects an immutable release. If that pointer or artifact fails validation, the request passes through to the customer’s origin.

GET customer.com/security

Delivery decision

Active pointer

release-024
signature
valid
content hash
pinned
artifact
available

Pointer valid

Serve the signed release

Return the approved published artifact for the requested interface.

Pointer invalid or missing

Pass through to origin

Return the customer’s original page. The edge does not invent a replacement.

Immutable releases

History stays intact

Pointer rollback

No artifact is erased

Human path

Content stays unchanged

Observed use

Availability and use stay separate.

KnitKnot records each signal in its own lane. None of them prove that an interface changed an AI answer.

Delivery response

Served

The edge returned the published interface artifact.

Tool call

get_facts

A client called one read-only tool on the customer domain.

AI referral

Observed

A visit preserved an identifiable AI referrer.

Delivery responses, tool calls, and referrals are recorded separately.

Questions

Agent delivery FAQ

Start with the record

Host the first agent-facing page from approved evidence.

Benchmark the company, approve the Fact Ledger, and publish a governed Agent Version before opening another interface.

Question → evidence → next evaluation