Gemini 2.5 Models now support implicit caching

In May 2024, a significant advancement in context caching aimed at reducing repetitive context costs by 75% was introduced, and now, the Gemini API is enhancing this with a new feature: implicit caching. This feature allows developers to benefit from cache savings without setting up an explicit cache, as requests sharing a common prefix with previous ones are eligible for cache hits, dynamically providing cost savings. To optimize requests for cache hits, it's recommended to keep consistent content at the start and place variable elements like user questions at the end. The minimum request size for cache eligibility has been decreased to 1024 tokens for the 2.5 Flash model and 2048 for the 2.5 Pro model. Developers can still use the explicit caching API to ensure guaranteed savings, with the usage metadata now indicating cached tokens charged at a lower price. The company expresses enthusiasm for these developments and encourages feedback on the updates.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.