# Instride (instride.ch): agent-readiness 32/100, grade F

> Rank 880 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-27T15:40:16.776Z. Page: https://qomvia.com/site/instride-ch  JSON: https://qomvia.com/api/score/instride-ch

## Summary

{
  "known": false,
  "confidence": "low",
  "summary": "I do not have specific, independently verified information about instride.ch in my knowledge base. Therefore, I cannot confidently describe what this site is or what it does based on my training data.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "Specific service offerings and specialization",
    "Target client segments and industries served",
    "Unique value propositions or methodologies",
    "Market reputation and specific case studies",
    "Competitive landscape relative to its exact positioning"
  ],
  "alternatives": [],
  "business": null,
  "competitors": []
}

## Score by group
- Machine access: 11/24
- Content legibility: 7/26
- Discovery surface: 3/20
- Identity & policy: 3/12
- Agent-facing performance: 8/8
- Agent protocols: 0/10
Failing checks:
- [blocker] No llms.txt
- [blocker] The site does not say who it is
- [blocker] Content is buried in boilerplate
- [blocker] Bot protection blocks declared agents
- [blocker] No API or feed to read

## FAQ
Q: Is Instride readable by AI agents?
A: Instride (instride.ch) scores 32 out of 100 for agent readiness, grade F, measured 3 days ago, on 27.09.2026. 0 of 3 agent classes we test can use the site, and 8 checks currently block agents outright.

Q: What stops agents from using instride.ch?
A: The heaviest problems are: No llms.txt; The site does not say who it is; Content is buried in boilerplate; Bot protection blocks declared agents; 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 Instride agent-readiness score calculated?
A: Qomvia fetches public pages of instride.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 3 days ago, on 27.09.2026.

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