# Stark (stark.ch): agent-readiness 60/100, grade C

> Rank 398 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-28T01:00:16.722Z. Page: https://qomvia.com/site/stark-ch  JSON: https://qomvia.com/api/score/stark-ch

## Summary

{
  "known": false,
  "confidence": "low",
  "summary": "I do not have specific, distinct knowledge about stark.ch from my training data. Therefore, I cannot provide a detailed summary of its operations or market position based on my own information.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "Specific product catalog and pricing details",
    "Precise target market demographics and needs",
    "Market share and financial performance",
    "Customer satisfaction metrics and reviews",
    "Detailed geographical service areas and logistics"
  ],
  "alternatives": [],
  "business": null,
  "competitors": []
}

## Score by group
- Machine access: 24/24
- Content legibility: 21/26
- Discovery surface: 5/20
- Identity & policy: 5/12
- Agent-facing performance: 5/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 Stark readable by AI agents?
A: Stark (stark.ch) scores 60 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 3 checks currently block agents outright.

Q: What stops agents from using stark.ch?
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 Stark agent-readiness score calculated?
A: Qomvia fetches public pages of stark.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 2 days ago, on 28.09.2026.

## Related
- Leaderboard: https://qomvia.com/leaderboard
- Score another site: https://qomvia.com/