Charles JonesDocs
What an AI assistant actually sees when it visits a website, what the WebMCP standard is and where it really stands, how attribution receipts work — and the rules this practice holds itself to. Every figure names its source, and where something is a forecast rather than a measurement, it says so.
What agents see
What happens when an assistant visits
An AI assistant fetches your website nothing like a person does. Here is what it actually gets.
Agent-invisible, defined and measured
A precise definition, and what a fetch-only crawl of business websites found.
How to read your recording
If we sent you a recording of what an assistant saw on your site, this explains what you are looking at.
WebMCP
What WebMCP is
A way for a web page to offer an AI assistant tools it can call, instead of leaving it to guess from the HTML.
Where the standard actually stands
Accepted by the W3C community group, live as a Chrome origin trial, and adopted almost nowhere on purpose.
What a tool surface looks like
The shape of a small, honest set of tools for a business that takes bookings.
Why a slow tool fails the whole interaction
A tool an assistant calls sits inside a customer waiting. Latency is not a quality metric there; it is a pass or fail.
Building for agents
Designing a site an agent can use
What is measured about agent access today, what is a bet about where it goes, and why the two are kept apart.
Speed is a correctness requirement
A slow site does not give an assistant a slow answer. It gives it no answer, and the assistant moves on.
Structured data an agent reads
Machine-readable marks that say what your business is, instead of leaving software to infer it.
llms.txt
A plain-text file at the root of your site that tells an assistant what is here and where to look.
Why static output wins
Pre-built pages are faster, cheaper, harder to break, and legible to software by construction.
Provenance & receipts
What a receipt proves
A signed statement that a span of AI output matches a specific document, at a specific offset, under a specific corpus, at a specific time.
Merkle roots, plainly
How one short value can prove that none of a million documents has changed.
Verifying one yourself
Verification is free, forever — and the reason is not generosity.
Status: in design
What exists, what does not, and what would have to be true before any of it is sold.
How this estate runs
Every figure is a pointer
A number inherited from a previous session, a state file, or a tool is re-measured before it is acted on.
A gate that never ran is never clean
Silence from a check and success from a check are indistinguishable unless you make them different.
Nothing filed is rewritten
Corrections sit beside what they correct, dated. The record is append-only.
A control is captured, never authored
Evidence has to come from the run it claims to describe. A well-formed file passes every check that asks whether it is well-formed.