Is apollopharmacy.in agent ready?
apollopharmacy.in is not yet agent ready: it scores 44/100 (grade D) on the w2agent rubric. Weakest areas: Agent Auth (0), Agent Protocols (27), Agent Discovery (29).
Changed since last check
+7 points since the previous check (2026-09-16)
Fixed: Appropriate Schema.org type, JSON-LD valid, Heading hierarchy
Changed: Answer-first content (fail → partial), Response time (partial → fail), Schema.org completeness (fail → partial)
Category scores
Technical
88
Agent Auth
0
Agent Discovery
29
Agent Protocols
27
Content Quality
56
Structured Data
77
Bot Accessibility
57
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- MCP discoveryNot found
- llms.txt validityPresent
Check results
Bot Accessibility
- ✓No error status codespass
- ✗Response timefail
- ✗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 elementspartial
- ✓Appropriate Schema.org typepass
- ✓JSON-LD validpass
- ✓Heading hierarchypass
- ~Schema.org JSON-LD presentpartial
- ~Schema.org completenesspartial
Content Quality
- ✓FAQ contentpass
- ~Answer-first contentpartial
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- ~llms.txt follows specpartial
- ✓llms.txt existspass
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- ✓llms.txt links resolvepass
Agent Protocols
- ✗Discoverable API endpointsfail
- ✗MCP endpointfail
- ✗Action schemasfail
- ✗/.well-known/ucpfail
- —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 URLspass
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ✓Security headerspass
Other
- ✓nextjs-metadata-apipass
- —ecommerce-gtin-validskip
- —ecommerce-product-schemaskip
- ~nextjs-static-generationpartial
- ✗nextjs-well-known-servedfail
- —ecommerce-checkout-accessibleskip
Score history
- 44/100 · rubric v3.0
- 37/100 · rubric v3.0
- 38/100 · rubric v3.0
- 36/100 · rubric v2.0
- 36/100 · rubric v2.0
- 35/100 · rubric v2.0
- 35/100 · rubric v2.0