# Plexium (plexium.rweb.site): agent-readiness 65/100, grade C > Rank 230 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-30T14:00:54.745Z. Page: https://qomvia.com/site/plexium-rweb-site JSON: https://qomvia.com/api/score/plexium-rweb-site ## Summary Category: Software and SaaS { "known": false, "confidence": "low", "summary": "I do not have specific pre-existing knowledge about plexium.rweb.site in my training data, nor any independently verified information regarding its operations or purpose.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "The specific services, products, or applications offered by plexium.rweb.site.", "Its target audience, market position, or operational scale.", "Its business model, reliability, or trustworthiness.", "Any associated risks, benefits, or unique selling points for users.", "Its ownership, founding history, or financial performance." ], "alternatives": [], "business": null, "competitors": [] } ## Score by group - Machine access: 24/24 - Content legibility: 23/26 - Discovery surface: 5/20 - Identity & policy: 5/12 - Agent-facing performance: 8/8 - Agent protocols: 0/10 Failing checks: - [blocker] No llms.txt - [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 ## FAQ Q: Is Plexium readable by AI agents? A: Plexium (plexium.rweb.site) scores 65 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 plexium.rweb.site? A: The heaviest problems are: No llms.txt; No API or feed to read; 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 Plexium agent-readiness score calculated? A: Qomvia fetches public pages of plexium.rweb.site 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/saas-software - Score another site: https://qomvia.com/