patagonia.com

Whether agents can crawl you, find you in the registries and searches they check, and trust what they find.

• ✗Sitemap present & freshrequired0/4

  No valid sitemap found: robots.txt listed 0 Sitemap URL(s), and GET /sitemap.xml returned HTTP 404

  fix → Publish /sitemap.xml, reference it from robots.txt, and include <lastmod> dates so agents can tell what's current. Freshest lastmod seen: none.

  Resolved the sitemap from robots.txt or /sitemap.xml, validated XML, and checked lastmod freshness

  spec ↗report issue
• ✗Brand search discoverabilityrequired0/4

  Neither search ("Patagonia", "Patagonia e commerce") cited patagonia.com. Cited instead: https://sportstextiles.com/News/173575, https://antigreenwashcharter.org/how-patagonias-progress-report-acts-like-a-green-claims-policy/, https://planetarypl.com/test/patagonia, https://outdoorindustry.org/ccmc-progress-report/patagonia-2024/, https://www.sinkproject.com/company/patagonia

  fix → Your domain doesn't surface when agents search "Patagonia". Strengthen brand pages, structured data, and third-party citations (docs portals, GitHub, directories).

  Ran clean brand-name web searches and checked whether your domain is cited in the results

  report issue
• —MCP registry listingsrecommendedna

  No MCP server detected for this product

  Queried the official MCP registry, Smithery, Glama, and PulseMCP for servers matching your domain

  spec ↗report issue

Whether your robots policy, bot protection, and agent guidance actively admit AI agents instead of blocking them.

• ✗robots.txt present & parseablerequired0/2

  GET /robots.txt returned HTTP 404

  fix → Serve a valid /robots.txt; without one, agent crawlers guess your policy.

  Fetched /robots.txt and validated it parses as a robots policy

  spec ↗report issue
• ✓AI crawler policyrequired5/5

  No robots.txt (HTTP 404) — none of the 12 AI crawler user-agents are blocked. Note: without a robots.txt, crawlers guess your policy.

  Evaluated robots.txt groups for the major AI agent user-agents (GPTBot, ClaudeBot, PerplexityBot, …)

  report issue
• ✗Content Signals directivesemerging0/2

  No robots.txt (HTTP 404), so no Content-Signal lines are declared

  fix → Declare Content Signals in robots.txt (e.g. `Content-Signal: search=yes, ai-train=no`) to express AI usage preferences machine-readably.

  Looked for Content-Signal lines in robots.txt

  spec ↗report issue
• !Agent user-agent paritybetarequirederror

  Browser UA received HTTP 404 — cannot evaluate parity (the site may be blocking our scanner)

  Compared responses served to browser and AI-agent user-agents (informational while in beta)

  report issue
• ✗agents.mdrecommended0/3

  No agents.md: https://patagonia.com/agents.md → HTTP 404, https://patagonia.com/AGENTS.md → HTTP 404

  fix → Add /agents.md: what agents may do on your site, key URLs, auth, rate limits, and who to contact.

  Fetched /agents.md and checked for substantive agent guidance

  spec ↗report issue

Whether your pages carry machine-readable identity: structured data, llms.txt, clear copy an agent can quote.

• !Homepage states what you arerequirederror

  Homepage returned HTTP 404 — no content to evaluate

  An LLM read your homepage as an agent would and rated how confidently it could say what you do

  report issue
• !OpenGraph / social metadatarecommendederror

  Homepage returned HTTP 404 (no content-type) — could not parse HTML meta tags

  Parsed homepage og:title / og:description / og:image and twitter:card meta tags

  spec ↗report issue
• ✗llms.txtrecommended0/4

  GET /llms.txt returned HTTP 404

  fix → Add /llms.txt: an H1 with your name, a one-line blockquote summary, and H2 sections of curated links to docs, pricing, and API.

  Fetched /llms.txt and validated it against the llmstxt.org shape (H1, summary, curated links)

  spec ↗report issue
• ✗llms-full.txtbonusrecommended0/2

  GET /llms-full.txt returned HTTP 404

  fix → Add /llms-full.txt with expanded inline docs content so agents can load everything in one fetch.

  Fetched /llms-full.txt and checked for substantial inline markdown content

  spec ↗report issue
• !JSON-LD structured datarequirederror

  Homepage returned HTTP 404 (content-type unknown) — no HTML to inspect

  Extracted and validated application/ld+json blocks on the homepage and pricing page

  spec ↗report issue
• ✗Markdown content negotiationrecommended0/3

  GET / with `Accept: text/markdown` returned HTTP 404 unknown; no .md twins found (1 probed)

  fix → Serve text/markdown when clients send `Accept: text/markdown` (or expose .md twins of key pages) — agents get far more signal per token.

  Requested key pages with Accept: text/markdown and probed .md twin URLs

  report issue

Whether the artifacts an agent needs to build on you — docs, API specs, SDKs, MCP servers — exist and are findable.

