The Other Web
Every page has two audiences: the person looking at it and the machine reading over their shoulder. The semantic web asked publishers to mark meaning; today’s models scrape the human page; the next web must decide how machines act. Paste one URL to compare the human page, the HTTP response, and the browser-rendered result. Fetched server-side, honestly, as AadharshBot.
The machine web, 2026-08:56.0% of HTML requests are bots10.0% of desktop pages have llms.txt>10k public MCP servers$898K in x402 volume over 30 days
Try:
Compare puts Human, HTTP Machine, and Browser Run side by side. Predict the machine pane; the miss is the lesson.
Human view · the live page
Paste any URL above.You get the page a person sees, the raw file a machine gets instead, and what that difference costs.
Machine view
What the machine actually receives.The raw file, the rules it is handed, and the bill for reading them.
Browser Run · Rendered
Browser Run view. Ask Cloudflare to open this URL in a real headless browser and return the rendered page, screenshot, Markdown, accessibility tree, and a clear WebMCP lab boundary.
This is opt-in: browser execution is slower and can run page JavaScript. Runtime WebMCP discovery is reported separately and requires the Chrome-beta lab.
Idle. Nothing is fetched until you ask, and then just once, server-side, with no logging.