Static pre-check · Fri, 07 Aug 2026 06:49:49 GMT
pinecone.io
AI agents can effectively navigate Pinecone's vector database site, but face issues resolving links defined in llms.txt.
Watch a real agent use your site →
A live Claude Code run against pinecone.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 20.6/22.2
API reference linked from the homepagedetailsWARN
no link to an API reference in the homepage HTML
Fix: If you have an API, link its reference from the homepage. If you don't, this check is safe to ignore.
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.
Documentation linked from the homepagedetailsPASS
3 docs link(s), e.g. http://docs.pinecone.io/integrations/claude-code
Homepage has a meta descriptiondetailsPASS
138 characters
Homepage has a descriptive titledetailsPASS
'The vector database to build knowledgeable AI | Pinecone' (56 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, 400 bytes
robots.txt points at the sitemapdetailsPASS
robots.txt has a Sitemap: line
sitemap.xml exists and parsesdetailsPASS
607 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.1/33.3
Links in llms.txt resolvedetailsFAIL
2 of 5 sampled links broken: https://www.pinecone.io/mcp/ → timeout after 8s, https://docs.pinecone.io/mcp → timeout after 8s
Fix: Fix the dead links in /llms.txt. Pointing an agent at a 404 is worse than not pointing it anywhere.
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.
Content-to-markup ratio is reasonabledetailsWARN
ratio 0.0196 — 5089 readable chars in 259066 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.
Docs are readable without JavaScriptdetailsPASS
2713 characters of text at /docs
Homepage responds to an agent requestdetailsPASS
HTTP 200 for / (agent UA)
Served over HTTPSdetailsPASS
https://www.pinecone.io/
Structured data (JSON-LD) on the homepagedetailsPASS
1 valid block(s)
llms.txt is publisheddetailsPASS
HTTP 200, 29911 bytes
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
5089 characters of text in the served HTML
No long redirect chain on the homepagedetailsPASS
1 redirect(s)
Usability 39.2/44.4
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.
.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.
agents.md is publisheddetailsPASS
HTTP 200, 1483 bytes
A documentation endpoint respondsdetailsPASS
/docs → HTTP 200
OpenAPI declares its auth schemedetailsPASS
2 scheme(s): ApiKeyAuth, BearerAuth
OpenAPI operations are describeddetailsPASS
72/72 operations described (100%)
OpenAPI document publisheddetailsPASS
HTTP 200, 532558 bytes of JSON
OpenAPI documents error responsesdetailsPASS
266 error response(s) with a schema
OpenAPI document is structurally validdetailsPASS
OpenAPI 3.0.3, 47 path(s)
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
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/pinecone.io)<a href="/score/pinecone.io"><img src="/api/badge/pinecone.io" alt="agent readiness score" /></a>