SDK
2 articles
-
Gemini APIGemini 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.
-
AnthropicAnthropic's New SDKs Can Drop Your API Key Behind a Gateway
On 21 October Anthropic released API version 2026-10-21, the first since 2023-06-01, with new SDK majors (Python 2.0.0, TypeScript 1.0.0, Go 2.0.0, Java 3.0.0, C# 13.0.0, PHP 1.0.0, Ruby 2.0.0, ant CLI 2.0.0) that send it by default and on which temperature, top_p and top_k return a 400 even at default values. The SDKs also move the API key from X-Api-Key into Authorization: Bearer. On a local capture server, a gateway token set in that header through default_headers replaced the key outright with no error; the guide's fix (auth_token plus X-Api-Key in default_headers, with the gateway stripping its own Authorization) and the undocumented version pin (default_headers anthropic-version 2023-06-01 plus extra_body temperature) both produced the expected request. LiteLLM reads Authorization before x-api-key, so its virtual keys still arrive.