# Aspkom (aspkom.ch): agent-readiness 69/100, grade C > Rank 125 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-30T10:20:15.902Z. Page: https://qomvia.com/site/aspkom-ch JSON: https://qomvia.com/api/score/aspkom-ch ## Summary { "known": false, "confidence": "low", "summary": "I do not have specific pre-existing knowledge about Aspkom.ch from my training data. Therefore, I cannot provide a summary based on my direct understanding of the website's operations or market position.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "The specific services provided by Aspkom.ch beyond general growth consulting", "Its primary target industries or client types", "Its unique methodologies or proprietary tools", "Its operational history, market reputation, or client testimonials", "Its typical pricing models or project engagement structures" ], "alternatives": [], "business": "A growth agency based in St. Gallen, Switzerland, focused on helping businesses increase revenue and profit through strategic consulting and marketing initiatives.", "competitors": [ "dreifive.com", "blueglass.ch", "digital-guru.ch", "necom.ch", "smart-up.ch", "webstyle.ch", "econnectivity.ch" ] } ## Score by group - Machine access: 24/24 - Content legibility: 23/26 - Discovery surface: 13/20 - Identity & policy: 5/12 - Agent-facing performance: 3/8 - Agent protocols: 1/10 Failing checks: - [blocker] Server responds too slowly for agents - [blocker] No MCP endpoint to call - [improvement] No stated policy for automated access - [improvement] No machine-readable contact - [improvement] No Content Signals ## AI mentions and rivals - dreifive.com: not measured - blueglass.ch: 68/100 https://qomvia.com/site/blueglass-ch ## FAQ Q: Is Aspkom readable by AI agents? A: Aspkom (aspkom.ch) scores 69 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 2 checks currently block agents outright. Q: What stops agents from using aspkom.ch? A: The heaviest problems are: Server responds too slowly for agents; No MCP endpoint to call; No stated policy for automated access; No machine-readable contact; 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 Aspkom agent-readiness score calculated? A: Qomvia fetches public pages of aspkom.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 - Score another site: https://qomvia.com/