Gemini API
Gemini Now Keeps New Paid Projects' Requests for 55 Days
Since 26 October 2026, Gemini API projects created on the paid tier store every generateContent, streamGenerateContent and batchGenerateContent request for 55 days by default, matching the Interactions API; existing projects keep storage off. The per-request opt-out is a top-level store:false, which the REST API accepts on v1beta, v1 and streaming and rejects inside generationConfig, on countTokens and on the OpenAI-compatible chat/completions endpoint (400 in both states). Captured on a local server: @google/genai 2.30.0 accepts config.store and sends the request without it; 2.31.0 sends it. google-genai 2.32.0 raises a pydantic ValidationError; 2.33.0 sends it. The SDK versions that can send the field shipped on 23 October, three days before the default flipped. An interaction created with store:false comes back with no id. Nothing in a generateContent response says whether it was stored. The new gemini-api CLI runs on the Interactions API, stored by default.
Marco Kotrotsos·7 Nov 2026·8 min read