Agent-readiness report, Professional services
No class of agent can use Lumeos today: they cannot read it, call it as a tool or extract its content.
lumeos.ch, last scanned 3 days ago, on 27.09.2026
Agent classes working
0/3
Score history
▼ 224 scans since 20.09.2026
0 of 3 agent classes work
Answer engines have no reliable label for the page, so they invent one or skip it.
BlockerA model summarising the page quotes navigation and cookie banners instead of the content.
BlockerRetrieval chunks the page badly, so the passage a model quotes lacks its context.
BlockerAgents that read HTML and do not run scripts see a blank page.
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 lumeos.ch to your dashboard.
5 domains free, unlimited with a plan.
Lumeos exposes 4 of 8 interfaces agents look for: AI crawler access, Bot user-agent handling, llms.txt, Organisation markup.
Locked
All 8 interfaces and 26 checks for lumeos.ch
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
lumeos.ch 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 lumeos.ch scores 60/100. There is no embed code until it is earned.
Lumeos (lumeos.ch) scores 45 out of 100 for agent readiness, grade D, measured 3 days ago, on 27.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; Content is buried in boilerplate; No heading hierarchy; Pages are empty without JavaScript; 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 lumeos.ch 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 3 days ago, on 27.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.