# Norgay (norgay.at): agent-readiness 64/100, grade C > Rank 253 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-30T06:50:15.888Z. Page: https://qomvia.com/site/norgay-at JSON: https://qomvia.com/api/score/norgay-at ## Summary { "known": false, "confidence": "low", "summary": "I do not have specific knowledge about norgay.at from my training data. Therefore, I cannot provide a summary of what this site is and what it does.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "Its specific business model and range of services.", "Its target audience and typical client profile.", "Its market position, reputation, and unique selling propositions.", "Its primary geographic areas of operation.", "Its main competitors in the digital agency and interim management space." ], "alternatives": [], "business": "I do not have specific knowledge to describe this company's business.", "competitors": [] } ## Score by group - Machine access: 24/24 - Content legibility: 25/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 Norgay readable by AI agents? A: Norgay (norgay.at) scores 64 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 norgay.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 Norgay agent-readiness score calculated? A: Qomvia fetches public pages of norgay.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 - Score another site: https://qomvia.com/