• ◐Developer resource discoverabilityrecommended1/3

  Search "Patagonia API documentation" cited no patagonia.com URL — only third-party content describes your API: https://patagoniahealth.com/hubfs/Certifications/PatientHealth-Data-API-Documentation-v1.1.pdf, https://patagoniahealth.com/hubfs/SmartOnFHIR-API-Documentation.pdf, https://www.openbankingtracker.com/provider/banco-patagonia-sa/apis, https://21302886.fs1.hubspotusercontent-na1.net/hubfs/21302886/Certifications/RWT-Test-Plan_Patagonia_2024_FinalSigned.pdf, https://21302886.fs1.hubspotusercontent-na1.net/hubfs/21302886/Certifications/Real-World-Testing-Results-Report_2023-Patagonia_Health.pdf

  fix → Create a crawlable /docs or developers.patagonia.com hub and link it from your homepage footer so search-grounded agents find your official API docs.

  Searched for your brand with developer-keyword suffixes and checked which official resources are cited

  report issue
• ✗OpenAPI spec discoverablerequired0/5

  No OpenAPI spec found: checked docs-page links and /openapi.json, /openapi.yaml, /swagger.json, /api/openapi.json, /docs/openapi.json, and api-subdomain locations

  fix → Publish your OpenAPI spec at /openapi.json and link it from docs — it's the single highest-leverage artifact for agent integration.

  Probed standard OpenAPI locations and docs links for a fetchable, parseable spec

  spec ↗report issue
