AgentsReady
Verified deep dive · Comms & data

Pinecone

Run the agent liveReport a change
5 minTime to key
NoNo-human path
1Human gates
8/10Onboarding score
Email verification

Fastest path to a key

  1. Email verification
    Sign up at app.pinecone.io (email/Google/GitHub/Microsoft), verify email
  2. Starter (free) org + default project auto-created
  3. Agent path: `brew install pinecone-io/tap/pinecone` then `pc auth login` (browser URL, auto-targets org/project)
  4. `pc api-key create` mints a project API key (or Console > API Keys > Create)
  5. Configure local MCP with PINECONE_API_KEY
  6. Working API key

Biggest gap

Main MCP is local npx with a raw API key; no remote OAuth MCP, so web agents (Claude.ai/ChatGPT) cannot connect without a pasted key.

Worth copying

Published AGENTS-PYTHON.md / AGENTS-JAVASCRIPT.md at the docs root plus a 'Connect to Pinecone' embeddable flow that hands a user's API key to a third-party app.

Sources (10) · checked 2026-10-11
84Readiness score / 100
L4 Agent-nativeBeats 96% of 1,846 companies
Access20/20
Context17/20
Interfaces32/32
Onboarding8/19
Trust7/9
llms.txt · root
MCP · https://docs.pinecone.io/mcp
OpenAPI · https://www.pinecone.io/openapi.json

Biggest gains

  1. +6 Agents can self-register OAuth clients. Support dynamic client registration (RFC 7591) or client ID metadata documents so MCP clients connect in one click.
  2. +5 OAuth discovery metadata. Publish RFC 8414 authorization-server and RFC 9728 protected-resource metadata.
  3. +3 llms-full.txt exists. Publish /llms-full.txt with the whole docs corpus in one file.
All 20 checks
  • PASSAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • PASSContent is server-rendered4
  • PASSllms.txt exists8
  • FAILllms-full.txt exists3
  • PASSDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • PASSPublic developer docs4
  • PASSMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • PASSSDKs and a CLI4
  • FAILOAuth discovery metadata5
  • FAILAgents can self-register OAuth clients6
  • PASSSelf-serve API keys5
  • PASSFree tier or test mode3
  • PASSAgent manifests4
  • FAILsecurity.txt2
  • PASSPublic status page3

Your fix pack: 5 changes, up to +16 points

Each change is ready to paste, filled in for pinecone.io, with a command to check it worked. Or hand the whole list to your coding agent.

Without client self-registration, every new agent needs a human to create an OAuth app before it can connect. This is the biggest one-click blocker we see.

Where: Your authorization server
Support one of:
1. Client ID metadata documents (CIMD, preferred by the current MCP auth spec): accept a client_id that is an
   https URL, fetch its JSON metadata, and validate redirect_uris against it.
2. Dynamic client registration (RFC 7591): POST /oauth/register returns a client_id for any MCP client.

Don't want to build it? WorkOS AuthKit, Stytch Connected Apps, Clerk and Auth0 all ship MCP-ready OAuth with DCR/CIMD.
Require PKCE (S256), short-lived tokens, and show the user a consent screen with the scopes.

Add the badge to your README

AgentsReady badge for pinecone.io
[![AgentsReady](https://agentsready.dev/badge/pinecone.io)](https://agentsready.dev/c/pinecone.io)