Get index stats
Return statistics about the contents of an index, including the vector count per namespace, the number of dimensions, and the index fullness.
Serverless indexes scale automatically as needed, so index fullness is relevant only for pod-based indexes.
# To get the unique host for an index,
# see https://docs.pinecone.io/guides/manage-data/target-an-index
PINECONE_API_KEY="YOUR_API_KEY"
INDEX_HOST="YOUR_INDEX_HOST"
curl -X POST "https://$INDEX_HOST/describe_index_stats" \
-H "Api-Key: $PINECONE_API_KEY" \
-H "X-Pinecone-Api-Version: 2026-07"POST /describe_index_stats
{
"dimension": 1024,
"indexFullness": 0.4,
"namespaces": {
"": {
"vectorCount": 50000
},
"example-namespace-2": {
"vectorCount": 30000
}
},
"totalVectorCount": 80000
}{
"code": 123,
"message": "<string>",
"details": [
{
"typeUrl": "<string>",
"value": "<string>"
}
]
}{
"code": 123,
"message": "<string>",
"details": [
{
"typeUrl": "<string>",
"value": "<string>"
}
]
}{
"code": 123,
"message": "<string>",
"details": [
{
"typeUrl": "<string>",
"value": "<string>"
}
]
}Authorizations
Section titled “Authorizations”Api-KeystringrequiredAn API Key is required to call Pinecone APIs. Get yours from the console.
Headers
Section titled “Headers”X-Pinecone-Api-VersionstringrequiredRequired date-based version header
filter?objectIf this parameter is present, the operation only returns statistics for vectors that satisfy the filter. See Understanding metadata. Serverless and Starter indexes do not support filtering describe_index_stats by metadata, and reject a request carrying a non-empty filter.
Response
Section titled “Response”200 — A successful response.
The response for the describe_index_stats operation.
namespaces?objectA mapping for each namespace in the index from the namespace name to a summary of its contents.
dimension?integerThe dimension of the indexed vectors. Not specified if sparse index.
Example: 1024
indexFullness?numberExample: 0.4
The fullness of the index, reported to a granularity of 1% and capped at 1.0. Always 0 for indexes with on-demand read capacity. Serverless indexes scale automatically as needed, so index fullness is relevant only for pod-based indexes. The index fullness result may be inaccurate during pod resizing; to get the status of a pod resizing process, use describe_index.
totalVectorCount?integerThe total number of vectors in the index, regardless of whether a metadata filter expression was passed
Example: 80000
metric?stringThe metric used to measure similarity.
Example: cosine
vectorType?stringThe type of vectors stored in the index.
Example: dense
memoryFullness?numberThe amount of memory used by a dedicated index
storageFullness?numberThe amount of storage used by a dedicated index