# Cryptoweb3 (cryptoweb3.ch): agent-readiness 32/100, grade F > Rank 880 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-30T14:10:52.609Z. Page: https://qomvia.com/site/cryptoweb3-ch JSON: https://qomvia.com/api/score/cryptoweb3-ch ## Summary { "known": false, "confidence": null, "summary": "This website, cryptoweb3.ch, is explicitly stated to be under construction. Therefore, its intended purpose, offerings, and operations are currently undefined.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "The specific purpose or services cryptoweb3.ch intends to offer.", "The target audience for cryptoweb3.ch once it launches.", "The geographic scope of its operations beyond the .ch domain.", "Any unique selling propositions or strengths it might possess.", "Whether the site will ever launch or what its final content will be." ], "alternatives": [], "business": null, "competitors": [] } ## Score by group - Machine access: 16/24 - Content legibility: 8/26 - Discovery surface: 0/20 - Identity & policy: 0/12 - Agent-facing performance: 8/8 - Agent protocols: 0/10 Failing checks: - [blocker] No discoverable sitemap - [blocker] No llms.txt - [blocker] The site does not say who it is - [blocker] Content is buried in boilerplate - [blocker] No API or feed to read ## FAQ Q: Is Cryptoweb3 readable by AI agents? A: Cryptoweb3 (cryptoweb3.ch) scores 32 out of 100 for agent readiness, grade F, measured today, on 30.09.2026. 0 of 3 agent classes we test can use the site, and 7 checks currently block agents outright. Q: What stops agents from using cryptoweb3.ch? A: The heaviest problems are: No discoverable sitemap; No llms.txt; The site does not say who it is; Content is buried in boilerplate; No API or feed to read. 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 Cryptoweb3 agent-readiness score calculated? A: Qomvia fetches public pages of cryptoweb3.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/