adentris.com

AI agents struggle discovering site content due to missing sitemap.xml, limiting crawlability despite decent accessibility and strong compliance documentation features.

19 pass · 7 warn · 1 fail · 14 n/a

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.

Discovery

18/22.2

Accessibility

32.4/33.3

Usability

22.2/44.4

Payments

n/a

Discovery 18/22.2

sitemap.xml exists and parsesdetailsFAIL
sitemap.xml not served (HTTP 404)
Fix: Publish /sitemap.xml listing your public pages, and reference it from robots.txt with a `Sitemap:` line.
API reference linked from the homepagedetailsWARN
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.
Canonical URL declareddetailsPASS
https://adentris.com/

Badge

Shows the current scan score and grade for this domain, straight from the latest static pre-check.

[![agent ready](https://www.vorza.dev/api/badge/adentris.com)](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>

Documentation linked from the homepage

details

PASS

5 docs link(s), e.g. /solutions/documentation-compliance

Homepage has a meta descriptiondetailsPASS

156 characters

Homepage has a descriptive titledetailsPASS

'Adentris · AI for Healthcare Revenue Integrity & Compliance' (59 chars)

Open Graph tags presentdetailsPASS

og:title and og:description present

robots.txt allows agent crawlersdetailsPASS

all 6 agent crawlers may fetch /

robots.txt existsdetailsPASS

HTTP 200, 1023 bytes

robots.txt points at the sitemapdetailsPASS

robots.txt has a Sitemap: line

Listed in the official MCP registrydetailsN/A

site advertises no MCP endpoint — a registry listing is not expected

Accessibility 32.4/33.3

Serves markdown when asked for itdetailsWARN
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.
Homepage responds to an agent requestdetailsPASS
HTTP 200 for / (agent UA)
Served over HTTPSdetailsPASS
https://adentris.com/
Structured data (JSON-LD) on the homepagedetailsPASS
8 valid block(s) (Organization, WebSite, SoftwareApplication)
llms-full.txt is publisheddetailsPASS
HTTP 200, 4509 bytes
llms.txt is publisheddetailsPASS
HTTP 200, 6337 bytes
Links in llms.txt resolvedetailsPASS
5 sampled link(s) all resolve
llms.txt is structured markdowndetailsPASS
has headings and markdown links
Same response for agents and browsersdetailsPASS
both User-Agents got HTTP 200
Homepage has readable text without JavaScriptdetailsPASS
16261 characters of text in the served HTML
Content-to-markup ratio is reasonabledetailsPASS
ratio 0.1902 (16261 chars of 85487)
No long redirect chain on the homepagedetailsPASS
0 redirect(s)
Docs are readable without JavaScriptdetailsN/A
/docs not served (HTTP 404) — docs may live on another path or host

Usability 22.2/44.4

agents.md is publisheddetailsWARN
/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.
A documentation endpoint respondsdetailsWARN
/docs → HTTP 404
Fix: Serve docs at the conventional /docs path, or redirect it to wherever they live. Agents try conventional paths first.
Errors are machine-readabledetailsWARN
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 document publisheddetailsWARN
/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 advertises an MCP serverdetailsWARN
/.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.
The /api root behaves predictablydetailsN/A
/api → HTTP 404 (no API at the conventional root)
MCP server completes the initialize handshakedetailsN/A
no MCP endpoint found to probe (none in the input URL and none advertised at /.well-known/mcp.json)
MCP tool parameters are typed and describeddetailsN/A
no listed MCP tools to inspect
Every MCP tool has a descriptiondetailsN/A
no listed MCP tools to inspect
MCP server lists toolsdetailsN/A
no MCP endpoint to probe
OpenAPI declares its auth schemedetailsN/A
no parseable OpenAPI document
OpenAPI operations are describeddetailsN/A
no parseable OpenAPI document
OpenAPI documents error responsesdetailsN/A
no parseable OpenAPI document
OpenAPI document is structurally validdetailsN/A
no parseable OpenAPI document

Payments not applicable — excluded from the score

Serves a 402 payment challengedetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Declares AP2 / ACP supportdetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Publishes x402 payment metadatadetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.