# Echo3 (echo3.de): agent-readiness 29/100, grade F

> Rank 896 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-28T09:10:41.712Z. Page: https://qomvia.com/site/echo3-de  JSON: https://qomvia.com/api/score/echo3-de

## Summary

{
  "known": false,
  "confidence": "low",
  "summary": "I do not have specific information about the website echo3.de in my knowledge base. Therefore, I cannot provide a summary of what this site is or what it does.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "The primary services or products offered by echo3.de",
    "Its target audience and market position",
    "Its operational geography and business model",
    "Any unique strengths or distinguishing features",
    "Its main competitors in the market"
  ],
  "alternatives": [],
  "business": "I do not have enough information to describe what this company does.",
  "competitors": []
}

## Score by group
- Machine access: 16/24
- Content legibility: 5/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 Echo3 readable by AI agents?
A: Echo3 (echo3.de) scores 29 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 echo3.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 Echo3 agent-readiness score calculated?
A: Qomvia fetches public pages of echo3.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/