Agent Readiness Check
Understanding the report
The paid check is live at 0.01 USDC per call, paid on Solana via x402. Call GET /check.php?domain=example.com (optional &probe=/path). An unpaid request receives an x402 payment challenge; after payment, the same request returns this report.
Observations, not a score
Reports record a domain, a UTC check time, and observations from public HTTP requests. They do not certify a site or assign a universal readiness score. A missing discovery file does not by itself mean a website is broken.
HTTPS and redirects
https.reachable records whether the HTTPS request returned an HTTP response, including an error status. Read https.status alongside it: reachable does not mean successful. http_redirects_to_https records whether the HTTP request finished at an HTTPS URL.
Discovery files
llms_txt describes the response from /llms.txt and the document features the parser finds. agent_card describes the JSON at /.well-known/agent-card.json, including selected fields and skill count. These checks do not verify the accuracy of a site's claims or test its agent operations.
Robots rules
robots_txt.ai_agents reports the evaluated rules for the root path / for selected crawler names. A root result does not describe every path, and a robots rule does not demonstrate whether a crawler follows it.
Optional payment challenge
When a same-domain probe path is supplied, x402_probe records an unpaid response and any payment challenge the parser recognizes. A recognized challenge does not prove that payment settlement or delivery works.
Errors and partial results
Read each observation's status and error together. A blocked destination, timeout, or failed fetch is a limitation of that observation, not proof that the file is absent. The engine can return an overall ok: true while individual requests fail; this means a report was produced, not that every check passed.
See a complete, real report: sample report.