Is ebird.org agent ready?
ebird.org is not yet agent ready: it scores 27/100 (grade F) on the w2agent rubric. Weakest areas: Agent Discovery (0), Agent Auth (10), Structured Data (21), Agent Protocols (30), Content Quality (37), Bot Accessibility (39).
Changed since last check
+4 points since the previous check (2026-09-16)
Fixed: Response time, Content length, Token efficiency (HTML-to-text ratio)
Regressed: Security headers, Lists and tables for structured info
Changed: Public API surface (fail → partial), OpenGraph meta tags (fail → partial)
Category scores
Technical
67
Agent Auth
10
Agent Discovery
0
Agent Protocols
30
Content Quality
37
Structured Data
21
Bot Accessibility
39
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot found
- MCP discoveryNot found
- llms.txt validityNot measured
Check results
Bot Accessibility
- ✓No error status codespass
- ✓Response timepass
- ✗XML sitemap existsfail
- ✗AI agent accessfail
- ✓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 validskip
- ✓Heading hierarchypass
- ✗Schema.org JSON-LD presentfail
- ✗Schema.org completenessfail
Content Quality
- ✗FAQ contentfail
- ✗Answer-first contentfail
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓Citation readinesspass
- ✗Lists and tables for structured infofail
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 surfacepartial
- —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 URLsfail
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ✗Security headersfail
Score history
- 27/100 · rubric v3.0
- 23/100 · rubric v3.0
- 24/100 · rubric v3.0