# 226lab (226lab.com): agent-readiness 58/100, grade D

> Rank 470 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-30T08:40:16.379Z. Page: https://qomvia.com/site/226lab-com  JSON: https://qomvia.com/api/score/226lab-com

## Summary

{
  "known": false,
  "confidence": "low",
  "summary": "I do not have pre-existing information in my knowledge base specifically about the website 226lab.com.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "Specific client base and success stories",
    "Market reputation and specific specializations",
    "Company size and team structure",
    "Pricing models for services",
    "Unique selling propositions beyond general marketing claims"
  ],
  "alternatives": [],
  "business": "I do not have pre-existing information about the specific business operations or market positioning of 226lab.com.",
  "competitors": []
}

## Score by group
- Machine access: 24/24
- Content legibility: 17/26
- Discovery surface: 8/20
- Identity & policy: 5/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 226lab readable by AI agents?
A: 226lab (226lab.com) scores 58 out of 100 for agent readiness, grade D, measured today, on 30.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 226lab.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 226lab agent-readiness score calculated?
A: Qomvia fetches public pages of 226lab.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 today, on 30.09.2026.

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