# Cloro (cloro.dev): agent-readiness 92/100, grade A

> Rank 6 of 3306 on Qomvia (rubric v2.3.0). Last scanned 2026-11-11T12:00:14.617Z. Page: https://qomvia.com/site/cloro-dev  JSON: https://qomvia.com/api/score/cloro-dev

## Summary
Category: Software and SaaS
{
  "known": false,
  "confidence": "low",
  "summary": "I do not have specific information about cloro.dev in my training data. Therefore, I cannot provide a summary of what this site is or what it does based on my own knowledge.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "Details about its specific API functionality and integration complexity",
    "Its market penetration and user base",
    "Specific pricing tiers and enterprise solutions",
    "Its long-term viability and competitive landscape",
    "Customer reviews and satisfaction"
  ],
  "alternatives": [],
  "business": null,
  "competitors": []
}

## Score by group
- Machine access: 24/24
- Content legibility: 25/26
- Discovery surface: 19/20
- Identity & policy: 8/12
- Agent-facing performance: 8/8
- Agent protocols: 8/10
Failing checks:
- [improvement] No stated policy for automated access
- [polish] Language and market are declared
- [polish] DNS-AID agent index or ARD
- [polish] No Web Bot Auth support
- [polish] No OAuth discovery

## AI mentions and rivals
Named in 1 AI assistant answers.


## FAQ
Q: Is Cloro readable by AI agents?
A: 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.

Q: What stops agents from using cloro.dev?
A: 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.

Q: How is the Cloro agent-readiness score calculated?
A: 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.

Q: How often is this score updated?
A: 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.

## Related
- Leaderboard: https://qomvia.com/leaderboard — category ranking: https://qomvia.com/leaderboard/saas-software
- Score another site: https://qomvia.com/