# Agencetrio (agencetrio.ch): agent-readiness 55/100, grade D > Rank 552 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-30T09:40:16.218Z. Page: https://qomvia.com/site/agencetrio-ch JSON: https://qomvia.com/api/score/agencetrio-ch ## Summary { "known": false, "confidence": "low", "summary": "I do not have specific pre-existing knowledge about Agence Trio (agencetrio.ch) from my training data or real-time access. Therefore, I cannot provide details about what this site is or what it does based on my own memory.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "Specific services and specializations of Agence Trio", "Target industries or client types", "Its market position and reputation in Switzerland", "Key past campaigns or client success stories", "Its unique selling propositions or competitive advantages" ], "alternatives": [], "business": null, "competitors": [] } ## Score by group - Machine access: 24/24 - Content legibility: 22/26 - Discovery surface: 3/20 - Identity & policy: 3/12 - Agent-facing performance: 3/8 - Agent protocols: 0/10 Failing checks: - [blocker] No llms.txt - [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 ## FAQ Q: Is Agencetrio readable by AI agents? A: Agencetrio (agencetrio.ch) 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 4 checks currently block agents outright. Q: What stops agents from using agencetrio.ch? A: The heaviest problems are: No llms.txt; No API or feed to read; Server responds too slowly for agents; No MCP endpoint to call; No stated policy for automated access. 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 Agencetrio agent-readiness score calculated? A: Qomvia fetches public pages of agencetrio.ch 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/