Agent-readiness report, Software and SaaS
Is Cloro agent-ready?
Agents can read and quote it or call it as a tool, so Cloro is usable end to end.
cloro.dev, last scanned 3 days ago, on 11.11.2026
Agent classes working
2/3
Score history
±02 scans since 05.11.2026
- 0
- Blocking agents
- 5
- Weak spots
- 21/26
- Checks passed
What costs Cloro the most
2 of 3 agent classes work
- ✓Answer engines & research agents
- ✓MCP tool-callers
- !Summarisers & knowledge agents
- ✕
No stated policy for automated access
Cautious platforms will not act on the site without an explicit permission signal.
Improvement - !
Language and market are declared
Localised answers cannot tell which market the page serves, so it loses local queries.
Polish - !
DNS-AID agent index or ARD
Agents cannot find your agents by looking up your domain.
Polish - ✕
No Web Bot Auth support
Signed, verifiable agents get treated like anonymous scrapers.
Polish - ✕
No OAuth discovery
An agent that needs to sign in has no machine-readable way to find out how.
Polish
✓21 checks passed+−
Free dashboard
Track cloro.dev and watch it climb.
Weekly re-scans, the fix for every gap above, and the rank moves of your rivals.
- 5 optimization suggestions, ready today
- Weekly re-scan with alerts on every change
- Rank and rival moves in one view
Your dashboard
We email you a sign-in link and add cloro.dev to your dashboard.
- Re-scan weekly
- Fixes listed
- Rivals tracked
Check a rival
5 domains free, unlimited with a plan.
Machine interfaces
Cloro exposes 8 of 8 interfaces agents look for: AI crawler access, Bot user-agent handling, Server-rendered content, llms.txt, MCP server, API or feed, Organisation markup, Machine-readable contact.
Locked
All 8 interfaces and 26 checks for cloro.dev
See which interface is missing, what each check looked for, and what to change to pass it. Free account, no card.
View detailed signalsThe seal
Agent-Ready Champion
Every agent class can find, read, trust and act on this site. Paste this line where you want the seal: it is drawn at runtime, so it upgrades itself when you improve and removes itself if a deploy closes the site to agents.
<script src="https://qomvia.com/badge.js" data-slug="cloro-dev" async></script>There is no image URL and no static version. The seal exists only as markup we serve per request, which is what makes it worth displaying.
- Agent-Ready Champion90+
- Agent-Ready75+
- Agent-Readable60+
- In Progress40+, dashboard only
Cloro and AI agents: common questions
Is Cloro readable by AI agents?+−
Cloro (cloro.dev) scores 92 out of 100 for agent readiness, grade A, measured 3 days ago, on 11.11.2026. 2 of 3 agent classes we test can use the site, and 0 checks currently block agents outright.
What stops agents from using cloro.dev?+−
The heaviest problems are: No stated policy for automated access; Language and market are declared; DNS-AID agent index or ARD; No Web Bot Auth support; No OAuth discovery. Each one is scored from a public HTTP response, and the fix for each is listed in the signed-in report.
How is the Cloro agent-readiness score calculated?+−
Qomvia fetches public pages of cloro.dev as an AI agent would and runs the core checks every site gets across 6 groups: Machine access, Content legibility, Discovery surface, Identity & policy, Agent-facing performance, Agent protocols. Checks are weighted by how much an agent loses when they fail, and the score is expressed out of 100.
How often is this score updated?+−
Public scores are re-checked when the site is re-scanned; tracked domains are re-scanned weekly and their owners are alerted when a check regresses. This page shows the scan from 3 days ago, on 11.11.2026.
Compare and keep reading
Scores are computed from public HTTP responses only. We never submit forms, never attempt a purchase and never bypass a bot challenge. Disagree with a result? Request a correction or opt this domain out.