# Jpmedia (jpmedia.de): agent-readiness 24/100, grade F > Rank 920 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-28T11:40:15.972Z. Page: https://qomvia.com/site/jpmedia-de JSON: https://qomvia.com/api/score/jpmedia-de ## Summary { "known": false, "confidence": "low", "summary": "I do not have specific pre-existing knowledge about jpmedia.de as a distinct entity in my training data. Therefore, I cannot provide a summary based on my own knowledge.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "The specific business model and services offered by jpmedia.de", "Its target audience and geographic operational scope", "Its main competitors and market position", "Any unique selling propositions or notable achievements", "Its history or founding principles" ], "alternatives": [], "business": "I cannot confidently identify what this company does, for whom, and where, based on my knowledge.", "competitors": [] } ## Score by group - Machine access: 16/24 - Content legibility: 0/26 - Discovery surface: 0/20 - Identity & policy: 0/12 - Agent-facing performance: 8/8 - Agent protocols: 0/10 Failing checks: - [blocker] Page metadata is incomplete - [blocker] No discoverable sitemap - [blocker] No llms.txt - [blocker] The site does not say who it is - [blocker] Content is buried in boilerplate ## FAQ Q: Is Jpmedia readable by AI agents? A: Jpmedia (jpmedia.de) scores 24 out of 100 for agent readiness, grade F, measured 2 days ago, on 28.09.2026. 0 of 3 agent classes we test can use the site, and 9 checks currently block agents outright. Q: What stops agents from using jpmedia.de? A: The heaviest problems are: Page metadata is incomplete; No discoverable sitemap; No llms.txt; The site does not say who it is; Content is buried in boilerplate. 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 Jpmedia agent-readiness score calculated? A: Qomvia fetches public pages of jpmedia.de 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 - Score another site: https://qomvia.com/