# Laus (laus.co): agent-readiness 41/100, grade D

> Rank 828 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-29T15:40:44.195Z. Page: https://qomvia.com/site/laus-co  JSON: https://qomvia.com/api/score/laus-co

## Summary

{
  "known": false,
  "confidence": "low",
  "summary": "I do not have specific information about laus.co in my knowledge base. The provided information suggests it is a website announcing an upcoming launch, with 'Launching Soon' and 'Contact Us' sections.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "The specific products or services laus.co plans to offer.",
    "Its target market and customer demographics.",
    "The geographic regions it intends to serve.",
    "Its unique value proposition or competitive advantages.",
    "The current status of its launch and operations."
  ],
  "alternatives": [],
  "business": "I do not have specific information about the business purpose or offerings of laus.co.",
  "competitors": []
}

## Score by group
- Machine access: 21/24
- Content legibility: 9/26
- Discovery surface: 3/20
- Identity & policy: 0/12
- Agent-facing performance: 8/8
- Agent protocols: 0/10
Failing checks:
- [blocker] Page metadata is incomplete
- [blocker] No llms.txt
- [blocker] The site does not say who it is
- [blocker] No API or feed to read
- [blocker] No MCP endpoint to call

## FAQ
Q: Is Laus readable by AI agents?
A: Laus (laus.co) scores 41 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 5 checks currently block agents outright.

Q: What stops agents from using laus.co?
A: The heaviest problems are: Page metadata is incomplete; No llms.txt; The site does not say who it is; No API or feed to read; No MCP endpoint to call. 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 Laus agent-readiness score calculated?
A: Qomvia fetches public pages of laus.co 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
- Score another site: https://qomvia.com/