# Sydney (sydney.at): agent-readiness 26/100, grade F

> Rank 910 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-30T06:20:43.681Z. Page: https://qomvia.com/site/sydney-at  JSON: https://qomvia.com/api/score/sydney-at

## Summary

{
  "known": false,
  "confidence": "low",
  "summary": "I do not have specific pre-existing knowledge about the website sydney.at from my training data. Therefore, I cannot provide details on its operations, business model, or market position.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "Specific services and products offered",
    "Company's unique selling proposition",
    "Primary geographical market beyond the TLD",
    "Customer demographics and psychographics",
    "Financial performance or market share"
  ],
  "alternatives": [],
  "business": "I cannot describe the business as I lack specific information about this domain.",
  "competitors": []
}

## Score by group
- Machine access: 16/24
- Content legibility: 2/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 Sydney readable by AI agents?
A: Sydney (sydney.at) scores 26 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 8 checks currently block agents outright.

Q: What stops agents from using sydney.at?
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 Sydney agent-readiness score calculated?
A: Qomvia fetches public pages of sydney.at 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/