Static pre-check · Fri, 07 Aug 2026 06:49:39 GMT
wandb.ai
AI agents struggle significantly because documentation requires JavaScript to render and lacks OpenAPI specifications for programmatic integration.
Watch a real agent use your site →
A live Claude Code run against wandb.ai, streamed step by step.
Test this with real agents →
An audit: measured success rates from repeated real agent runs, with confidence intervals and downloadable evidence.
Discovery 22.2/22.2
Canonical URL declareddetailsPASS
httpss://wandb.ai/site
Homepage has a meta descriptiondetailsPASS
54 characters
Homepage has a descriptive titledetailsPASS
'Weights & Biases' (16 chars)
Open Graph tags presentdetailsPASS
og:title and og:description present
robots.txt allows agent crawlersdetailsPASS
all 6 agent crawlers may fetch /
robots.txt existsdetailsPASS
HTTP 200, 166 bytes
robots.txt points at the sitemapdetailsPASS
robots.txt has a Sitemap: line
sitemap.xml exists and parsesdetailsPASS
12321 URL(s) listed
API reference linked from the homepagedetailsN/A
no homepage links to inspect
Brand findable in agent searchdetailsN/A
search-based checks are deferred — excluded from the score
Documentation linked from the homepagedetailsN/A
no homepage links to inspect (see the accessibility checks — the homepage produced no parseable navigation)
Listed in an MCP registrydetailsN/A
registry lookup not implemented in v1 — excluded from the score rather than guessed
Accessibility 19.1/33.3
Docs are readable without JavaScriptdetailsFAIL
/docs returns only 0 characters of readable text
Fix: Server-render your documentation. Docs behind a client-side renderer are invisible to every agent that reads them, which is the whole audience for docs.
llms.txt is structured markdowndetailsFAIL
/llms.txt returns HTML, not markdown
Fix: Serve /llms.txt as text/plain or text/markdown. An HTML error page at this path is worse than a 404: it looks like content.
Homepage has readable text without JavaScriptdetailsFAIL
only 0 characters of readable text in the served HTML
Fix: Server-render the homepage's core content (SSR, static export, or prerendering). A client-rendered shell is empty to every agent.
Structured data (JSON-LD) on the homepagedetailsWARN
no JSON-LD blocks on the homepage
Fix: Add a JSON-LD block (schema.org Organization or SoftwareApplication) so agents get your name, description and links as data rather than prose.
Links in llms.txt resolvedetailsWARN
llms.txt contains no resolvable links
Fix: Add markdown links to your actual docs pages — a description with no links leaves the agent where it started.
Serves markdown when asked for itdetailsWARN
Accept: text/markdown → text/html; charset=UTF-8
Fix: Optional but increasingly expected: honour `Accept: text/markdown` by serving a markdown rendering of the page, so agents skip HTML parsing entirely.
Content-to-markup ratio is reasonabledetailsWARN
ratio 0.0 — 0 readable chars in 3441 bytes of HTML
Fix: Most of what you serve is markup and inline script rather than content. Reduce inline payloads or server-render more text so the signal-to-noise ratio favours readers.
Homepage responds to an agent requestdetailsPASS
HTTP 200 for / (agent UA)
Served over HTTPSdetailsPASS
https://wandb.ai/
llms-full.txt is publisheddetailsPASS
HTTP 200, 3964 bytes
llms.txt is publisheddetailsPASS
HTTP 200, 3934 bytes
Same response for agents and browsersdetailsPASS
both User-Agents got HTTP 200
No long redirect chain on the homepagedetailsPASS
1 redirect(s)
Usability 15.9/44.4
OpenAPI document publisheddetailsFAIL
/openapi.json is served but is not valid JSON
Fix: Serve a parseable OpenAPI document at /openapi.json. What is there now cannot be read by any tooling.
.well-known/mcp.json advertises an MCP serverdetailsFAIL
/.well-known/mcp.json is served but is not valid JSON
Fix: Fix the JSON at /.well-known/mcp.json — as served it cannot be parsed, so the advertisement does nothing.
agents.md is publisheddetailsWARN
/agents.md returns HTML
Fix: Serve /agents.md as markdown (text/markdown or text/plain). An HTML page here is probably your SPA catch-all route.
The /api root behaves predictablydetailsWARN
/api → HTTP 200 text/html; charset=utf-8
Fix: Serve JSON from API paths, with an accurate content-type.
Errors are machine-readabledetailsWARN
a nonexistent path returned HTTP 200, not 404
Fix: Return 404 for paths that do not exist. A 200 on a missing page makes an agent believe it found something.
A documentation endpoint respondsdetailsPASS
/docs → HTTP 200
MCP server completes the initialize handshakedetailsN/A
no MCP endpoint found to probe (none in the input URL and none advertised at /.well-known/mcp.json)
MCP tool parameters are typed and describeddetailsN/A
no listed MCP tools to inspect
Every MCP tool has a descriptiondetailsN/A
no listed MCP tools to inspect
MCP server lists toolsdetailsN/A
no MCP endpoint to probe
OpenAPI declares its auth schemedetailsN/A
no parseable OpenAPI document
OpenAPI operations are describeddetailsN/A
no parseable OpenAPI document
OpenAPI documents error responsesdetailsN/A
no parseable OpenAPI document
OpenAPI document is structurally validdetailsN/A
no parseable OpenAPI document
Payments not applicable — excluded from the score
Serves a 402 payment challengedetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Declares AP2 / ACP supportdetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Publishes x402 payment metadatadetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Badge
Shows the current scan score and grade for this domain, straight from the latest static pre-check.
[](/score/wandb.ai)<a href="/score/wandb.ai"><img src="/api/badge/wandb.ai" alt="agent readiness score" /></a>