# Studio (studio.com): agent-readiness 65/100, grade C > Rank 1201 of 3060 on Qomvia (rubric v2.3.0). Last scanned 2026-11-02T04:20:39.733Z. Page: https://qomvia.com/site/studio-com JSON: https://qomvia.com/api/score/studio-com ## Summary Category: Software and SaaS { "known": false, "confidence": "low", "summary": "", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "I do not have specific information about studio.com from my training data." ], "alternatives": [], "business": "", "competitors": [] } ## Score by group - Machine access: 24/24 - Content legibility: 21/26 - Discovery surface: 8/20 - Identity & policy: 7/12 - Agent-facing performance: 5/8 - Agent protocols: 0/10 Failing checks: - [blocker] No llms.txt - [blocker] No MCP endpoint to call - [improvement] No machine-readable contact - [improvement] Stated automated-access policy - [improvement] No Content Signals ## Add-on packs - E-commerce & product feeds: 27/100 (not part of the public score) ## AI mentions and rivals Named in 1 AI assistant answers. ## FAQ Q: Is Studio readable by AI agents? A: Studio (studio.com) scores 65 out of 100 for agent readiness, grade C, measured yesterday, on 02.11.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 studio.com? A: The heaviest problems are: No llms.txt; No MCP endpoint to call; No machine-readable contact; Stated automated-access policy; No Content Signals. 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 Studio agent-readiness score calculated? A: Qomvia fetches public pages of studio.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 (27/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 02.11.2026. ## Related - Leaderboard: https://qomvia.com/leaderboard — category ranking: https://qomvia.com/leaderboard/saas-software - Score another site: https://qomvia.com/