Practical overview
When it fits
Use it when a TypeScript project needs a fetch-based client for Pinecone vector operations and benefits from generic metadata typing.
Who it is for
- TypeScript developers integrating Pinecone into an application or developer tool.
- Teams that want typed vector metadata and query results.
Documented uses
- Insert vectors and metadata into Pinecone.
- Query vectors using metadata filters and typed results.
- Fetch, update or delete vectors and manage Pinecone indexes from application code.
Requirements & limits
The repository is public and declares an MIT license. The package is installed through npm; no price or account policy is described.
- Native ESM only: CommonJS projects need conversion or dynamic import.
- The listed runtimes are Deno, Node.js 18+, Cloudflare Workers and browsers; environments without native fetch are unsupported.
- Pinecone API credentials and an index URL are needed for API calls, either in client configuration or through the documented environment variables.
- The README points to Pinecone’s similar TypeScript client as an option for developers who do not need fully typed metadata.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up a Pinecone Client instance
Install the package and configure a client with Pinecone connection details.
Before you start
- A supported fetch-based runtime: Deno, Node.js 18+, Cloudflare Workers or a browser.
- Pinecone API key and index URL.
Steps
Install the package with the command below.
npm install pinecone-clientImport
PineconeClientfrompinecone-client.Create a client instance with
apiKey,baseUrland an optional namespace, or provide the documentedPINECONE_API_KEYandPINECONE_BASE_URLenvironment variables.
Expected outcome
A configured client instance that can be used to make Pinecone API calls.
Guide limitations
- The package is native ESM and does not provide a CommonJS export; CommonJS projects must convert to ESM or use dynamic import.
- The README lists environments without native fetch, including Node versions below 17, as unsupported.
Insert and query typed vectors
Use the README’s example pattern to upsert vectors and query them with a metadata filter.
Before you start
- An initialized Pinecone Client instance with Pinecone connection details.
- A TypeScript metadata type for the vectors.
Steps
Define a metadata type, such as fields for a numeric size and optional string tags.
Instantiate
PineconeClientwith that metadata type.Call
upsert()with vector IDs, values and metadata.Call
query()with a top-K value, a vector ID and a metadata filter.
Expected outcome
Vectors are submitted to Pinecone, and the query returns matches whose metadata is typed according to the declared TypeScript type.
Guide limitations
- The README says null metadata values are automatically removed because Pinecone does not accept nulls.
- The example requires a configured Pinecone connection; it does not provide vector generation.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 17 October 2026
- Original website title
- dexaai/pinecone-client · Official homepage title · retained in its source language
Related options
Pinecone TypeScript client — The README identifies Pinecone’s client as a similar option for users who do not require fully typed metadata.

