Skip to main content
Products & Tools

Pinecone Python SDK - Pinecone Docs - Pinecone Docs

Fetch the complete documentation index at: /llms.txt Use this file to discover all available pages before exploring further. For installation instructions, usage examples, and reference information, see the Pinecone Python SDK documentation .

By Precis Daily Newsroom6 min read1,299 words
Illustration for: Pinecone Python SDK - Pinecone Docs - Pinecone Docs
Illustration
Key points
  • Fetch the complete documentation index at: /llms.txt Use this file to discover all available pages before exploring further.
  • For installation instructions, usage examples, and reference information, see the Pinecone Python SDK documentation .
  • The Pinecone Python SDK requires Python 3.9 or later.

Fetch the complete documentation index at: /llms.txt Use this file to discover all available pages before exploring further. For installation instructions, usage examples, and reference information, see the Pinecone Python SDK documentation . To report an issue or request a feature, file an issue on GitHub . The Pinecone Python SDK is distributed on PyPI using the package name pinecone . By default, the pinecone package has a minimal set of dependencies and interacts with Pinecone via HTTP requests. However, you can install the following extras to unlock additional functionality: pinecone[grpc] adds dependencies on grpcio and related libraries needed to run data operations such as upserts and queries over gRPC for a modest performance improvement. pinecone[asyncio] adds a dependency on aiohttp and enables usage of async methods for use with asyncio . For more details, see Async requests . The Pinecone Python SDK requires Python 3.9 or later. It has been tested with CPython versions from 3.9 to 3.13. SDK versions are pinned to specific API versions . When a new API version is released, a new version of the SDK is also released. The mappings between API versions and Python SDK versions are as follows: API version SDK version 2026-07 v10.x 2026-04 v9.x 2025-10 v8.x 2025-04 v7.x 2025-01 v6.x 2024-10 v5.3.x 2024-07 v5.0.x-v5.2.x 2024-04 v4.x When a new stable API version is released, you should upgrade your SDK to the latest version to ensure compatibility with the latest API changes. To install the latest version of the Python SDK , run the following command: # Install the latest version with gRPC extras # Install the latest version with asyncio extras To install a specific version of the Python SDK, run the following command: # Install a specific version with gRPC extras pip install "pinecone[grpc]"== < versio n > # Install a specific version with asyncio extras pip install "pinecone[asyncio]"== < versio n > To check your SDK version, run the following command: To use the Inference API , you must be on version 5.0.0 or later. Install the Pinecone Assistant Python plugin As of Python SDK v7.0.0, the pinecone-plugin-assistant package is included by default. It’s only necessary to install the package if you are using a version of the Python SDK prior to v7.0.0. pip install --upgrade pinecone pinecone-plugin-assistant Before upgrading to v6.0.0 , update all relevant code to account for the breaking changes explained here . Also, make sure to upgrade using the pinecone package name instead of pinecone-client ; upgrading with the latter will not work as of v6.0.0 . If you already have the Python SDK, upgrade to the latest version as follows: # Upgrade to the latest version with gRPC extras # Upgrade to the latest version with asyncio extras pip install "pinecone[asyncio]" --upgrade Once installed, you can import the library and then use an API key to initialize a client instance: pc = Pinecone( api_key = "YOUR_API_KEY" ) from pinecone.grpc import PineconeGRPC as Pinecone pc = Pinecone( api_key = "YOUR_API_KEY" ) When creating an index , import the ServerlessSpec or PodSpec class as well: from pinecone.grpc import PineconeGRPC as Pinecone pc = Pinecone( api_key = "YOUR_API_KEY" ) from pinecone.grpc import PineconeGRPC as Pinecone pc = Pinecone( api_key = "YOUR_API_KEY" ) If your network setup requires you to interact with Pinecone through a proxy, you will need to pass additional configuration using optional keyword parameters: proxy_url : The location of your proxy. This could be an HTTP or HTTPS URL depending on your proxy setup. proxy_headers : Accepts a python dictionary which can be used to pass any custom headers required by your proxy. If your proxy is protected by authentication, use this parameter to pass basic authentication headers with a digest of your username and password. The make_headers utility from urllib3 can be used to help construct the dictionary. Note: Not supported with Asyncio. ssl_ca_certs : By default, the client will perform SSL certificate verification using the CA bundle maintained by Mozilla in the certifi package. If your proxy is using self-signed certicates, use this parameter to specify the path to the certificate (PEM format). ssl_verify : SSL verification is enabled by default, but it’s disabled when set to False . It’s not recommened to go into production with SSL verification disabled. proxy_headers = make_headers( proxy_basic_auth = 'username:password' ), from pinecone.grpc import PineconeGRPC as Pinecone proxy_headers = make_headers( proxy_basic_auth = 'username:password' ), Pinecone Python SDK versions 6.0.0 and later provide async methods for use with asyncio . Asyncio support makes it possible to use Pinecone with modern async web frameworks such as FastAPI , Quart , and Sanic , and should significantly increase the efficiency of running requests in parallel. Use the PineconeAsyncio class to create and manage indexes and the IndexAsyncio class to read and write index data. To ensure that sessions are properly closed, use the async with syntax when creating PineconeAsyncio and IndexAsyncio objects. from pinecone import PineconeAsyncio, ServerlessSpec async with PineconeAsyncio( api_key = "YOUR_API_KEY" ) as pc: pc = Pinecone( api_key = "YOUR_API_KEY" ) async with pc.IndexAsyncio( host = "INDEX_HOST" ) as idx: "description" : "The story of the mysteriously wealthy Jay Gatsby and his love for the beautiful Daisy Buchanan." , "description" : "A young girl comes of age in the segregated American South and witnesses her father's courageous defense of an innocent black man." , "description" : "In a dystopian future, a totalitarian regime exercises absolute control through pervasive surveillance and propaganda." , Each query is limited to a single namespace . However, the Pinecone Python SDK provides a query_namespaces utility method to run a query in parallel across multiple namespaces in an index and then merge the result sets into a single ranked result set with the top_k most relevant results. The query_namespaces method accepts most of the same arguments as query with the addition of a required namespaces parameter. When using the Python SDK without gRPC extras, to get good performance, it’s important to set values for the pool_threads and connection_pool_maxsize properties on the index client. The pool_threads setting is the number of threads available to execute requests, while connection_pool_maxsize is the number of cached http connections that will be held. Since these tasks aren’t computationally heavy and are mainly i/o bound, it should be okay to have a high ratio of threads to cpus. The combined results include the sum of all read unit usage used to perform the underlying queries for each namespace. Python pc = Pinecone( api_key = "YOUR_API_KEY" ) pool_threads = 50 , # <-- make sure to set these connection_pool_maxsize = 50 , # <-- make sure to set these query_vec = [ 0.1 , ... ] # an embedding vector with same dimension as the index combined_results = index.query_namespaces( namespaces = [ 'ns1' , 'ns2' , 'ns3' , 'ns4' ], filter = { "genre" : { "$eq" : "comedy" }}, for scored_vec in combined_results.matches: When using the Python SDK with gRPC extras, there is no need to set the connection_pool_maxsize because grpc makes efficient use of open connections by default. Python pc = PineconeGRPC( api_key = "YOUR_API_KEY" ) pool_threads = 50 , # <-- make sure to set this query_vec = [ 0.1 , ... ] # an embedding vector with same dimension as the index combined_results = index.query_namespaces( namespaces = [ 'ns1' , 'ns2' , 'ns3' , 'ns4' ], filter = { "genre" : { "$eq" : "comedy" }}, for scored_vec in combined_results.matches: To quickly ingest data when using the Python SDK , use the upsert_from_dataframe method. The method includes retry logic and batch_size , and is performant especially with Parquet file data sets. The following example upserts the uora_all-MiniLM-L6-bm25 dataset as a dataframe. from pinecone import Pinecone, ServerlessSpec from pinecone_datasets import list_datasets, load_dataset dataset = load_dataset( "quora_all-MiniLM-L6-bm25" ) # see https://docs.pinecone.io/guides/manage-data/target-an-index index.upsert_from_dataframe(dataset.drop( columns = [ "blob" ]))

Sources

Summarized from the linked originals.

Related stories

Illustration for: SWE-Bench Pro - Scale AI
Products & Tools

Evaluating challenging long-horizon software engineering tasks in public open source repositories SWE-Bench Pro is a benchmark designed to provide a rigorous and realistic evaluation of AI agents for software engineering.

Scale AI7 min