What Survives the Convert: HTML In, Markdown Out
An agent that asks for a web page does not receive the page. It receives Markdown, a title, and a set of signals — and all three are the output of a chain of decisions about what to keep. Those decisions are usually invisible, which is why a parse that looks fine in a demo can be wrong in a way nobody notices until the model cites a navigation link as a source.
This is a run with the decisions left in. Eight URLs, eight page classes, every payload saved, every count computed from the Markdown that came back rather than estimated.
Method
Eight URLs were submitted to the live endpoint on 2026-10-07 through the operator path used for measurement — the same renderer the paid path uses, with the free-tier counter bypassed so the sample was not capped at ten. URLs were chosen by class before the run. Seven rendered; one was refused, and its response is quoted in full below.
Each URL is one POST, and the response to that POST is three fields. The finished job is four:
POST <url> -> 202 {"jobId":"6d706c27-…","status":"queued", "statusUrl":"/status?jobId=6d706c27-…"} GET <statusUrl> -> 200 {"status":"completed","markdown":"…", "metadata":{…},"litmus":{…}} The Markdown and the fifteen signals arrive in the same body. A caller that wants both does not make a second request to grade the page it just read.
The run
class host words chars H1 tables links boiler content_type reference en.wikipedia.org 2993 37087 2 1 353 0.08 academic_paper documentation developer.mozilla.org 6187 59781 2 2 292 0.39 tutorial documentation www.rust-lang.org 369 4081 1 0 14 0.33 tutorial commerce www.cloudflare.com - - - - - - refused: consent wall academic arxiv.org 821 17299 1 1 150 0.06 academic_paper code github.com 378 4494 4 1 37 0.06 documentation news www.bbc.com 1262 9671 2 0 53 0.02 tutorial forum lobste.rs 668 20837 1 0 216 0.02 general words and chars are counted on the returned Markdown. H1 is the number of lines matching a top-level heading. tables counts GFM separator rows (| --- |), so it is the number of tables the source page actually had. boiler is the litmus boilerplate_ratio. content_type is the litmus classifier.
Structure does survive
Tables survive as tables. This is a two-column table lifted from the MDN Array reference, cells and links intact:
| Mutating method | Non-mutating alternative | | --- | --- | | [copyWithin()](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/copyWithin) | No one-method alternative | | [fill()](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/fill) | No one-method alternative | | [pop()](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/pop) | [slice(0, -1)](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/slice) | That renders in any Markdown viewer without a plugin, and the links inside the cells still point at the source site. Links are the bulk of the output on some pages: the Wikipedia article came back with 353 of them, the MDN page with 292, a link aggregator with 216.
Code does not
Code is not fenced. The quickstart block from the GitHub repository page came back as plain lines with no fence around them:
To get started quickly with a new project, run the command below: npm create cloudflare@latest pnpm create cloudflare@latest # or yarn create cloudflare@latest Two things follow, and both are visible in the counts. First, the # or lines are indistinguishable from headings to a Markdown renderer, because nothing marks them as code. Second, the page
Test the page your agent just read.
Clean Markdown and 20 trust signals, $0.002 per parse.