# Picker-pr (picker-pr.at): agent-readiness 81/100, grade B

> Rank 15 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-30T00:10:47.114Z. Page: https://qomvia.com/site/picker-pr-at  JSON: https://qomvia.com/api/score/picker-pr-at

## Summary
Category: Professional services
{
  "known": false,
  "confidence": "low",
  "summary": null,
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "Cannot provide details about its specific services or products.",
    "Cannot identify its primary target audience or client base.",
    "Cannot determine its geographical focus beyond its name.",
    "Cannot assess its market position or competitive advantages.",
    "Cannot evaluate its reputation or any public perception."
  ],
  "alternatives": [],
  "business": null,
  "competitors": []
}

## Score by group
- Machine access: 24/24
- Content legibility: 21/26
- Discovery surface: 20/20
- Identity & policy: 6/12
- Agent-facing performance: 5/8
- Agent protocols: 5/10
Failing checks:
- [improvement] No stated policy for automated access
- [improvement] Title, description and canonical URL
- [improvement] Organisation structured data
- [improvement] No Content Signals
- [improvement] Time to first byte

## Add-on packs
- E-commerce & product feeds: 44/100 (not part of the public score)

## FAQ
Q: Is Picker-pr readable by AI agents?
A: Picker-pr (picker-pr.at) scores 81 out of 100 for agent readiness, grade B, measured today, on 30.09.2026. 1 of 3 agent classes we test can use the site, and 0 checks currently block agents outright.

Q: What stops agents from using picker-pr.at?
A: The heaviest problems are: No stated policy for automated access; Title, description and canonical URL; Organisation structured data; No Content Signals; Time to first byte. 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 Picker-pr agent-readiness score calculated?
A: Qomvia fetches public pages of picker-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. E-commerce & product feeds checks are scored separately (44/100) and do not affect the public score or rank.

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 today, on 30.09.2026.

## Related
- Leaderboard: https://qomvia.com/leaderboard — category ranking: https://qomvia.com/leaderboard/professional-services
- Score another site: https://qomvia.com/