# Studio-core (studio-core.ch): agent-readiness 61/100, grade C > Rank 351 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-30T01:00:41.048Z. Page: https://qomvia.com/site/studio-core-ch JSON: https://qomvia.com/api/score/studio-core-ch ## Summary Category: Sports and outdoor { "known": false, "confidence": "high", "summary": "", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "I do not have specific pre-trained information about this website or business.", "I cannot provide details on its services, target audience, or operational geography.", "My knowledge base does not contain specific data on its business model or market position.", "I cannot list specific strengths or areas of improvement.", "I cannot identify direct competitors or alternatives." ], "alternatives": [], "business": "", "competitors": [] } ## Score by group - Machine access: 24/24 - Content legibility: 19/26 - Discovery surface: 9/20 - Identity & policy: 3/12 - Agent-facing performance: 6/8 - Agent protocols: 0/10 Failing checks: - [blocker] No API or feed to read - [blocker] No heading hierarchy - [blocker] No MCP endpoint to call - [improvement] No stated policy for automated access - [improvement] No machine-readable contact ## AI mentions and rivals Named in 3 AI assistant answers. ## FAQ Q: Is Studio-core readable by AI agents? A: Studio-core (studio-core.ch) scores 61 out of 100 for agent readiness, grade C, measured today, on 30.09.2026. 0 of 3 agent classes we test can use the site, and 3 checks currently block agents outright. Q: What stops agents from using studio-core.ch? A: The heaviest problems are: No API or feed to read; No heading hierarchy; No MCP endpoint to call; No stated policy for automated access; No machine-readable contact. 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-core agent-readiness score calculated? A: Qomvia fetches public pages of studio-core.ch 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 today, on 30.09.2026. ## Related - Leaderboard: https://qomvia.com/leaderboard — category ranking: https://qomvia.com/leaderboard/sports-outdoor - Score another site: https://qomvia.com/