Is thenounproject.com agent ready?
thenounproject.com is partly agent ready: it scores 51/100 (grade C) on the w2agent rubric.
Changed since last check
−2 points since the previous check (2026-09-15)
Regressed: Reachable as ChatGPT-User
Category scores
Category breakdown not recorded for this audit.
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 timefail
- ✓XML sitemap existspass
- ✓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 tagspartial
- ~Semantic HTML elementspartial
- ✓Appropriate Schema.org typepass
- ✓JSON-LD validpass
- ~Heading hierarchypartial
- ~Schema.org JSON-LD presentpartial
- ~Schema.org completenesspartial
Content Quality
- ✓FAQ contentpass
- ✓Answer-first contentpass
- ✓Content lengthpass
- ~Token efficiency (HTML-to-text ratio)partial
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓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 resolvepass
Agent Protocols
- ✓Discoverable API endpointspass
- ✗MCP endpointfail
- ✓Action schemaspass
- —/.well-known/ucpskip
- ✓Structured formspass
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ?Reachable as Google-Agenterror
- ✗Reachable as ChatGPT-Userfail
- ?Reachable as Perplexity-Usererror
Agent Auth
- —MCP authorization (401 challenge → protected resource metadata)skip
- —PKCE S256 supportskip
- ✓Public API surfacepass
- —Client ID Metadata Documents (bonus)skip
- ✗OpenAPI specificationfail
- —Agent/bot auth documentationskip
- ✗OAuth discovery chain (RFC 9728 → RFC 8414)fail
- ✗Developer portalfail
- —Scoped API permissionsskip
- ✗API catalog (RFC 9727)fail
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ~Canonical URLspartial
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ✗Security headersfail
Other
- ✗nextjs-metadata-apifail
- ~nextjs-static-generationpartial
- ✗nextjs-well-known-servedfail
Score history
- 51/100 · rubric v3.0
- 53/100 · rubric v3.0
- 50/100 · rubric v2.0
- 50/100 · rubric v2.0
- 51/100 · rubric v2.0
- 50/100 · rubric v2.0