Paste a URL. See the page an agent has to read.
Agent Preview puts your HTML beside a clean Markdown version so the cost of browser clutter becomes impossible to miss.
HTML bloat is easy to dismiss when it is hiding in DevTools. It is harder to ignore when the same page is sitting beside a clean Markdown version at one-thirtieth the size.
That is the idea behind Agent Preview. Paste a public URL and we request it twice: once as HTML and once with an Accept header that prefers Markdown. If the site supports content negotiation, we show the response it actually serves. If not, we generate a cleaned-up comparison so you can see what a purpose-built representation could look like.
HTML on the left. Markdown on the right. No signup, and usually only a couple of seconds between the URL and the “oh, wow.”
The signal ratio
We estimate a signal ratio for each version: how much of the response appears to be meaningful page content rather than document machinery. It is a heuristic, not a universal measure of quality. It is still very good at exposing pages where the article is a rounding error inside the application shell.
The file-size delta tells the same story without interpretation. A page that weighs 400KB as HTML might become 15KB of clean Markdown. Repeat that across a research task and the difference gets loud quickly.
This vs. the full audit
Agent Preview answers one question about one URL: what is the gap between the page we serve browsers and the content an agent needs?
The audit tool is the full picture.
| Agent Preview | Audit | |
|---|---|---|
| Pages checked | 1 | Up to 10 |
| Speed | Instant | ~30 seconds |
| Output | Side-by-side preview | Scored dashboard |
| Checks run | Signal ratio, size delta, content negotiation | 7 checks with weighted scoring |
| Best for | Quick preview, sharing with teammates | Full site assessment, tracking readiness |
Preview makes the problem visible. The audit shows whether it repeats across the site and which implementation details are failing.
Copy and use the output
The Markdown panel has a copy button because the output should be useful, not decorative. Drop it into a prompt, compare it with your own endpoint, or use it as a rough target while implementing content negotiation.
Paste in a page. If the side-by-side comparison is ugly, good—you now have something concrete to fix. Run the full audit when you want to know how far the problem spreads.