Is caliente.mx agent ready?
caliente.mx is not yet agent ready: it scores 33/100 (grade D) on the w2agent rubric. Weakest areas: Agent Auth (0), Agent Discovery (0), Structured Data (18), Agent Protocols (25), Content Quality (42).
Changed since last check
+1 points since the previous check (2026-09-16)
Category scores
Technical
64
Agent Auth
0
Agent Discovery
0
Agent Protocols
25
Content Quality
42
Structured Data
18
Bot Accessibility
94
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- MCP discoveryNot found
- llms.txt validityNot measured
Check results
Bot Accessibility
- ✓No error status codespass
- ✓Response timepass
- ✓XML sitemap existspass
- ✓AI agent accesspass
- ✓Edge treatment of agent user-agentstracked, not scoredpass
- ✓robots.txt existspass
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ~OpenGraph meta tagspartial
- ~Semantic HTML elementspartial
- ✗Appropriate Schema.org typefail
- ✗JSON-LD validfail
- ~Heading hierarchypartial
- ~Schema.org JSON-LD presentpartial
- ✗Schema.org completenessfail
Content Quality
- ✓FAQ contentpass
- ~Answer-first contentpartial
- ~Content lengthpartial
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ~Citation readinesspartial
- ~Lists and tables for structured infopartial
Agent Discovery
- —llms.txt follows specskip
- ✗llms.txt existsfail
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- —llms.txt links resolveskip
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-Agentpass
- ✓Reachable as ChatGPT-Userpass
- ✓Reachable as Perplexity-Userpass
Agent Auth
- —MCP authorization (401 challenge → protected resource metadata)skip
- —PKCE S256 supportskip
- ✗Public API surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- —Agent/bot auth documentationskip
- —OAuth discovery chain (RFC 9728 → RFC 8414)skip
- —Developer portalskip
- —Scoped API permissionsskip
- —API catalog (RFC 9727)skip
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ~Canonical URLspartial
- ✗Mobile viewportfail
- ~Content accessible without JSpartial
- ~Security headerspartial
Other
- ✓wp-page-builder-souppass
- ✗wp-rest-api-accessiblefail
- ✓wp-security-blocking-botspass
- ✓wp-robots-default-blockingpass
- —local-business-hours-jsonldskip
- —local-business-nap-structuredskip
- —local-business-booking-accessibleskip
Score history
- 33/100 · rubric v3.0
- 32/100 · rubric v3.0
- 29/100 · rubric v3.0
- 53/100 · rubric v2.0
- 53/100 · rubric v2.0
- 47/100 · rubric v2.0
- 55/100 · rubric v2.0
- 55/100 · rubric v2.0
- 55/100 · rubric v2.0