Is artsy.net agent ready?
artsy.net is not yet agent ready: it scores 38/100 (grade D) on the w2agent rubric. Weakest areas: Content Quality (24), Structured Data (27), Agent Protocols (30), Agent Auth (31), Agent Discovery (35).
Changed since last check
−3 points since the previous check (2026-09-16)
Regressed: FAQ content, Content negotiation (Markdown)
Changed: Heading hierarchy (partial → fail)
Category scores
Technical
81
Agent Auth
31
Agent Discovery
35
Agent Protocols
30
Content Quality
24
Structured Data
27
Bot Accessibility
54
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot measured
- MCP discoveryNot found
- llms.txt validityPresent
Check results
Bot Accessibility
- ~No error status codespartial
- ✓Response timepass
- ✗XML sitemap existsfail
- ✓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 typepartial
- ✓JSON-LD validpass
- ✗Heading hierarchyfail
- ~Schema.org JSON-LD presentpartial
- ~Schema.org completenesspartial
Content Quality
- ✗FAQ contentfail
- ✗Answer-first contentfail
- ~Content lengthpartial
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓Citation readinesspass
- ~Lists and tables for structured infopartial
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 resolvepartial
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 supportfail
- ✗Public API surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- ✗Agent/bot auth documentationfail
- —OAuth discovery chain (RFC 9728 → RFC 8414)skip
- ✓Developer portalpass
- ~Scoped API permissionspartial
- —API catalog (RFC 9727)skip
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ~Canonical URLspartial
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ✓Security headerspass
Score history
- 38/100 · rubric v3.0
- 41/100 · rubric v3.0
- 39/100 · rubric v3.0
- 37/100 · rubric v2.0
- 37/100 · rubric v2.0
- 32/100 · rubric v2.0
- 31/100 · rubric v2.0