# Jadimedia (jadimedia.ch): agent-readiness 54/100, grade D > Rank 598 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-30T16:10:16.208Z. Page: https://qomvia.com/site/jadimedia-ch JSON: https://qomvia.com/api/score/jadimedia-ch ## Summary { "known": false, "confidence": "low", "summary": "I do not have specific pre-existing knowledge about jadimedia.ch in my training data. Therefore, I cannot provide a summary of what this site is or what it does from my own knowledge.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "The specific services offered by Jadimedia.", "Their target audience and geographical focus.", "Their market position and competitive landscape.", "Their business model and operational specifics.", "The quality of their work and client testimonials." ], "alternatives": [], "business": "I cannot accurately describe the business of Jadimedia from my own knowledge.", "competitors": [] } ## Score by group - Machine access: 24/24 - Content legibility: 15/26 - Discovery surface: 5/20 - Identity & policy: 0/12 - Agent-facing performance: 8/8 - Agent protocols: 2/10 Failing checks: - [blocker] No llms.txt - [blocker] The site does not say who it is - [blocker] No API or feed to read - [blocker] No MCP endpoint to call - [improvement] No stated policy for automated access ## FAQ Q: Is Jadimedia readable by AI agents? A: Jadimedia (jadimedia.ch) scores 54 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 jadimedia.ch? A: The heaviest problems are: No llms.txt; The site does not say who it is; No API or feed to read; 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 Jadimedia agent-readiness score calculated? A: Qomvia fetches public pages of jadimedia.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. 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/