A block reports “not measured”, never a low score
A site that refuses automated clients is not failing. It is not measured. Scoring it anyway would punish a decision it is entitled to make, so the score is withheld and the reason is published.
60 checks from a public rubric. Each shows its evidence and its source.
The scanner uses a plain HTTP client and public rubric v0.9.1. Each check lists a shell command that repeats its measurement. Read the methodology
How the score is composed
essential ×3 · recommended ×1
Web standards, by dimension
API and agent checks and commerce checks join the web-standards part only when the scan finds that surface on the site. When no agent convention applies, or none was measured, web standards are the whole score.
Each checker here runs the full scan, and the report opens on the checks it names. The generator writes robots.txt lines and sends no request.
Start with the guide: How to make your website agent-ready
Then read: What is agent readiness? A plain guide · What is a good agent readiness score? · What is llms.txt? Does Google use it? · How to test an MCP server with curl
Anatomy of a scan
vercel.com · 75 requests · 23.3s · rubric v0.9.1
Read from a stored record, not a mock-up. The full transcript, every response size and every status code, is in the status file for this scan — and the same log streams live while yours runs.
The measured corpus
We measured 5 of the 5 published candidates under rubric v0.9.1. The highest score is 88.5 (cloudflare.com), and the median is 73.6. 2 of the 4 sites with an API or agent surface reached level 4. 3 checks were not passed by any of them.
Read from the stored scan records of the 5 published candidates; the newest was measured 2026-11-11. Measured under the current rubric v0.9.1.
Restraint
A site that refuses automated clients is not failing. It is not measured. Scoring it anyway would punish a decision it is entitled to make, so the score is withheld and the reason is published.
If a probe gets no usable answer, the check is reported as not measured. It leaves the score, the confidence figure falls, and a level gate it holds is not reached.
Every redirect hop is resolved and refused if it points at a private or link-local address. At most 3 scans run at once, and each client may start 10 per minute. The scan requests 24 paths on every site, and up to 82 when more checks apply. Beyond them it requests only a capped set of URLs the site's documents name, and 1 random missing path, so it is not a crawl.
Every page renders completely with JavaScript disabled, and loads 1 script from another origin: the page-view counter at analytics.marifeting.com. The homepage also loads /hero-glow.js from this site, which only moves a glow with your pointer. The scan runs none of the scripts on your site. It reads what a client without a browser can read, because that is the client it measures for.
AgenticWebScore measures agent readiness: how well a website serves an agent that has no browser. It fetches a public domain from the outside, the way an agent would. It scores what it observed against a versioned rubric of 60 checks in 5 dimensions. Every defect lists what was observed and, where one exists, a command that reproduces it.
Lighthouse runs in a browser. This scanner uses a plain HTTP client, and it gives no score to a site it cannot measure.
| Dimension | Share of web standards | Question |
|---|---|---|
| Discoverability | 37% | Can an agent reach the homepage and find the pages? |
| Content | 54% | Can an agent read the page without running JavaScript? |
| Crawler access | 9% | Do crawlers know what they may fetch? |
| API and agent | Only when the scan finds it | Is the API or tool server described for agents? |
| Commerce | Only when the scan finds it | Can an agent read products, prices and policies? |
It does not bind the measured origin, the redirect, the defect flag, and every detail, evidence, and fix text. An edit to any of these is not caught.
This site publishes the surfaces below. Each is served now and generated from one content source. It does not pass every check in its own rubric.
It is whether an autonomous agent can find your site, read it, trust it, and act on it without a human in the loop. That is narrower than SEO and different from AI visibility: it measures the machine-facing contract, not your ranking or your brand mentions.
Lighthouse runs in a browser and audits one page at a time, its agentic browsing audits included. This scanner uses a plain HTTP client and no browser.
The scan requests 24 paths on every site, and up to 82 when more checks apply. It also requests a capped set of URLs the site's documents name. It scores what it observed against a published rubric and publishes a record with a fingerprint. A site can use both.
A site that returns 403 or 429 to every automated client has told us nothing about itself. It has told us something about our vantage point. So the result is no score, with an explanation, rather than a number.
No. The scanner decides what kind of site it is looking at before it scores anything. A check whose subject is absent from the site is reported as out of scope. It leaves the score, it is never a failure, and the report says why.
Yes, within limits: every record carries a fingerprint. The fingerprint binds the host, the rubric version, the site profile, and the module scope. It also binds each scored check's id, status, points, counted flag, and exclusion, mcp-server's discoveredBy field, and each unscored check's id and state. /verify recomputes the score and level from the bound outcomes, and reports a mismatch as tamper evidence.
It does not bind the measured origin, the redirect, the defect flag, and every detail, evidence, and fix text. An edit to any of these is not caught. Records measured under an earlier rubric are not shown, and a re-scan measures the site under the current one.
The rubric is published as /rubric.json, the surfaces above are served, and the scanner runs. This site's own score is read from its scan record, as any other site's is.
When a record of this site is stored, it is at /aws/<host> for this site's host, with a markdown copy at /aws/<host>/status.md. No score is published for this site without one.
Every defect lists what the scanner observed and, where one exists, a command that reproduces it. Where a cause can be fixed, the report shows the change to make.
Make the changes, then press Re-scan now on your report. Entering your domain again within 6 hours opens the stored report instead.
To show your score on your own site, press Get the badge on your report and paste its snippet into your homepage. Press Check my badge, and the directory lists your site as a verified listing.