How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Pinecone Vector Operations API

The Vector Operations API from Pinecone — 10 operation(s) for vector operations.

Pinecone Vector Operations API is one of 9 APIs that Pinecone publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Vector Operations. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 10 operations across 10 paths, and defines 34 schemas. It is described by OpenAPI 3.2.0, at version 2025-10.

Requests are made against a single base URL, https://{index_host}.

10 operations 10 paths 34 schemas 2 GET8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2025-10
Base URL
https://api.pinecone.io
Authentication
API Key
License
Resource Areas
1

Authentication & Security 1

Pinecone Vector Operations API declares 1 security scheme for authenticating requests. An API key is passed in the header as Api-Key (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — An API Key is required to call Pinecone APIs. Get yours from the [console](https://app.pinecone.io/).

Paths & Operations 10

Across 10 paths, the API surfaces 10 operations — 2 GET, 8 POST. Each is listed below with its method, path, parameters, and response codes.

Vector Operations 10
POST
/describe_index_stats
Get index stats
describeIndexStats 1 param body → 2004004XX5XX
POST
/query
Search with a vector
queryVectors 1 param body → 2004004XX5XX
POST
/vectors/delete
Delete vectors
deleteVectors 1 param body → 2004004XX5XX
GET
/vectors/fetch
Fetch vectors
fetchVectors 3 params → 2004004XX5XX
POST
/vectors/fetch_by_metadata
Fetch vectors by metadata
fetch_vectors_by_metadata 1 param body → 2004004XX5XX
GET
/vectors/list
List vector IDs
listVectors 5 params → 2004004XX5XX
POST
/vectors/update
Update a vector
updateVector 1 param body → 2004004XX5XX
POST
/vectors/upsert
Upsert vectors
upsertVectors 1 param body → 2004004XX5XX
POST
/records/namespaces/{namespace}/upsert
Upsert text
upsertRecordsNamespace 2 params body → 2014004XX5XX
POST
/records/namespaces/{namespace}/search
Search with text
searchRecordsNamespace 2 params body → 2004004XX5XX

Schemas 34

The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are QueryRequest (11 properties), IndexDescription (8 properties), UpdateRequest (7 properties), ScoredVector (5 properties). Each schema is shown below with its type and property counts.

DeleteResponse
object
The response for the delete operation.
QueryResponse
object
The response for the query operation. These are the matches found for a particular query vector. The matches are ordered from most similar to least similar.
4 properties
FetchByMetadataRequest
object
The request for the fetchbymetadata operation.
4 properties
SearchRecordsVector
object
3 properties
NamespaceSummary
object
A summary of the contents of a namespace.
1 property
Pagination
object
1 property
Usage
object
1 property
UpdateResponse
object
The response for the update operation.
1 property
Hit
object
A record whose vector values are similar to the provided search query.
3 properties 3 required
DeleteRequest
object
The request for the delete operation.
4 properties
FetchByMetadataResponse
object
The response for the fetchbymetadata operation.
4 properties
ListResponse
object
The response for the list operation.
4 properties
FetchResponse
object
The response for the fetch operation.
3 properties
IndexDescription
object
The response for the describeindexstats operation.
8 properties
rpcStatus
object
3 properties
QueryRequest
object
The request for the query operation.
11 properties 1 required
SingleQueryResults
object
2 properties
SearchRecordsResponse
object
The records search response.
2 properties 2 required
UpsertRecord
object
The request for the upsert operation.
1 property 1 required
Vector
object
4 properties 1 required
UpsertRequest
object
The request for the upsert operation.
2 properties 1 required
protobufAny
object
2 properties
SearchMatchTerms
object
Specifies which terms must be present in the text of each search hit based on the specified strategy. The match is performed against the text field specified i…
2 properties
VectorValues
array
This is the vector data included in the request.
SparseValues
object
Vector sparse data. Represented as a list of indices and a list of corresponded values, which must be with the same length.
2 properties 2 required
UpdateRequest
object
The request for the update operation.
7 properties
QueryVector
object
A single query vector within a QueryRequest.
5 properties 1 required
ScoredVector
object
5 properties 1 required
EmbedInputs
object
UpsertResponse
object
The response for the upsert operation.
1 property
ListItem
object
1 property
SearchUsage
object
3 properties 1 required
SearchRecordsRequest
object
A search request for records in a specific namespace.
3 properties 1 required
DescribeIndexStatsRequest
object
The request for the describeindexstats operation.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pinecone-vector-operations-api-openapi.yml Raw ↑

Other APIs Pinecone publishes across the network.

Pinecone API Keys API
Pinecone Bulk Operations API
Pinecone Inference API
Pinecone Manage Assistants API
Pinecone Manage Indexes API
Pinecone Namespace Operations API
Pinecone Organizations API
Pinecone Projects API
Where this information came from

This is an independent, third-party profile of Pinecone Vector Operations API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.