Skip to main content

Monitor organization-level usage and costs

To view usage and costs across your Pinecone organization, you must be an organization owner or billing admin. Also, this feature is available only to organizations on the Standard or Enterprise plans.
The Usage dashboard in the Pinecone console gives you a detailed report of usage and costs across your organization, broken down by each billable SKU or aggregated by project or service. You can view the report in the console or download it as a CSV file for more detailed analysis.
  1. Go to Settings > Usage in the Pinecone console.
  2. Select the time range to report on. This defaults to the last 30 days.
  3. Select the scope for your report:
    • SKU: The usage and cost for each billable SKU, for example, read units per cloud region, storage size per cloud region, or tokens per embedding model.
    • Project: The aggregated cost for each project in your organization.
    • Service: The aggregated cost for each service your organization uses, for example, database (includes serverless back up and restore), assistants, inference (embedding and reranking), and collections.
  4. Choose the specific SKUs, projects, or services you want to report on. This defaults to all.
  5. To download the report as a CSV file, click Download.
    The CSV download provides more granular detail than the console view, including breakdowns by individual index as well as project and index tags.
Dates are shown in UTC to match billing invoices. Cost data is delayed up to three days from the actual usage date.

Set monthly spend alerts

You can set up email alerts to monitor your organization’s monthly spending. These alerts notify designated recipients when spending reaches specified thresholds. The alerts automatically reset at the start of each monthly billing cycle.
Spend alerts are available on the Standard and Enterprise plans. They’re not needed on the Starter or Builder plans, where usage is capped by plan quotas rather than billed per unit.
To set a spend alert:
  1. Go to Settings > Spend alerts in the Pinecone console
  2. Click + Add Alert.
  3. Enter the dollar amount for the spend alert.
  4. Enter the email addresses to send the alert to. Organization owners are listed by default.
  5. Click Create.
To edit a spend alert:
  1. In the row of the spend alert you want to edit, click ellipsis (…) menu > Edit.
  2. Change the dollar amount and/or email addresses for the spend alert.
  3. Click Update.
Auto-spend spike alert: To protect from unexpected cost increases, Pinecone sends an alert when spending exceeds double your previous month’s invoice amount. While the alert threshold is fixed and the alert can’t be deleted, you can modify which email addresses receive the alert and enable or disable the alert notifications.

Monitor index-level usage

You can monitor index-level usage directly in the Pinecone console, or you can pull them into Prometheus. For more details, see Monitoring.

Monitor operation-level usage

Read units

Query, fetch, and list by ID requests return a usage parameter with the read unit consumption of each request that’s made.
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.
Indexes built on Dedicated Read Nodes aren’t subject to read unit limits for query, fetch, list, and full-text search operations. For sizing and capacity planning guidance, see the Dedicated Read Nodes guide.
Example query request:
The response looks like this:
For a more in-depth demonstration of how to use read units to inspect read costs, see this 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 parameter with the total tokens generated. For example, the following request to use the multilingual-e5-large model to generate embeddings for sentences related to the word “apple” might return this request and summary of embedding tokens generated:
The returned object looks like this:

See also