Agent Reading Test

150K-char page with canary tokens at 10K, 40K, 75K, 100K, and 130K. Maps exactly where your agent's truncation limit kicks in.

page-size-html, page-size-markdown

80K of inline CSS before the real content. Tests whether agents distinguish CSS noise from documentation.

content-start-position

Client-side rendered page. Content only appears after JavaScript executes. Most agents see an empty shell.

rendering-strategy

8 language variants in tabs. Canary tokens in tabs 1, 4, and 8. Tests how far into serialized tab content the agent reads.

tabbed-content-serialization

Returns HTTP 200 with a "page not found" message. Tests whether the agent recognizes it as an error page.

http-status-codes

Markdown with an unclosed code fence. Everything after it becomes "code." Tests markdown parsing awareness.

markdown-code-fence-validity

Different canary tokens in HTML vs. markdown versions. Tests whether your agent requests the better format.

content-negotiation

301 redirect to a different hostname. Most agents won't follow it (security measure). The canary is on the other side.

redirect-behavior

Three cloud platforms, identical "Step 1/2/3" headers. Tests whether agents can determine which section is which.

section-header-quality

Real content buried after 50% navigation chrome. Tests whether agents read past the sidebar serialization.

content-start-position