# Art-redaktionsteam (art-redaktionsteam.at): agent-readiness 55/100, grade D > Rank 552 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-29T10:50:44.953Z. Page: https://qomvia.com/site/art-redaktionsteam-at JSON: https://qomvia.com/api/score/art-redaktionsteam-at ## Summary Category: Professional services { "known": false, "confidence": "low", "summary": "My knowledge base does not contain specific information about art-redaktionsteam.at. Therefore, I cannot provide details on what this site is or what it does.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "Specific purpose and content of the website.", "The identity or background of the 'art editorial team'.", "Any services or products offered by the site.", "Its target audience or community.", "Operational scope or geographic focus beyond the '.at' domain." ], "alternatives": [], "business": null, "competitors": [] } ## Score by group - Machine access: 24/24 - Content legibility: 23/26 - Discovery surface: 5/20 - Identity & policy: 0/12 - Agent-facing performance: 3/8 - Agent protocols: 0/10 Failing checks: - [blocker] No llms.txt - [blocker] The site does not say who it is - [blocker] No API or feed to read - [blocker] Server responds too slowly for agents - [blocker] No MCP endpoint to call ## FAQ Q: Is Art-redaktionsteam readable by AI agents? A: Art-redaktionsteam (art-redaktionsteam.at) scores 55 out of 100 for agent readiness, grade D, measured yesterday, on 29.09.2026. 0 of 3 agent classes we test can use the site, and 5 checks currently block agents outright. Q: What stops agents from using art-redaktionsteam.at? A: The heaviest problems are: No llms.txt; The site does not say who it is; No API or feed to read; Server responds too slowly for agents; No MCP endpoint to call. 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 Art-redaktionsteam agent-readiness score calculated? A: Qomvia fetches public pages of art-redaktionsteam.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 yesterday, on 29.09.2026. ## Related - Leaderboard: https://qomvia.com/leaderboard — category ranking: https://qomvia.com/leaderboard/professional-services - Score another site: https://qomvia.com/