# Derhandler (derhandler.at): agent-readiness 50/100, grade D

> Rank 703 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-29T17:20:16.150Z. Page: https://qomvia.com/site/derhandler-at  JSON: https://qomvia.com/api/score/derhandler-at

## Summary

{
  "known": false,
  "confidence": "low",
  "summary": "I do not have specific information about the website derhandler.at in my knowledge base. Therefore, I cannot provide a summary of what it is or what it does.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "The specific services or products offered by derhandler.at.",
    "Its target audience and geographical focus.",
    "Its unique selling propositions or market position.",
    "Its operational history and reputation.",
    "Direct competitors in its specific market segment."
  ],
  "alternatives": [],
  "business": null,
  "competitors": []
}

## Score by group
- Machine access: 24/24
- Content legibility: 17/26
- Discovery surface: 3/20
- Identity & policy: 0/12
- Agent-facing performance: 5/8
- Agent protocols: 1/10
Failing checks:
- [blocker] No discoverable sitemap
- [blocker] No llms.txt
- [blocker] The site does not say who it is
- [blocker] No MCP endpoint to call
- [improvement] No stated policy for automated access

## FAQ
Q: Is Derhandler readable by AI agents?
A: Derhandler (derhandler.at) scores 50 out of 100 for agent readiness, grade D, measured yesterday, on 29.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 derhandler.at?
A: The heaviest problems are: No discoverable sitemap; No llms.txt; The site does not say who it is; 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 Derhandler agent-readiness score calculated?
A: Qomvia fetches public pages of derhandler.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/