Agent-readiness report
No class of agent can use Madkings today: they cannot call it as a tool.
madkings.com, last scanned 2 days ago, on 28.09.2026
Agent classes working
0/3
Score history
±04 scans since 20.09.2026
0 of 3 agent classes work
Nothing tells an agent where the useful pages, feeds and policies are.
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.
BlockerCautious platforms will not act on the site without an explicit permission signal.
ImprovementWhen something breaks, an agent operator has no documented way to reach you.
ImprovementFree 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 madkings.com to your dashboard.
5 domains free, unlimited with a plan.
Madkings exposes 4 of 8 interfaces agents look for: AI crawler access, Bot user-agent handling, Server-rendered content, Organisation markup.
Locked
All 8 interfaces and 26 checks for madkings.com
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
Agents can read the site, but acting on it still breaks. Paste this line where you want the seal: it is drawn at runtime, so it upgrades itself when you improve and removes itself if a deploy closes the site to agents.
<script src="https://qomvia.com/badge.js" data-slug="madkings-com" async></script>There is no image URL and no static version. The seal exists only as markup we serve per request, which is what makes it worth displaying.
Madkings (madkings.com) scores 63 out of 100 for agent readiness, grade C, measured 2 days ago, on 28.09.2026. 0 of 3 agent classes we test can use the site, and 3 checks currently block agents outright.
The heaviest problems are: No llms.txt; No API or feed to read; No MCP endpoint to call; No stated policy for automated access; No machine-readable contact. 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 madkings.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.
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 2 days ago, on 28.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.