# 3aw (3aw.com): agent-readiness 59/100, grade D

> Rank 445 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-29T03:50:43.611Z. Page: https://qomvia.com/site/3aw-com  JSON: https://qomvia.com/api/score/3aw-com

## Summary
Category: Professional services
{
  "known": false,
  "confidence": "low",
  "summary": "This specific website, 3aw.com, is not distinctly recognized in my knowledge base as a specific entity separate from general web content. I cannot provide information about its purpose or operations based on pre-existing knowledge.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "The precise nature of its business operations",
    "Its primary target audience",
    "Its geographical scope of operation",
    "Specific products or services it offers",
    "Its competitive landscape"
  ],
  "alternatives": [],
  "business": null,
  "competitors": []
}

## Score by group
- Machine access: 24/24
- Content legibility: 20/26
- Discovery surface: 8/20
- Identity & policy: 3/12
- Agent-facing performance: 3/8
- Agent protocols: 1/10
Failing checks:
- [blocker] No llms.txt
- [blocker] Server responds too slowly for agents
- [blocker] No heading hierarchy
- [blocker] No MCP endpoint to call
- [improvement] No stated policy for automated access

## FAQ
Q: Is 3aw readable by AI agents?
A: 3aw (3aw.com) scores 59 out of 100 for agent readiness, grade D, measured yesterday, on 29.09.2026. 0 of 3 agent classes we test can use the site, and 4 checks currently block agents outright.

Q: What stops agents from using 3aw.com?
A: The heaviest problems are: No llms.txt; Server responds too slowly for agents; No heading hierarchy; No MCP endpoint to call; No stated policy for automated access. 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 3aw agent-readiness score calculated?
A: Qomvia fetches public pages of 3aw.com 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 yesterday, on 29.09.2026.

## Related
- Leaderboard: https://qomvia.com/leaderboard — category ranking: https://qomvia.com/leaderboard/professional-services
- Score another site: https://qomvia.com/