• ✗Docs discoverablerequired0/4

  No docs found: probed 6 candidates (https://patagonia.com/docs, https://patagonia.com/documentation, https://patagonia.com/developers, https://patagonia.com/api, https://docs.patagonia.com/, https://developers.patagonia.com/)

  fix → Expose public docs at /docs or docs.patagonia.com and link them from your homepage nav.

  Followed homepage nav/footer links and probed /docs, /developers, docs.{domain}

  report issue
• ✗MCP server discoveryrequired0/5

  No MCP evidence found: probed /.well-known/mcp/server-card.json, /.well-known/mcp.json, /mcp.json and scanned llms.txt, agents.md, and docs for endpoints or install commands

  fix → Publish /.well-known/mcp/server-card.json describing your MCP endpoint so agents can autodiscover it. Evidence found: none.

  Probed /.well-known/mcp/server-card.json, mcp.json, and docs mentions for an MCP endpoint

  spec ↗report issue
• !npm SDKrecommendederror

  All 6 npm registry requests failed: @patagonia/sdk (Request budget exhausted), @patagonia/patagonia (Request budget exhausted), patagonia (Request budget exhausted), patagonia-sdk (Request budget exhausted), patagonia-api (Request budget exhausted), patagonia-js (Request budget exhausted)

  Searched the npm registry for an official, domain-verified SDK package

  report issue
• !PyPI SDKrecommendederror

  All 4 PyPI registry requests failed: patagonia (Request budget exhausted), patagonia-sdk (Request budget exhausted), patagoniaapi (Request budget exhausted), patagonia-python (Request budget exhausted)

  Searched PyPI for an official, domain-verified SDK package

  report issue

Whether your specs, docs, and tools are complete and descriptive enough for an agent to use them without guessing.

• —OpenAPI validity & qualityrecommendedna

  No OpenAPI spec found — nothing to lint

  Linted the spec: descriptions, operationIds, securitySchemes, servers

  report issue
• —Docs qualityrecommendedna

  No documentation found to evaluate

  An LLM rated your docs for clarity, completeness, runnable examples, and agent-friendliness

  report issue
• —Quickstart / getting startedrecommendedna

  No docs found — a quickstart is evaluated on the docs artifact

  Looked for a quickstart/getting-started guide containing code blocks

  report issue
• —MCP tool qualityrecommendedna

  No MCP endpoint known — tool lint requires a tools/list

  Linted listed tools for descriptions, typed input schemas, and naming

  report issue

Response hygiene, TLS and redirect discipline, and security contact channels agents depend on at runtime.

• ◐TLS & redirect hygienerequired1/2

  http://patagonia.com/ reaches https but ends in HTTP 404: http://patagonia.com/ → https://patagonia.com/ → https://www.patagonia.com/

  fix → Redirect http→https in one hop and keep redirect chains ≤2; each hop costs agent latency and some clients give up.

  Checked http→https redirect behavior, chain length, and TLS health

  report issue
• !Response speed & weightrequirederror

  Homepage returned HTTP 404 — cannot assess response hygiene

  Measured homepage TTFB, payload size, and compression

  report issue
• ✗security.txtrecommended0/1

  https://patagonia.com/.well-known/security.txt returned HTTP 404

  fix → Publish RFC 9116 /.well-known/security.txt with a Contact and a future Expires.

  Fetched /.well-known/security.txt and validated Contact + Expires

  spec ↗report issue

Whether agents can discover your auth model machine-readably (OAuth metadata) and follow documented steps to credentials.

• ✗OAuth authorization server metadatarecommended0/3

  Neither /.well-known/oauth-authorization-server nor /.well-known/openid-configuration resolved (HTTP 404 / HTTP 404)

  fix → Serve RFC 8414 metadata at /.well-known/oauth-authorization-server with PKCE (S256) and a registration_endpoint so agents can self-onboard.

  Fetched /.well-known/oauth-authorization-server (and openid-configuration fallback)

  spec ↗report issue
• ✗OAuth protected resource metadatarecommended0/2

  No RFC 9728 metadata: https://patagonia.com/.well-known/oauth-protected-resource → HTTP 404

  fix → Serve RFC 9728 metadata at /.well-known/oauth-protected-resource naming your authorization servers so agents can discover how to authenticate.

  Fetched /.well-known/oauth-protected-resource

  spec ↗report issue
• ✗Auth documentationrecommended0/2

  No /auth.md and no docs page to search for authentication documentation

  fix → Document auth end-to-end (key creation → header format → example call), or ship /auth.md.

  Looked for /auth.md or an authentication docs page with code examples

  report issue

Whether pricing is discoverable and machine-readable, and whether you support agent payment protocols.

• ✗Pricing discoverablerequired0/5

  No pricing page found: no homepage link matching pricing/plans/billing, and probes of /pricing and /plans returned no HTML page.

  fix → Expose a crawlable /pricing page with literal plan prices and link it from your homepage nav.

  Followed nav/footer links and probed /pricing for a page with legible price signals

  report issue
• —Machine-readable pricingrecommendedna

  No pricing page found to evaluate

  Looked for Offer JSON-LD, then had an LLM attempt structured extraction of your plans

  spec ↗report issue
• ✗x402 payment supportbonusrecommended0/2

  /.well-known/x402 returned HTTP 404. No x402 support detected (bonus check — absence costs nothing).

  fix → Support x402: serve payment requirements at /.well-known/x402, or answer unauthenticated API calls with HTTP 402 plus an x402 payment-requirements payload (x402Version, accepts[]).

  Probed /.well-known/x402 and API endpoints for HTTP 402 payment-required envelopes

  spec ↗report issue
• ✗AP2 readinessemerging0/1

  No AP2 hints found — scanned no fetched artifacts (none available); /.well-known/ap2 returned HTTP 404.

  fix → Adopt AP2 to accept delegated agent payments — see https://ap2-protocol.org.

  Scanned fetched artifacts and well-known paths for AP2 hints

  spec ↗report issue
• ✗Agentic Commerce Protocolemerging0/1

  No Agentic Commerce Protocol hints found — scanned no fetched artifacts (none available); /.well-known/acp returned HTTP 404.

  fix → Adopt the Agentic Commerce Protocol so agent checkouts can complete against your store — see https://developers.openai.com/commerce.

  Scanned docs and specs for agentic checkout endpoints

  spec ↗report issue
• ✗Other agent payment protocolsbonusemerging0/1

  No UCP/MPP hints found — scanned no fetched artifacts (none available).

  fix → Track emerging agent payment protocols (UCP, MPP) and adopt the ones your buyers' agents use.

  Scanned fetched artifacts for UCP/MPP protocol hints

  report issue

Whether an end user's agent can operate on their behalf: working MCP tools, published skills, agent configs.

• —Agent skill publishedbonusemergingna

  Requires the analysis phase — not yet evaluated

  Checked /skill.md, /.well-known/skills/, and skills.sh for published agent skills

  report issue
• —MCP handshake & tools listrequiredna

  No MCP endpoint known — nothing to handshake with

  Performed a streamable-HTTP initialize + tools/list against the MCP endpoint

  spec ↗report issue
• —Agent configs in public repobonusemergingna

  Requires the analysis phase — not yet evaluated

  Checked your public GitHub org's main repos for AGENTS.md / .claude / .cursor configs

  report issue

Whether the site itself is legible to non-rendering and browser agents: semantic HTML, no JS walls, accessibility.

• ✗NLWeb endpointemerging0/1

  No NLWeb endpoint detected: /.well-known/nlweb.json returned HTTP 404 (no content-type); GET /ask?query=hello returned HTTP 404 (no content-type)

  fix → Consider exposing an NLWeb /ask endpoint (and /.well-known/nlweb.json) for conversational access to your content.

  Probed /.well-known/nlweb.json and the /ask endpoint

  spec ↗report issue
• !Semantic HTML structurerequirederror

  Homepage returned HTTP 404 (content-type unknown) — no HTML to inspect

  Scored landmark elements, heading hierarchy, and text-to-markup ratio on the homepage

  report issue
• !Content readable without JavaScriptrequirederror

  Homepage returned HTTP 404 (content-type unknown) — no HTML to inspect

  Measured visible text in the raw, unrendered homepage HTML

  report issue
• !Accessibility basicsrequirederror

  Homepage did not parse as HTML (HTTP 404, content-type "")

  Static checks: lang attribute, title, alt coverage, labeled inputs, landmarks

  report issue
• ✗WebMCPemerging0/1

  No WebMCP evidence on homepage: no application/webmcp script and no navigator.modelContext reference

  fix → Consider WebMCP to expose page actions as tools to browser agents.

  Looked for WebMCP script declarations on the homepage

  spec ↗report issue