# Azular (azular.ch): agent-readiness 50/100, grade D > Rank 704 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-30T10:00:17.037Z. Page: https://qomvia.com/site/azular-ch JSON: https://qomvia.com/api/score/azular-ch ## Summary { "known": false, "confidence": "low", "summary": "I do not have specific pre-existing knowledge about azular.ch as a distinct entity in my knowledge base. Therefore, I cannot provide details about its operations or services from my own data.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "Specific services and products offered by azular.ch", "Target audience and geographic reach", "Business model and market position", "Key technologies and frameworks utilized", "Customer testimonials or case studies" ], "alternatives": [], "business": "I do not have specific pre-existing knowledge about azular.ch.", "competitors": [] } ## Score by group - Machine access: 21/24 - Content legibility: 15/26 - Discovery surface: 8/20 - Identity & policy: 0/12 - Agent-facing performance: 5/8 - Agent protocols: 1/10 Failing checks: - [blocker] No llms.txt - [blocker] The site does not say who it is - [blocker] No heading hierarchy - [blocker] No MCP endpoint to call - [improvement] No stated policy for automated access ## Add-on packs - E-commerce & product feeds: 15/100 (not part of the public score) ## FAQ Q: Is Azular readable by AI agents? A: Azular (azular.ch) scores 50 out of 100 for agent readiness, grade D, measured today, on 30.09.2026. 0 of 3 agent classes we test can use the site, and 4 checks currently block agents outright. Q: What stops agents from using azular.ch? A: The heaviest problems are: No llms.txt; The site does not say who it is; No heading hierarchy; No MCP endpoint to call; No stated policy for automated access. 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 Azular agent-readiness score calculated? A: Qomvia fetches public pages of azular.ch 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. E-commerce & product feeds checks are scored separately (15/100) and do not affect the public score or rank. 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/