# Visiblo (visiblo.io): agent-readiness 7/100, grade F > Rank 996 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-10-01T18:12:24.723Z. Page: https://qomvia.com/site/visiblo-io JSON: https://qomvia.com/api/score/visiblo-io ## Summary { "known": false, "confidence": "low", "summary": "I do not have specific information about visiblo.io in my knowledge base. Therefore, I cannot provide a summary of what this site is or what it does.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "The primary services or products offered by visiblo.io", "Its target audience and geographical reach", "Its unique selling propositions or notable features", "Its business model and revenue streams", "Key competitors in its market" ], "alternatives": [], "business": "I do not have sufficient information to describe what this company does, for whom, and where.", "competitors": [] } ## Score by group - Machine access: 7/24 - Content legibility: 0/26 - Discovery surface: 0/20 - Identity & policy: 0/12 - Agent-facing performance: 0/8 - Agent protocols: 0/10 Failing checks: - [blocker] No discoverable sitemap - [blocker] No llms.txt - [blocker] Bot protection blocks declared agents - [blocker] No API or feed to read - [blocker] No MCP endpoint to call ## AI mentions and rivals Named in 6 AI assistant answers. ## FAQ Q: Is Visiblo readable by AI agents? A: Visiblo (visiblo.io) scores 7 out of 100 for agent readiness, grade F, measured 1 week ago, on 01.10.2026. 0 of 3 agent classes we test can use the site, and 5 checks currently block agents outright. Q: What stops agents from using visiblo.io? A: The heaviest problems are: No discoverable sitemap; No llms.txt; Bot protection blocks declared agents; No API or feed to read; No MCP endpoint to call. 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 Visiblo agent-readiness score calculated? A: Qomvia fetches public pages of visiblo.io 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 1 week ago, on 01.10.2026. ## Related - Leaderboard: https://qomvia.com/leaderboard - Score another site: https://qomvia.com/