Is bitrix24.com agent ready?
bitrix24.com is partly agent ready: it scores 52/100 (grade C) on the w2agent rubric. Weakest areas: Agent Discovery (0), Bot Accessibility (20), Agent Protocols (39).
Changed since last check
−14 points since the previous check (2026-09-16)
Regressed: FAQ content, XML sitemap exists, llms.txt exists, robots.txt exists
Changed: Response time (partial → fail)
Files removed: robots.txt, sitemap.xml, llms.txt
Category scores
Technical
92
Agent Auth
69
Agent Discovery
0
Agent Protocols
39
Content Quality
60
Structured Data
80
Bot Accessibility
20
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryPresent
- MCP discoveryPresent
- llms.txt validityNot measured
Check results
Bot Accessibility
- ✓No error status codespass
- ✗Response timefail
- ✗XML sitemap existsfail
- ?AI agent accesserror
- ?Edge treatment of agent user-agentstracked, not scorederror
- ✗robots.txt existsfail
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ✓OpenGraph meta tagspass
- ✓Semantic HTML elementspass
- ✓Appropriate Schema.org typepass
- ✓JSON-LD validpass
- ✗Heading hierarchyfail
- ✓Schema.org JSON-LD presentpass
- ~Schema.org completenesspartial
Content Quality
- ✗FAQ contentfail
- ✓Answer-first contentpass
- ✓Content lengthpass
- ✗Token efficiency (HTML-to-text ratio)fail
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
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 endpointspass
- ✓MCP endpointpass
- ✗Action schemasfail
- —/.well-known/ucpskip
- ✗Structured formsfail
- —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 supportpass
- ✗Public API surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- —Agent/bot auth documentationskip
- ✓OAuth discovery chain (RFC 9728 → RFC 8414)pass
- —Developer portalskip
- —Scoped API permissionsskip
- —API catalog (RFC 9727)skip
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ✓Canonical URLspass
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ~Security headerspartial
Score history
- 52/100 · rubric v3.0
- 66/100 · rubric v3.0
- 65/100 · rubric v3.0
- 47/100 · rubric v2.0
- 47/100 · rubric v2.0
- 47/100 · rubric v2.0
- 47/100 · rubric v2.0