# Stefandacey (stefandacey.com): agent-readiness 72/100, grade C > Rank 70 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-28T23:40:18.642Z. Page: https://qomvia.com/site/stefandacey-com JSON: https://qomvia.com/api/score/stefandacey-com ## Summary { "known": false, "confidence": "low", "summary": "I do not have specific pre-existing knowledge about stefandacey.com within my training data. Therefore, I cannot provide a summary based on my own knowledge.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "Specific services and products offered by stefandacey.com", "Its primary target audience and customer base", "The geographic regions where it primarily operates", "Unique selling propositions or competitive advantages", "Its market position and reputation" ], "alternatives": [], "business": "I do not have sufficient pre-existing knowledge to describe the business of stefandacey.com.", "competitors": [] } ## Score by group - Machine access: 24/24 - Content legibility: 23/26 - Discovery surface: 9/20 - Identity & policy: 8/12 - Agent-facing performance: 8/8 - Agent protocols: 0/10 Failing checks: - [blocker] No API or feed to read - [blocker] No MCP endpoint to call - [improvement] No stated policy for automated access - [improvement] No Content Signals - [improvement] Content carries a date ## FAQ Q: Is Stefandacey readable by AI agents? A: Stefandacey (stefandacey.com) scores 72 out of 100 for agent readiness, grade C, measured 2 days ago, on 28.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 stefandacey.com? A: The heaviest problems are: No API or feed to read; No MCP endpoint to call; No stated policy for automated access; No Content Signals; 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 Stefandacey agent-readiness score calculated? A: Qomvia fetches public pages of stefandacey.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. 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 2 days ago, on 28.09.2026. ## Related - Leaderboard: https://qomvia.com/leaderboard - Score another site: https://qomvia.com/