Is alchemy.com agent ready?
alchemy.com is largely agent ready: it scores 62/100 (grade B) on the w2agent rubric. Weakest areas: Agent Protocols (20), Agent Discovery (41), Agent Auth (44).
Changed since last check
−7 points since the previous check (2026-09-16)
Regressed: MCP endpoint, Response time, Reachable as ChatGPT-User, nextjs-static-generation
Changed: Content negotiation (Markdown) (partial → fail)
Category scores
Technical
91
Agent Auth
44
Agent Discovery
41
Agent Protocols
20
Content Quality
76
Structured Data
89
Bot Accessibility
79
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 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 tagspass
- ✓Semantic HTML elementspass
- ✓Appropriate Schema.org typepass
- ✓JSON-LD validpass
- ✓Heading hierarchypass
- ✓Schema.org JSON-LD presentpass
- ~Schema.org completenesspartial
Content Quality
- ✓FAQ contentpass
- ✓Answer-first contentpass
- ✓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 specpass
- ✓llms.txt existspass
- —MCP server cardtracked, not scoredskip
- ✓Markdown alternate linkspass
- ✗/.well-known/agent-card.jsonfail
- ✓llms.txt links resolvepass
Agent Protocols
- ✗Discoverable API endpointsfail
- ✗MCP endpointfail
- ✗Action schemasfail
- —/.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 supportfail
- ✗Public API surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- ✓Agent/bot auth documentationpass
- —OAuth discovery chain (RFC 9728 → RFC 8414)skip
- ✓Developer portalpass
- ✗Scoped API permissionsfail
- —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
- ~nextjs-static-generationpartial
- ✗nextjs-well-known-servedfail
Score history
- 62/100 · rubric v3.0
- 69/100 · rubric v3.0
- 69/100 · rubric v3.0
- 63/100 · rubric v2.0
- 63/100 · rubric v2.0
- 62/100 · rubric v2.0
- 61/100 · rubric v2.0
- 58/100 · rubric v2.0
- 58/100 · rubric v2.0
- 57/100 · rubric v2.0
- 58/100 · rubric v2.0
- 58/100 · rubric v2.0
- 58/100 · rubric v2.0