# Anchour (anchour.com): agent-readiness 67/100, grade C > Rank 172 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-29T13:50:16.851Z. Page: https://qomvia.com/site/anchour-com JSON: https://qomvia.com/api/score/anchour-com ## Summary { "known": false, "confidence": "low", "summary": "I do not have specific, independently verifiable information about Anchour.com as an individual entity in my knowledge base. Therefore, I cannot provide detailed insights into its operations or market position from my own data.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "Specific client portfolio and success stories", "Their market reputation and industry standing", "Details on their pricing models and service packages", "Key leadership or team expertise", "Any recent news or significant achievements" ], "alternatives": [], "business": null, "competitors": [] } ## Score by group - Machine access: 24/24 - Content legibility: 23/26 - Discovery surface: 8/20 - Identity & policy: 3/12 - Agent-facing performance: 8/8 - Agent protocols: 1/10 Failing checks: - [blocker] No llms.txt - [blocker] No MCP endpoint to call - [improvement] No stated policy for automated access - [improvement] No machine-readable contact - [improvement] Organisation structured data ## Add-on packs - E-commerce & product feeds: 15/100 (not part of the public score) ## FAQ Q: Is Anchour readable by AI agents? A: Anchour (anchour.com) scores 67 out of 100 for agent readiness, grade C, measured yesterday, on 29.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 anchour.com? A: The heaviest problems are: No llms.txt; No MCP endpoint to call; No stated policy for automated access; No machine-readable contact; Organisation structured data. 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 Anchour agent-readiness score calculated? A: Qomvia fetches public pages of anchour.com 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 (15/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 yesterday, on 29.09.2026. ## Related - Leaderboard: https://qomvia.com/leaderboard - Score another site: https://qomvia.com/