# Lumen-pr (lumen-pr.at): agent-readiness 54/100, grade D

> Rank 600 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-29T08:30:15.823Z. Page: https://qomvia.com/site/lumen-pr-at  JSON: https://qomvia.com/api/score/lumen-pr-at

## Summary

{
  "known": false,
  "confidence": "low",
  "summary": "I do not have specific pre-existing knowledge about the website lumen-pr.at beyond its domain and the provided descriptive text. Therefore, I cannot confidently describe what this site is or what it does.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "Specific services offered by this company",
    "Its target client base and industries",
    "Its market reputation and track record",
    "Its key personnel or leadership",
    "Its financial stability or size"
  ],
  "alternatives": [],
  "business": null,
  "competitors": []
}

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

## FAQ
Q: Is Lumen-pr readable by AI agents?
A: Lumen-pr (lumen-pr.at) scores 54 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 3 checks currently block agents outright.

Q: What stops agents from using lumen-pr.at?
A: The heaviest problems are: No llms.txt; The site does not say who it is; No MCP endpoint to call; Title, description and canonical URL; 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 Lumen-pr agent-readiness score calculated?
A: Qomvia fetches public pages of lumen-pr.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/