Is pinecone.io agent ready?

pinecone.io is partly agent ready: it scores 60/100 (grade C) on the w2agent rubric.

60/ 100
Grade: C

Last checked

Scored Sep 16, 2026 · Rubric v3.0

Changed since last check

+5 points since the previous check (2026-09-15)

Fixed: Agent/bot auth documentation

Changed: Response time (fail → partial), Scoped API permissions (fail → partial)

Category scores

Category breakdown not recorded for this audit.

Agent protocol panel

  • A2A agent cardPresent
  • OAuth discoveryNot found
  • MCP discoveryPresent
  • llms.txt validityPresent

Check results

Bot Accessibility

  • ✓No error status codespass
  • ~Response timepartial
  • ✓XML sitemap existspass
  • ✓AI agent accesspass
  • ✓Edge treatment of agent user-agentstracked, not scoredpass
  • ✓robots.txt existspass
  • ✓Content negotiation (Markdown)pass
  • —Declared AI usage preferencestracked, not scoredskip

Structured Data

  • ✓OpenGraph meta tagspass
  • ✓Semantic HTML elementspass
  • ✗Appropriate Schema.org typefail
  • ✗JSON-LD validfail
  • ~Heading hierarchypartial
  • ~Schema.org JSON-LD presentpartial
  • ✗Schema.org completenessfail

Content Quality

  • ✓FAQ contentpass
  • ✗Answer-first contentfail
  • ✓Content lengthpass
  • ✓Token efficiency (HTML-to-text ratio)pass
  • ✗Freshness signalsfail
  • ✗Author attributionfail
  • ✓Citation readinesspass
  • ~Lists and tables for structured infopartial

Agent Discovery

  • ✓llms.txt follows specpass
  • ✓llms.txt existspass
  • —MCP server cardtracked, not scoredskip
  • ✗Markdown alternate linksfail
  • ~/.well-known/agent-card.jsonpartial
  • ~llms.txt links resolvepartial

Agent Protocols

  • ✗Discoverable API endpointsfail
  • ✓MCP endpointpass
  • ✗Action schemasfail
  • —/.well-known/ucpskip
  • ✗Structured formsfail
  • —WebMCP imperative APItracked, not scoredskip
  • —WebMCP declarative APItracked, not scoredskip
  • ✓Reachable as Google-Agentpass
  • ✓Reachable as ChatGPT-Userpass
  • ✓Reachable as Perplexity-Userpass

Agent Auth

  • —MCP authorization (401 challenge → protected resource metadata)skip
  • ✗PKCE S256 supportfail
  • ✓Public API surfacepass
  • —Client ID Metadata Documents (bonus)skip
  • ✗OpenAPI specificationfail
  • ✓Agent/bot auth documentationpass
  • ✗OAuth discovery chain (RFC 9728 → RFC 8414)fail
  • ✓Developer portalpass
  • ~Scoped API permissionspartial
  • ✓API catalog (RFC 9727)pass
  • —Agent operator signing directorytracked, not scoredskip

Technical

  • ✓HTTPSpass
  • ✓UTF-8 charsetpass
  • ✓Canonical URLspass
  • ✓Mobile viewportpass
  • ✓Content accessible without JSpass
  • ~Security headerspartial

Other

  • ✓nextjs-metadata-apipass
  • ✓nextjs-static-generationpass
  • ✓nextjs-well-known-servedpass

Score history

  • 60/100 · rubric v3.0
  • 55/100 · rubric v3.0
  • 52/100 · rubric v2.0
  • 52/100 · rubric v2.0
  • 49/100 · rubric v2.0
  • 48/100 · rubric v2.0
  • 42/100 · rubric v2.0
  • 44/100 · rubric v2.0
  • 43/100 · rubric v2.0
  • 43/100 · rubric v2.0
  • 47/100 · rubric v2.0

Related websites

Is your own site agent ready?

Check your own site →

Re-audit pinecone.io