# Web-house (web-house.at): agent-readiness 63/100, grade C

> Rank 283 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-30T06:50:47.683Z. Page: https://qomvia.com/site/web-house-at  JSON: https://qomvia.com/api/score/web-house-at

## Summary
Category: IT services and agencies
{
  "known": false,
  "confidence": "low",
  "summary": "I do not have specific information about web-house.at within my knowledge base.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "Specific services and products offered",
    "Target customer demographics and firmographics",
    "Geographic areas of operation",
    "Unique selling propositions and competitive advantages",
    "Financial performance or market position"
  ],
  "alternatives": [],
  "business": "No specific information available in my knowledge base.",
  "competitors": []
}

## Score by group
- Machine access: 24/24
- Content legibility: 22/26
- Discovery surface: 9/20
- Identity & policy: 5/12
- Agent-facing performance: 3/8
- Agent protocols: 0/10
Failing checks:
- [blocker] No API or feed to read
- [blocker] Server responds too slowly for agents
- [blocker] No MCP endpoint to call
- [improvement] No stated policy for automated access
- [improvement] No machine-readable contact

## FAQ
Q: Is Web-house readable by AI agents?
A: Web-house (web-house.at) scores 63 out of 100 for agent readiness, grade C, measured today, on 30.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 web-house.at?
A: The heaviest problems are: No API or feed to read; Server responds too slowly for agents; No MCP endpoint to call; No stated policy for automated access; No machine-readable contact. 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 Web-house agent-readiness score calculated?
A: Qomvia fetches public pages of web-house.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 today, on 30.09.2026.

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