
Ora against agent-ready.dev
Scanner against scanner, on the same evidence rules.
In short
Ora ranks 1 of 10 on the rubric with 94 points, and agent-ready.dev ranks 4 with 61. Use agent-ready.dev when you want a score tied to named specs; use Ora when you want weighting by measured agent behaviour. agent-ready.dev's per-check fixes are written by the operator; Ora's ranking is more useful for competitor framing.
Which to pick
Pick Ora unless you want a pull-request gate in which 69 of the 72 checks map to a published spec and the score is a plain pass percentage; then use agent-ready.dev. On the rubric Ora scores 94 and agent-ready.dev 61; Ora is ahead on 6 of 10 criteria and level on 4. 1
The pick page has the reasons and the limits: Best agent readiness scanner.
The sourced difference
agent-ready.dev counts passing checks out of 72 with no weights and maps each to a published spec; Ora weights 132 checks it authors and adds live agent evaluation. agent-ready.dev records dated method changes, the latest on 2026-10-20. 1
Side by side
| Measure | Ora | agent-ready.dev |
|---|---|---|
| Operator | era labs (Ora) | Agent Ready (independent) |
| Type | Scanner | Scanner |
| Pricing and access | Free. The /pricing endpoint returns one plan, Free, 0 USD, with unlimited score lookups and full REST API access; API keys for higher scan limits are issued manually on request (read 2026-11-04). 2 | Free scan with no sign-up; Pro 19 USD a month for API, authenticated MCP and CI gating (read 2026-11-04). 3 |
| Journey (of 15) | 15 | 11 |
| Checks (of 15) | 15 | 11 |
| Real agents (of 15) | 15 | 0 |
| Open method (of 10) | 10 | 10 |
| Standards (of 5) | 3 | 3 |
| Dev fit (of 10) | 10 | 10 |
| Peers (of 10) | 10 | 4 |
| Fixes (of 10) | 10 | 7 |
| Repeat scans (of 5) | 1 | 1 |
| Free (of 5) | 5 | 4 |
| Total of 100 (rank of 10) | 94 (rank 1) | 61 (rank 4) |
| Domains scored in the Concordance | 60 of 60 | 0 of 60 |
Points are from the ten-criterion rubric on the method page; every cell's source is on the evidence page.
Verdict by reader type
- Head of web
- Use agent-ready.dev when you want a score tied to named specs; use Ora when you want weighting by measured agent behaviour.
- Technical marketer
- agent-ready.dev's per-check fixes are written by the operator; Ora's ranking is more useful for competitor framing.
- Platform engineer
- agent-ready.dev's unweighted percentage is easier to gate in CI (Pro plan, 19 USD a month); Ora's check ids are stable and free to re-run.
In the Scanner Concordance
agent-ready.dev scored none of the 60 Concordance domains (badge says unscored), so the two cannot be compared on the same sites. The reason is access: neither a keyless lookup nor a scan the scanner's terms allow was available on 2026-11-04. See the Concordance method.
What each does not do
Ora
- Does not convert pages to markdown or serve agents a separate version of your site.
- Does not manage or block bots; it only reports how bot protection treats agents.
- Does not track brand mentions or citations in AI answers.
- Does not scan private or logged-in pages; every check runs against a public URL.
agent-ready.dev
- Does not test bot protection or what a WAF returns to agents.
- Does not run agents on tasks; it reads files, headers and HTML.
- Does not rank sites on a public leaderboard.
Where to read next
Sources
- agent-ready.dev methodology. https://agent-ready.dev/methodology, read 2026-11-04.
- Ora /pricing (JSON). https://ora.ai/pricing, read 2026-11-04.
- agent-ready.dev vs alternatives (updated 2026-11-04). https://agent-ready.dev/agent-ready-vs-alternatives, read 2026-11-04.
Last reviewed 2026-11-05