# 8am (8am.ch): agent-readiness 66/100, grade C

> Rank 198 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-30T08:00:15.767Z. Page: https://qomvia.com/site/8am-ch  JSON: https://qomvia.com/api/score/8am-ch

## Summary

{
  "known": false,
  "confidence": "low",
  "summary": "I do not have specific, pre-existing knowledge about the website 8am.ch to provide a confident summary of what it is and what it does.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "The specific nature of services or products offered by 8am.ch.",
    "The target audience or customer base of 8am.ch.",
    "The primary operational geography of 8am.ch.",
    "The specific business model or revenue streams of 8am.ch.",
    "Direct competitors or common alternatives to 8am.ch."
  ],
  "alternatives": [],
  "business": "I cannot confidently describe what this company does, for whom and where.",
  "competitors": []
}

## Score by group
- Machine access: 24/24
- Content legibility: 23/26
- Discovery surface: 8/20
- Identity & policy: 3/12
- Agent-facing performance: 8/8
- Agent protocols: 0/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] Organisation structured data

## FAQ
Q: Is 8am readable by AI agents?
A: 8am (8am.ch) scores 66 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 2 checks currently block agents outright.

Q: What stops agents from using 8am.ch?
A: The heaviest problems are: No llms.txt; 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 8am agent-readiness score calculated?
A: Qomvia fetches public pages of 8am.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/