Is dantri.com.vn agent ready?
dantri.com.vn is not yet agent ready: it scores 43/100 (grade D) on the w2agent rubric. Weakest areas: Agent Protocols (0), Agent Auth (13), Agent Discovery (33).
Changed since last check
No change in score since the previous check (2026-09-16)
Fixed: llms.txt exists
Regressed: Reachable as ChatGPT-User, Reachable as Perplexity-User
Changed: Token efficiency (HTML-to-text ratio) (partial → fail)
Files added: llms.txt
Category scores
Technical
88
Agent Auth
13
Agent Discovery
33
Agent Protocols
0
Content Quality
69
Structured Data
50
Bot Accessibility
62
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot found
- MCP discoveryNot found
- llms.txt validityPresent
Check results
Bot Accessibility
- ✓No error status codespass
- ~Response timepartial
- ✗XML sitemap existsfail
- ✓AI agent accesspass
- ?Edge treatment of agent user-agentstracked, not scorederror
- ✓robots.txt existspass
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ✓OpenGraph meta tagspass
- ✓Semantic HTML elementspass
- ✗Appropriate Schema.org typefail
- ✗JSON-LD validfail
- ✗Heading hierarchyfail
- ✓Schema.org JSON-LD presentpass
- ~Schema.org completenesspartial
Content Quality
- ✓FAQ contentpass
- ✓Answer-first contentpass
- ✓Content lengthpass
- ✗Token efficiency (HTML-to-text ratio)fail
- ✗Freshness signalsfail
- ✓Author attributionpass
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- ✓llms.txt follows specpass
- ✓llms.txt existspass
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- ✗llms.txt links resolvefail
Agent Protocols
- ✗Discoverable API endpointsfail
- ✗MCP endpointfail
- ✗Action schemasfail
- —/.well-known/ucpskip
- —Structured formsskip
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ?Reachable as Google-Agenterror
- ✗Reachable as ChatGPT-Userfail
- ✗Reachable as Perplexity-Userfail
Agent Auth
- —MCP authorization (401 challenge → protected resource metadata)skip
- ✗PKCE S256 supportfail
- ~Public API surfacepartial
- —Client ID Metadata Documents (bonus)skip
- ✗OpenAPI specificationfail
- ✗Agent/bot auth documentationfail
- ✗OAuth discovery chain (RFC 9728 → RFC 8414)fail
- ~Developer portalpartial
- ✗Scoped API permissionsfail
- ✗API catalog (RFC 9727)fail
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ✓Canonical URLspass
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ~Security headerspartial
Other
- —local-business-hours-jsonldskip
- ~local-business-nap-structuredpartial
- —local-business-booking-accessibleskip
Score history
- 43/100 · rubric v3.0
- 43/100 · rubric v3.0
- 42/100 · rubric v3.0
- 37/100 · rubric v2.0
- 37/100 · rubric v2.0
- 29/100 · rubric v2.0
- 42/100 · rubric v2.0
- 41/100 · rubric v2.0
- 46/100 · rubric v2.0