CheckWebsiteNow Agent Readability Score for one public homepage

Our own transparent 0-100 score (model cwn-ars-1), not an official standard. Fixed fetch plan on the final homepage origin: homepage HTML, robots.txt, llms.txt, /.well-known/api-catalog, /.well-known/ai-catalog.json, /.well-known/mcp/server-card.json, a sitemap prefix and one Accept: text/markdown request. Shared ten-second deadline, nine requests in total, at most five redirects per resource (files after the homepage follow redirects only on the same host), 1 MiB (larger homepages are analysed from their first 1 MiB) HTML and 64 KiB per text file, identity encoding only, no JavaScript, no forms, never a call to a discovered MCP or API endpoint. Score = earned / measured weight points, rounded down; unknown checks are removed, never passed; no number below 70 measured points or without readable homepage HTML. Ten requests per minute per client, one running check per client, 60-second cache per website (cached: true). findings and summary are the deprecated schema 1.0 view, kept for one transition. Method: GET /api/v1/agent-readability-method.

post/api/v1/agent-check

Request

  • Base URL: https://checkwebsitenow.com
  • URL: https://checkwebsitenow.com/api/v1/agent-check
  • Auth: none declared

Request body

hostnamestring required

Example request

{
  "hostname": "example.com"
}

Response

Score and evidence. Unavailable resources are unknown checks, not proof of failure.

schema_version'2.0' required
score_name'CheckWebsiteNow Agent Readability Score' required
score_modelstring required
officialunknown required
method_urlstring required
targetstring required
checked_atstring date-time required
final_urlstring nullable required
final_originstring nullable required
final_url_truncatedboolean required
duration_msinteger required
requests_usedinteger required
measurement_regionstring required
cachedboolean required
cached_age_secondsinteger

Only on cached results: age of the reused result. Normally below 60; up to 300 when a limit refused a fresh check and a recent result was served instead.

status'complete' | 'partial' | 'unavailable' required
scoreinteger nullable required
score_availableboolean required
score_unavailable_reasonstring nullable required
scaledboolean required

True when the score is scaled to fewer than 100 measured points.

caps_appliedstring[] required
disclaimerstring required
summaryobject required

Schema 1.0 counts of findings.

findingsobject[] required

Schema 1.0 observations (document, structure, robots, llms, metadata, webmcp).

limitationsstring[] required
homepage_truncatedboolean

True when the homepage was larger than 1 MiB and only its first 1 MiB was analysed.

homepage_notestring nullable

Plain-language note when homepage_truncated is true, otherwise null.

homepage_http_statusinteger nullable

HTTP status our GET received for the final homepage (null when it was not read). Compare it with http_status of POST /api/v1/check: when one request was refused (401/403/429) and the other allowed, bot protection treated the two requests differently.

Example response

{
  "score_model": "cwn-ars-1",
  "method_url": "/agents#score"
}

Changes

No recorded changes to this operation across all 1 revision of this API.