# Raphael (raphael.de): agent-readiness 26/100, grade F

> Rank 910 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-28T14:30:16.225Z. Page: https://qomvia.com/site/raphael-de  JSON: https://qomvia.com/api/score/raphael-de

## Summary

{
  "known": false,
  "confidence": "low",
  "summary": "I do not have specific, pre-existing knowledge about the website raphael.de from my training data. Therefore, I cannot provide a detailed summary of its purpose or operations.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "The specific business model and services offered by raphael.de.",
    "Its target audience and operational geography.",
    "Its market position and competitive landscape.",
    "Any particular strengths or unique selling points.",
    "Its history and ownership."
  ],
  "alternatives": [],
  "business": "I lack sufficient information to describe the business of raphael.de.",
  "competitors": []
}

## Score by group
- Machine access: 16/24
- Content legibility: 2/26
- Discovery surface: 0/20
- Identity & policy: 0/12
- Agent-facing performance: 8/8
- Agent protocols: 0/10
Failing checks:
- [blocker] No discoverable sitemap
- [blocker] No llms.txt
- [blocker] The site does not say who it is
- [blocker] Content is buried in boilerplate
- [blocker] No API or feed to read

## FAQ
Q: Is Raphael readable by AI agents?
A: Raphael (raphael.de) scores 26 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 8 checks currently block agents outright.

Q: What stops agents from using raphael.de?
A: The heaviest problems are: No discoverable sitemap; No llms.txt; The site does not say who it is; Content is buried in boilerplate; No API or feed to read. 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 Raphael agent-readiness score calculated?
A: Qomvia fetches public pages of raphael.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/