Agent readiness checks compared
How many checks each scanner publishes, and whether they cover finding, reading, acting and paying.
In short
Ora publishes 132 checks, agent-ready.dev 72, StartupHub 44 and Mintlify 35; 4 publish no count. Ora, StartupHub, is-agentic.com and Cloudflare check agent payments in the score. A count is not a quality: it says how much a scanner looks at, not how well.
How many checks each scanner publishes
| Scanner | Checks | What the page says |
|---|---|---|
| 132 | 132 checks in the public catalog at contract 1.38.0, 106 verified and counted toward the score, 26 emerging and shown 1 | |
| 44 | 44 checks in six categories on the scanner page and in the spec; the API docs say 27 and the markdown summary says about 40 2 | |
| is-agentic.com | no count | No fixed count: for an App site such as telnyx.com the report shows 11 essential and 20 recommended checks plus 79 bonus signals 3 |
| 72 | 72 checks in four categories, plus a separate accessibility sub-score of 23 checks 4 | |
| 23 | 23 checks in five categories 5 | |
| 35 | A report shows 35 checks (23 of 35 passed for telnyx.com); the mint score documentation lists 20, and AFDocs, the standard underneath, lists 28 6 | |
| 7 | 7 audits listed for the Agentic Browsing category 7 | |
| SEOJuice Agent Ready | no count | The full check list is not published 8 |
| no count | Not a check scanner: it evaluates how coding agents attempt tasks against a product 9 | |
| no count | No check list is published; the page names WebMCP, llms.txt, structured data, content accessibility and meta information 10 |
Which stage of the journey each one checks
| Scanner | Find | Read | Use | Pay |
|---|---|---|---|---|
| Yes | Yes | Yes | Yes | |
| Yes | Yes | Yes | Yes | |
| is-agentic.com | Yes | Yes | Yes | Yes |
| Yes | Yes | Partial | Partial | |
| Yes | Yes | Yes | Yes | |
| Yes | Yes | Yes | No | |
| Yes | Yes | Yes | No | |
| SEOJuice Agent Ready | Yes | Yes | Yes | No |
| No | No | Yes | No | |
| No | Yes | Yes | No |
"Partial" means the scanner reports the area but does not score it, or covers part of it. The cell-by-cell basis is on the evidence page.
Ora's four layers
| Layer | Points | Checks | Verified | Emerging |
|---|---|---|---|---|
| Discovery | 20 | 16 | 13 | 3 |
| Access | 30 | 42 | 29 | 13 |
| Usability | 40 | 68 | 58 | 10 |
| Payments | 10 | 6 | 6 | 0 |
Ora's catalog: 132 checks, 106 verified and counted, 26 emerging and shown, 61 flagged bonus 1. Ora's methodology page lists 62 Usability checks and 126 in all 11.
What a count does not say
Cloudflare's 23 checks and Ora's 132 are not the same kind of count: Ora's catalog includes bonus and emerging checks that are shown and not scored, and agent-ready.dev's 72 sit beside a separate 23-check accessibility sub-score. Compare a count with the layer coverage in the table above, and read the weights on the score page.
Sources
- ora.ai/api/checks. https://ora.ai/api/checks, read 2026-11-05.
- startuphub.ai/agent-readiness. https://www.startuphub.ai/agent-readiness, read 2026-11-05.
- is-agentic.com/scan/telnyx.com. https://is-agentic.com/scan/telnyx.com, read 2026-11-05.
- agent-ready.dev/methodology. https://agent-ready.dev/methodology, read 2026-11-05.
- isitagentready.com/llms-full.txt. https://isitagentready.com/llms-full.txt, read 2026-11-05.
- mintlify.com/score/telnyx.com. https://www.mintlify.com/score/telnyx.com, read 2026-11-05.
- developer.chrome.com/docs/lighthouse/agentic-browsing/scoring. https://developer.chrome.com/docs/lighthouse/agentic-browsing/scoring, read 2026-11-05.
- seojuice.com/tools/agent-ready. https://seojuice.com/tools/agent-ready/, read 2026-11-05.
- github.com/microsoft/scope. https://github.com/microsoft/scope, read 2026-11-05.
- sitespeak.ai/tools/ai-agent-readiness-scanner. https://sitespeak.ai/tools/ai-agent-readiness-scanner, read 2026-11-05.
- ora.ai/methodology. https://ora.ai/methodology, read 2026-11-05.
Last reviewed 2026-11-05