# Socialhearts (socialhearts.at): agent-readiness 55/100, grade D > Rank 551 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-30T04:20:16.409Z. Page: https://qomvia.com/site/socialhearts-at JSON: https://qomvia.com/api/score/socialhearts-at ## Summary { "known": false, "confidence": "low", "summary": "I do not have specific pre-existing knowledge about the website socialhearts.at. My training data does not contain distinct information about this particular domain.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "Specific business model and services offered.", "Primary target audience and their needs.", "Geographic focus of their operations.", "Key differentiating factors from competitors.", "Performance metrics or user feedback." ], "alternatives": [], "business": "I cannot identify the specific business model or sector for socialhearts.at based on my pre-existing knowledge.", "competitors": [] } ## Score by group - Machine access: 24/24 - Content legibility: 18/26 - Discovery surface: 5/20 - Identity & policy: 0/12 - Agent-facing performance: 8/8 - Agent protocols: 0/10 Failing checks: - [blocker] No llms.txt - [blocker] The site does not say who it is - [blocker] No API or feed to read - [blocker] No heading hierarchy - [blocker] No MCP endpoint to call ## FAQ Q: Is Socialhearts readable by AI agents? A: Socialhearts (socialhearts.at) scores 55 out of 100 for agent readiness, grade D, measured today, on 30.09.2026. 0 of 3 agent classes we test can use the site, and 5 checks currently block agents outright. Q: What stops agents from using socialhearts.at? A: The heaviest problems are: No llms.txt; The site does not say who it is; No API or feed to read; No heading hierarchy; No MCP endpoint to call. 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 Socialhearts agent-readiness score calculated? A: Qomvia fetches public pages of socialhearts.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 - Score another site: https://qomvia.com/