New · Self-serve audits are live — real Claude Code & Cursor runs against your MCP server, SDK, or CLI →
B82/100

Static pre-check · Fri, 07 Aug 2026 06:50:23 GMT

snowplow.io

AI agents can discover and access Snowplow easily, but face moderate friction navigating complex usability workflows and interactions.

23 pass · 6 warn · 0 fail · 13 n/a

Watch a real agent use your site →

A live Claude Code run against snowplow.io, 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
19.5/20
Accessibility
29.6/30
Usability
23.2/40
Payments
10/10

Discovery 19.5/20

  • Canonical URL declareddetailsWARN

    no <link rel="canonical">

    Fix: Add <link rel="canonical"> to the homepage so agents and crawlers converge on one URL for this page.

  • API reference linked from the homepagedetailsPASS

    2 API link(s), e.g. https://docs.snowplow.io/docs/api-reference/loaders-storage-targets/lake-loader/

  • Documentation linked from the homepagedetailsPASS

    5 docs link(s), e.g. /developer-hub

  • Homepage has a meta descriptiondetailsPASS

    109 characters

  • Homepage has a descriptive titledetailsPASS

    'Customer Context Layer | Snowplow' (33 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, 122 bytes

  • robots.txt points at the sitemapdetailsPASS

    robots.txt has a Sitemap: line

  • sitemap.xml exists and parsesdetailsPASS

    1192 URL(s) listed

  • Brand findable in agent searchdetailsN/A

    search-based checks are deferred — excluded from the score

  • Listed in an MCP registrydetailsN/A

    registry lookup not implemented in v1 — excluded from the score rather than guessed

Accessibility 29.6/30

  • llms-full.txt is publisheddetailsWARN

    /llms-full.txt not served

    Fix: Optional but cheap: publish /llms-full.txt with your docs inlined as one markdown file, so an agent can read everything in a single fetch.

  • Docs are readable without JavaScriptdetailsPASS

    2655 characters of text at /docs

  • Homepage responds to an agent requestdetailsPASS

    HTTP 200 for / (agent UA)

  • Served over HTTPSdetailsPASS

    https://snowplow.io/

  • Structured data (JSON-LD) on the homepagedetailsPASS

    2 valid block(s) (WebPage, WebPage)

  • llms.txt is publisheddetailsPASS

    HTTP 200, 17547 bytes

  • Links in llms.txt resolvedetailsPASS

    5 sampled link(s) all resolve

  • llms.txt is structured markdowndetailsPASS

    has headings and markdown links

  • Serves markdown when asked for itdetailsPASS

    Accept: text/markdown → text/markdown; charset=utf-8

  • Same response for agents and browsersdetailsPASS

    both User-Agents got HTTP 200

  • Homepage has readable text without JavaScriptdetailsPASS

    9587 characters of text in the served HTML

  • Content-to-markup ratio is reasonabledetailsPASS

    ratio 0.0742 (9587 chars of 129216)

  • No long redirect chain on the homepagedetailsPASS

    0 redirect(s)

Usability 23.2/40

  • agents.md is publisheddetailsWARN

    /agents.md not served (HTTP 404)

    Fix: Publish /agents.md: what an agent may do here, which endpoints matter, auth requirements, and rate limits. It is the agent-facing counterpart to a README.

  • Errors are machine-readabledetailsWARN

    404 returns HTML, not a machine-readable body

    Fix: Content-negotiate your errors: return a JSON body with a stable `code` (and a `next_action` where recovery exists) to clients that ask for JSON.

  • OpenAPI document publisheddetailsWARN

    /openapi.json not served (HTTP 404)

    Fix: If you have an HTTP API, publish its OpenAPI document at a predictable path (/openapi.json). It is the difference between an agent reading your contract and an agent guessing it. If you have no HTTP API, ignore this.

  • .well-known/mcp.json advertises an MCP serverdetailsWARN

    /.well-known/mcp.json not served (HTTP 404)

    Fix: If you run an MCP server, advertise it at /.well-known/mcp.json so agents discover it without being told its URL.

  • A documentation endpoint respondsdetailsPASS

    /docs → HTTP 200

  • The /api root behaves predictablydetailsN/A

    /api → HTTP 404 (no API at the conventional root)

  • 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 10/10

  • Declares AP2 / ACP supportdetailsPASS

    marker(s) found: ap2

  • 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.

  • 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.

agent readiness badge for snowplow.io
[![agent ready](/api/badge/snowplow.io)](/score/snowplow.io)
<a href="/score/snowplow.io"><img src="/api/badge/snowplow.io" alt="agent readiness score" /></a>