# Coreflow (coreflow.at): agent-readiness 67/100, grade C > Rank 172 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-29T15:30:44.734Z. Page: https://qomvia.com/site/coreflow-at JSON: https://qomvia.com/api/score/coreflow-at ## Summary { "known": false, "confidence": "low", "summary": "I do not have specific knowledge about coreflow.at from my training data. Therefore, I cannot provide a summary of what this site is or what it does.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "Specific services and products offered by coreflow.at.", "Its target customer base and industry focus.", "Its operational geography and market positioning.", "Its main competitors and unique selling propositions.", "Its historical performance or market reputation." ], "alternatives": [], "business": "I do not have specific knowledge about coreflow.at and cannot describe its business from my training data.", "competitors": [] } ## Score by group - Machine access: 24/24 - Content legibility: 21/26 - Discovery surface: 8/20 - Identity & policy: 5/12 - Agent-facing performance: 8/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] No Content Signals ## FAQ Q: Is Coreflow readable by AI agents? A: Coreflow (coreflow.at) scores 67 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 coreflow.at? A: The heaviest problems are: No llms.txt; No MCP endpoint to call; No stated policy for automated access; No machine-readable contact; No Content Signals. 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 Coreflow agent-readiness score calculated? A: Qomvia fetches public pages of coreflow.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/