Static pre-check · Wed, 19 Aug 2026 05:29:42 GMT
AI agents struggle discovering site content due to missing sitemap.xml, limiting crawlability despite decent accessibility and strong compliance documentation features.
Watch a real agent use your site →
A live Claude Code run against adentris.com, streamed step by step.
Measure this with real agents →
An audit: measured success rates from repeated real agent runs, with confidence intervals and downloadable evidence.
sitemap.xml not served (HTTP 404)
Fix: Publish /sitemap.xml listing your public pages, and reference it from robots.txt with a `Sitemap:` line.
no link to an API reference in the homepage HTML
Fix: If you have an API, link its reference from the homepage. If you don't, this check is safe to ignore.
https://adentris.com/
Shows the current scan score and grade for this domain, straight from the latest static pre-check.
[](https://www.vorza.dev/score/adentris.com)<a href="https://www.vorza.dev/score/adentris.com"><img src="https://www.vorza.dev/api/badge/adentris.com" alt="agent readiness score" /></a>5 docs link(s), e.g. /solutions/documentation-compliance
156 characters
'Adentris · AI for Healthcare Revenue Integrity & Compliance' (59 chars)
og:title and og:description present
all 6 agent crawlers may fetch /
HTTP 200, 1023 bytes
robots.txt has a Sitemap: line
site advertises no MCP endpoint — a registry listing is not expected
Accept: text/markdown → text/html
Fix: Optional but increasingly expected: honour `Accept: text/markdown` by serving a markdown rendering of the page, so agents skip HTML parsing entirely.
HTTP 200 for / (agent UA)
https://adentris.com/
8 valid block(s) (Organization, WebSite, SoftwareApplication)
HTTP 200, 4509 bytes
HTTP 200, 6337 bytes
5 sampled link(s) all resolve
has headings and markdown links
both User-Agents got HTTP 200
16261 characters of text in the served HTML
ratio 0.1902 (16261 chars of 85487)
0 redirect(s)
/docs not served (HTTP 404) — docs may live on another path or host
/agents.md not served (HTTP 404)
Fix: Publish /agents.md: what an agent may do here, which endpoints matter, auth requirements, and rate limits. It is the agent-facing counterpart to a README.
/docs → HTTP 404
Fix: Serve docs at the conventional /docs path, or redirect it to wherever they live. Agents try conventional paths first.
404 returns HTML, not a machine-readable body
Fix: Content-negotiate your errors: return a JSON body with a stable `code` (and a `next_action` where recovery exists) to clients that ask for JSON.
/openapi.json not served (HTTP 404)
Fix: If you have an HTTP API, publish its OpenAPI document at a predictable path (/openapi.json). It is the difference between an agent reading your contract and an agent guessing it. If you have no HTTP API, ignore this.
/.well-known/mcp.json not served (HTTP 404)
Fix: If you run an MCP server, advertise it at /.well-known/mcp.json so agents discover it without being told its URL.
/api → HTTP 404 (no API at the conventional root)
no MCP endpoint found to probe (none in the input URL and none advertised at /.well-known/mcp.json)
no listed MCP tools to inspect
no listed MCP tools to inspect
no MCP endpoint to probe
no parseable OpenAPI document
no parseable OpenAPI document
no parseable OpenAPI document
no parseable OpenAPI document
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.