# Pulsaragency (pulsaragency.fr): agent-readiness 67/100, grade C > Rank 172 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-28T22:00:17.069Z. Page: https://qomvia.com/site/pulsaragency-fr JSON: https://qomvia.com/api/score/pulsaragency-fr ## Summary Category: IT services and agencies { "known": false, "confidence": "low", "summary": "I do not possess specific pre-existing knowledge about the website pulsaragency.fr from my training data. Therefore, I cannot provide an informed summary about what this site is or what it does based on my own knowledge.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "Specific business details and history", "Current market position and reputation", "Operational scale and number of employees", "Actual client list and project portfolio", "Financial performance and profitability" ], "alternatives": [], "business": null, "competitors": [] } ## Score by group - Machine access: 24/24 - Content legibility: 23/26 - Discovery surface: 9/20 - Identity & policy: 3/12 - Agent-facing performance: 8/8 - Agent protocols: 0/10 Failing checks: - [blocker] No API or feed to read - [blocker] No MCP endpoint to call - [improvement] No stated policy for automated access - [improvement] No machine-readable contact - [improvement] Organisation structured data ## FAQ Q: Is Pulsaragency readable by AI agents? A: Pulsaragency (pulsaragency.fr) scores 67 out of 100 for agent readiness, grade C, measured 2 days ago, on 28.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 pulsaragency.fr? A: The heaviest problems are: No API or feed to read; No MCP endpoint to call; No stated policy for automated access; No machine-readable contact; Organisation structured data. 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 Pulsaragency agent-readiness score calculated? A: Qomvia fetches public pages of pulsaragency.fr 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 2 days ago, on 28.09.2026. ## Related - Leaderboard: https://qomvia.com/leaderboard — category ranking: https://qomvia.com/leaderboard/it-services - Score another site: https://qomvia.com/