Pinecone changed its API changelog

===================================================================
--- before
+++ after
@@ -6,8 +6,43 @@
 
 Skip to main content
 All Pinecone products share this changelog. Use the filters to narrow the list.
 
+2026-09-02
+DatabaseSearch
+
+GENERAL AVAILABILITY: FULL-TEXT SEARCH AND THE DOCUMENTS API
+
+Full-text search is now generally available on API version 2026-07, built on the new Documents API.Create schema-based document indexes that combine full-text (BM25), dense-vector, and sparse-vector ranking fields in a single index. Query them with BM25 token matching, Lucene query syntax, or vector similarity, narrowed by metadata and text-match filters. You can also fetch, update, and delete documents by metadata filter, not just by ID.This is a change at the REST layer: on 2026-07, POST /indexes is schema-only, so the top-level dimension, metric, vector_type, and spec are replaced by a schema. Existing indexes and SDK create_index calls are unaffected. See Adopt the Documents API to check whether your code is affected and how to move.
+
+2026-09-01
+Billing
+
+BULK IMPORT CREDIT IS NO LONGER OFFERED
+
+New Standard and Enterprise subscriptions no longer receive the one-time $250 bulk import credit (1 TB). Imports from object storage are billed at the standard $0.25/GB rate.Credits already granted stay usable until they expire, 60 days after they were granted. The last balances expire by November 1, 2026.For details, see Understanding cost.
+
+2026-09-01
+DatabaseBilling
+
+EGRESS METERING AND MONTHLY EGRESS ALLOWANCES
+
+Pinecone now meters egress, the data returned to you on reads. Each plan includes a monthly egress allowance: 1 GB on Starter, 10 GB on Builder, and 100 GB on Standard and Enterprise.Egress is metered on reads that return record data, such as query, fetch, list, and search. Writes, index statistics, and index management requests aren’t metered. Egress applies to indexes that use dedicated read nodes as well as on-demand indexes.On Standard and Enterprise, egress beyond the allowance is billed at the rate on the pricing page, and reads keep serving. On Starter and Builder, reads that return record data are blocked once the allowance is reached, and the allowance resets at the start of the next billing period.
+
+2026-09-01
+Database
+
+BYOC STORES CLUSTER METADATA IN FOUNDATIONDB
+
+BYOC deployments run FoundationDB inside your Kubernetes cluster to store cluster metadata, with no managed database to operate.
+
+2026-08-31
+Marketplace
+
+END OF LIFE: PINECONE MARKETPLACE
+
+Pinecone Marketplace has reached end of life and is no longer available.Marketplace ran on Pinecone Assistant. To keep querying your data, see Pinecone Assistant, and contact Support if you need help.
+
 2026-08-25
 Database
 
 GENERAL AVAILABILITY: BRING YOUR OWN CLOUD (BYOC)
@@ -83,16 +118,16 @@
 
 COHERE RERANK 4.0 FAST IS GENERALLY AVAILABLE, AND COHERE-RERANK-3.5 IS DEPRECATED
 
 cohere-rerank-4-fast (Cohere Rerank 4.0 Fast) is now generally available as a reranking model on Pinecone. It succeeds cohere-rerank-3.5, improves relevance quality, and supports multiple rerank fields. Cohere Rerank 4.0 is hosted on Azure AI under the Global Standard deployment type, and requests may be processed in regions outside the United States.With this release, cohere-rerank-3.5 is deprecated:
- * Through July 31, 2026: cohere-rerank-3.5 continues to serve requests as before.
- * August 1, 2026: requests to cohere-rerank-3.5 are automatically served by cohere-rerank-4-fast.
+ * Through August 30, 2026: cohere-rerank-3.5 continues to serve requests as before.
+ * August 31, 2026: requests to cohere-rerank-3.5 are automatically served by cohere-rerank-4-fast.
 
 No code change is required for the transition, but note two differences before you migrate:
- * Relevance scores differ. cohere-rerank-4-fast returns different scores than cohere-rerank-3.5. If your application relies on hard-coded score thresholds, re-tune them against cohere-rerank-4-fast before August 1.
+ * Relevance scores differ. cohere-rerank-4-fast returns different scores than cohere-rerank-3.5. If your application relies on hard-coded score thresholds, re-tune them against cohere-rerank-4-fast before August 31.
  * Billing counts units differently. The per-unit rate is unchanged at $2.00 per 1,000 rerank units. One rerank unit covers a query plus up to 100 documents, with documents longer than ~500 tokens auto-chunked into ~500-token chunks that each count toward that 100. As a result, cohere-rerank-4-fast can bill multiple units for a large request, whereas cohere-rerank-3.5 billed one unit per request.
 
-To control the transition yourself, migrate your rerank requests to cohere-rerank-4-fast before August 1. For model details and parameters, see Reranking models.
+To control the transition yourself, migrate your rerank requests to cohere-rerank-4-fast before August 31. For model details and parameters, see Reranking models.
 
 2026-06-03
 DatabaseBilling
 
@@ -122,12 +157,10 @@
  * Multi-domain routing — Route end-user queries across multiple knowledge domains within a single deployment.
  * Evaluations and analytics — Run evaluations against your deployment and monitor usage with event logs.
  * Versioning and rollback — Publish deployment versions and roll back to previous configurations.
  * End-user experience — Authenticated chat interface with citations, visual components, and feedback collection.
- * Increased Starter plan limits - The Starter plan is currently offering 1M input tokens per month (500K before promotion) to help explore Marketplace apps until June 30, 2026.
+ * Increased Starter plan limits — The Starter plan offered 1M input tokens per month (500K before promotion) to help explore Marketplace apps until June 30, 2026.
 
-For details, see the Marketplace quickstart and Marketplace API reference.
-
 2026-05-04
 Billing
 
 NEW BUILDER PLAN