pinecone

Manage vector indexes, upserts, and hybrid queries on the Pinecone vector database.

13.0k|930|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/Orchestra-Research/AI-research-SKILLs --skill pinecone-orchestra-research
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pinecone
Source: https://github.com/Orchestra-Research/AI-research-SKILLs/tree/main/15-rag/pinecone
Command: npx skills add https://github.com/Orchestra-Research/AI-research-SKILLs --skill pinecone-orchestra-research

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pinecone-client, and includes references (resource) components.

What problem does it solve? Building production RAG or semantic search requires a vector database that scales without infrastructure management, and setting up indexes, namespaces, metadata filtering, and hybrid search correctly is error-prone without guidance. ## Core Features & Use Cases - Index Management: Create serverless or pod-based indexes, list, describe, and delete indexes with the pinecone-client SDK. - Vector Operations: Batch upsert vectors with metadata, query with top-k similarity, and delete by ID, filter, or namespace. - Hybrid Search & Filtering: Combine dense and sparse vectors with alpha weighting, apply metadata filters, and isolate tenants via namespaces. - Use Case: Build a production RAG application where document embeddings are upserted into a serverless index, queried with metadata filters per user namespace, and integrated with LangChain or LlamaIndex retrievers. ## Quick Start Use the pinecone skill to create a serverless index and upsert my document embeddings for a RAG application.

Frequently Asked Questions about pinecone

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Pinecone index in Python?▼

Create a Pinecone index by initializing the Pinecone client with your API key and calling pc.create_index with a name, dimension matching your embedding model, metric such as cosine, and a ServerlessSpec specifying cloud and region.

How to perform hybrid search with dense and sparse vectors in Pinecone?▼

Hybrid search in Pinecone works by upserting vectors with both values and sparse_values fields, then querying with vector and sparse_vector parameters plus an alpha weight where 0 is sparse only, 1 is dense only, and 0.5 is balanced.

Pinecone vs Chroma vs FAISS for vector search?▼

Pinecone is a fully managed serverless SaaS with auto-scaling and a 99.9% uptime SLA, while Chroma is self-hosted and open-source, and FAISS is an offline library for pure similarity search. Choose Pinecone when you do not want to manage infrastructure.

Does Pinecone support metadata filtering in queries?▼

Pinecone supports metadata filtering using operators like $eq, $gte, $lte, $in, $and, and $or passed via the filter parameter in index.query. Filtering adds roughly 10-20ms of latency overhead per query.

Can I use Pinecone with LangChain or LlamaIndex?▼

Pinecone integrates with LangChain through PineconeVectorStore for similarity search and retrievers, and with LlamaIndex through its PineconeVectorStore connected to a StorageContext. Both require an existing Pinecone index.

When should I not use Pinecone serverless?▼

Pinecone serverless is less suitable when you need consistent p95 latency or high sustained throughput, where pod-based indexes with dedicated resources perform better. Self-hosted alternatives fit teams avoiding SaaS dependencies.