# Rubbeldiekatz (rubbeldiekatz.com): agent-readiness 40/100, grade D > Rank 836 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-28T15:00:46.491Z. Page: https://qomvia.com/site/rubbeldiekatz-com JSON: https://qomvia.com/api/score/rubbeldiekatz-com ## Summary Category: Events and entertainment { "known": false, "confidence": "low", "summary": "I do not have specific prior knowledge about the website rubbeldiekatz.com from my training data. Therefore, I cannot provide a confident summary of its specific operations or offerings.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "The specific type of 'musical journey' or 'events' offered", "The primary target audience demographics", "The geographic regions where events are held", "The business model and revenue streams of the entity behind the site", "Its reputation or user feedback" ], "alternatives": [], "business": null, "competitors": [] } ## Score by group - Machine access: 24/24 - Content legibility: 6/26 - Discovery surface: 5/20 - Identity & policy: 0/12 - Agent-facing performance: 5/8 - Agent protocols: 0/10 Failing checks: - [blocker] Page metadata is incomplete - [blocker] No llms.txt - [blocker] The site does not say who it is - [blocker] No API or feed to read - [blocker] No heading hierarchy ## FAQ Q: Is Rubbeldiekatz readable by AI agents? A: Rubbeldiekatz (rubbeldiekatz.com) scores 40 out of 100 for agent readiness, grade D, measured 2 days ago, on 28.09.2026. 0 of 3 agent classes we test can use the site, and 6 checks currently block agents outright. Q: What stops agents from using rubbeldiekatz.com? A: The heaviest problems are: Page metadata is incomplete; No llms.txt; The site does not say who it is; No API or feed to read; No heading hierarchy. 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 Rubbeldiekatz agent-readiness score calculated? A: Qomvia fetches public pages of rubbeldiekatz.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. 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 2 days ago, on 28.09.2026. ## Related - Leaderboard: https://qomvia.com/leaderboard — category ranking: https://qomvia.com/leaderboard/events-entertainment - Score another site: https://qomvia.com/