Skip to main content
Requests that consume read units or embedding tokens return a usage field alongside their results. Reading it tells you what a single request cost, so you can compare approaches before running them at scale.

Read units

Query, fetch, and list by ID requests return a usage field with the read unit consumption of that request.
While Pinecone tracks read unit usage with decimal precision, the Pinecone API and SDKs round these values up to the nearest whole number in query, fetch, list, and full-text search responses. For example, if a query uses 0.45 read units, the API and SDKs will report it as 1 read unit.For precise read unit reporting, see index-level metrics or the organization-wide Usage dashboard.
Example query request:
The response looks like this:
For a worked example of inspecting read costs, see the read units notebook.

Embedding tokens

Requests to one of Pinecone’s hosted embedding models, either directly via the Generate vectors operation or automatically when upserting or querying an index with integrated embedding, return a usage field with the total tokens generated. For example, this request uses the multilingual-e5-large model to embed sentences related to the word “apple”:
The response looks like this:

See also