Can an AI agent read this page?

Paste a URL. The free check returns the verdict, how much the signals agree and one line of evidence. The same analysis in full, with every signal and the evidence behind it, is $0.01 per call in USDC on Base over x402.

Waiting for a URL.

What the verdicts mean

VerdictWhat it says to an agent
openFetches cleanly, robots allows the path, content is there. Use it.
machine_readableOpen, and the page publishes structured data (JSON-LD) - prefer that over scraping text.
robots_disallowedrobots.txt forbids the exact path for an agent. Do not fetch; look for an API or another source.
bot_walledA bot-management vendor fingerprints the request. Fetching fails or returns a challenge, not data.
auth_required401/403 on a plain GET: there is a login in the way, not a paywall.
js_renderedThe HTML carries no content without JavaScript - a plain fetch gets an empty shell.
thin_contentVery little extractable text: the page is a shell, a redirect or a stub.
unreachableDNS, TLS or timeout failure. Retry or drop it.

For agents, not just people

No signup, no API key, no invoice: the payment is a per-request signature. Machine-readable entry points are /v1/catalog (price list), /llms.txt (description written for models), /openapi.json (schema with the payment terms embedded), /.well-known/x402 (terms at the conventional location), and the free preview at /v1/page/posture/preview.