Agent-readiness report
No class of agent can use Laus today: they cannot call it as a tool.
laus.co, last scanned yesterday, on 29.09.2026
Agent classes working
0/3
Score history
±04 scans since 21.09.2026
0 of 3 agent classes work
Answer engines have no reliable label for the page, so they invent one or skip it.
BlockerNothing tells an agent where the useful pages, feeds and policies are.
BlockerA model cannot tell that this domain is the brand it was asked about.
BlockerEvery integration has to scrape HTML, which most integrators will not do.
BlockerTool-calling assistants have no function to call, so they can only scrape.
BlockerFree dashboard
Weekly re-scans, the fix for every gap above, and the rank moves of your rivals.
Your dashboard
We email you a sign-in link and add laus.co to your dashboard.
5 domains free, unlimited with a plan.
Laus exposes 2 of 8 interfaces agents look for: AI crawler access, Bot user-agent handling.
Locked
All 8 interfaces and 26 checks for laus.co
See which interface is missing, what each check looked for, and what to change to pass it. Free account, no card.
View detailed signalsThe seal
laus.co is in progress: Partly readable. Not yet good enough to display a public mark. Reach 60/100 to earn Agent-Readable and display it on your site.
Preview of Agent-Readable, greyed out until laus.co scores 60/100. There is no embed code until it is earned.
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.
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.
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.
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.
Scores are computed from public HTTP responses only. We never submit forms, never attempt a purchase and never bypass a bot challenge. Disagree with a result? Request a correction or opt this domain out.