# Viermalvier (viermalvier.at): agent-readiness 62/100, grade C > Rank 326 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-30T07:10:15.952Z. Page: https://qomvia.com/site/viermalvier-at JSON: https://qomvia.com/api/score/viermalvier-at ## Summary Category: Professional services { "known": false, "confidence": "low", "summary": "I do not have specific pre-existing knowledge about viermalvier.at from my training data. My model has not been trained on detailed information concerning this particular entity.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "Specific client portfolio", "Reputation and market standing", "Detailed service offerings and specializations", "Pricing structures", "Operational geography beyond general location" ], "alternatives": [], "business": "Information about this specific company is not available in my knowledge base.", "competitors": [] } ## Score by group - Machine access: 24/24 - Content legibility: 23/26 - Discovery surface: 8/20 - Identity & policy: 3/12 - Agent-facing performance: 3/8 - Agent protocols: 1/10 Failing checks: - [blocker] No llms.txt - [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 ## FAQ Q: Is Viermalvier readable by AI agents? A: Viermalvier (viermalvier.at) scores 62 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 viermalvier.at? A: The heaviest problems are: No llms.txt; Server responds too slowly for agents; 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 Viermalvier agent-readiness score calculated? A: Qomvia fetches public pages of viermalvier.at 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/professional-services - Score another site: https://qomvia.com/