# Jager-pr (jager-pr.at): agent-readiness 63/100, grade C

> Rank 284 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-29T23:10:42.148Z. Page: https://qomvia.com/site/jager-pr-at  JSON: https://qomvia.com/api/score/jager-pr-at

## Summary
Category: Professional services
{
  "known": false,
  "confidence": "low",
  "summary": "My knowledge base does not contain specific information regarding jager-pr.at as a distinct entity. Therefore, I cannot provide a summary of what this site is or what it does from my own pre-existing knowledge.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "Specific client portfolio and success stories",
    "Current operational scope and team structure",
    "Market reputation and client satisfaction levels",
    "Detailed pricing structures for its services",
    "Long-term business strategy and ownership details"
  ],
  "alternatives": [],
  "business": null,
  "competitors": []
}

## Score by group
- Machine access: 24/24
- Content legibility: 22/26
- Discovery surface: 8/20
- Identity & policy: 3/12
- Agent-facing performance: 5/8
- Agent protocols: 1/10
Failing checks:
- [blocker] No llms.txt
- [blocker] No MCP endpoint to call
- [improvement] No stated policy for automated access
- [improvement] No machine-readable contact
- [improvement] Organisation structured data

## FAQ
Q: Is Jager-pr readable by AI agents?
A: Jager-pr (jager-pr.at) scores 63 out of 100 for agent readiness, grade C, measured yesterday, on 29.09.2026. 0 of 3 agent classes we test can use the site, and 2 checks currently block agents outright.

Q: What stops agents from using jager-pr.at?
A: The heaviest problems are: No llms.txt; No MCP endpoint to call; No stated policy for automated access; No machine-readable contact; Organisation structured data. 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 Jager-pr agent-readiness score calculated?
A: Qomvia fetches public pages of jager-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 — category ranking: https://qomvia.com/leaderboard/professional-services
- Score another site: https://qomvia.com/