# Kalebaker (kalebaker.at): agent-readiness 67/100, grade C > Rank 172 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-29T21:10:43.561Z. Page: https://qomvia.com/site/kalebaker-at JSON: https://qomvia.com/api/score/kalebaker-at ## Summary { "known": false, "confidence": "low", "summary": "I do not have specific information about kalebaker.at in my knowledge base. Therefore, I cannot provide a summary of what this site is or what it does based on my own knowledge.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "Specific services and packages offered", "Clientele and target audience", "Operational geography and market focus", "Reputation, client testimonials, or case studies", "Pricing models and typical project scopes" ], "alternatives": [], "business": "I lack specific knowledge to define the business model, target audience, or operational location for kalebaker.at.", "competitors": [] } ## Score by group - Machine access: 24/24 - Content legibility: 19/26 - Discovery surface: 12/20 - Identity & policy: 3/12 - Agent-facing performance: 8/8 - Agent protocols: 1/10 Failing checks: - [blocker] No MCP endpoint to call - [improvement] No stated policy for automated access - [improvement] No machine-readable contact - [improvement] Organisation structured data - [improvement] No Content Signals ## FAQ Q: Is Kalebaker readable by AI agents? A: Kalebaker (kalebaker.at) scores 67 out of 100 for agent readiness, grade C, measured yesterday, on 29.09.2026. 0 of 3 agent classes we test can use the site, and 1 check currently block agents outright. Q: What stops agents from using kalebaker.at? A: The heaviest problems are: No MCP endpoint to call; No stated policy for automated access; No machine-readable contact; Organisation structured data; 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 Kalebaker agent-readiness score calculated? A: Qomvia fetches public pages of kalebaker.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 - Score another site: https://qomvia.com/