# Sourcewatch (sourcewatch.ai): agent-readiness 76/100, grade B > Rank 28 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-30T04:40:16.780Z. Page: https://qomvia.com/site/sourcewatch-ai JSON: https://qomvia.com/api/score/sourcewatch-ai ## Summary Category: Software and SaaS { "known": false, "confidence": "low", "summary": "I do not have specific pre-existing knowledge about sourcewatch.ai as an AI visibility and tracking tool. My training data does not contain detailed information about this particular website.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "Specific features and functionality beyond the provided description", "Pricing models and subscription tiers", "User base and market penetration", "Customer reviews and satisfaction", "Company background, funding, and team" ], "alternatives": [], "business": "I do not have sufficient information in my knowledge base to describe this company's specific business.", "competitors": [] } ## Score by group - Machine access: 18/24 - Content legibility: 23/26 - Discovery surface: 15/20 - Identity & policy: 6/12 - Agent-facing performance: 8/8 - Agent protocols: 6/10 Failing checks: - [blocker] robots.txt turns AI crawlers away - [blocker] No MCP endpoint to call - [improvement] No stated policy for automated access - [improvement] Organisation structured data - [improvement] Content carries a date ## Add-on packs - E-commerce & product feeds: 32/100 (not part of the public score) ## AI mentions and rivals Named in 1 AI assistant answers. ## FAQ Q: Is Sourcewatch readable by AI agents? A: Sourcewatch (sourcewatch.ai) scores 76 out of 100 for agent readiness, grade B, measured today, on 30.09.2026. 0 of 3 agent classes we test can use the site, and 2 checks currently block agents outright. Q: What stops agents from using sourcewatch.ai? A: The heaviest problems are: robots.txt turns AI crawlers away; No MCP endpoint to call; No stated policy for automated access; Organisation structured data; Content carries a date. 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 Sourcewatch agent-readiness score calculated? A: Qomvia fetches public pages of sourcewatch.ai 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. E-commerce & product feeds checks are scored separately (32/100) and do not affect the public score or rank. 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 today, on 30.09.2026. ## Related - Leaderboard: https://qomvia.com/leaderboard — category ranking: https://qomvia.com/leaderboard/saas-software - Score another site: https://qomvia.com/