Enhance Vertex AI context caching documentation#745
Open
mintlify[bot] wants to merge 1 commit intomainfrom
Open
Enhance Vertex AI context caching documentation#745mintlify[bot] wants to merge 1 commit intomainfrom
mintlify[bot] wants to merge 1 commit intomainfrom
Conversation
- Clarify distinction from Portkey gateway caching - Note that context caching is Gemini-specific on Vertex AI - Reorganize into two use cases: using existing caches and creating new caches - Add context caching pricing information - Improve explanation of custom-host proxy pattern for cache creation Generated-By: mintlify-agent
|
@cursor review this pr for correctness |
|
Skipping Bugbot: Bugbot is disabled for this repository. Visit the Bugbot dashboard to update your settings. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
cached_contentparameterx-portkey-custom-hostheaderAddresses customer confusion reported in tickets #1340, #2338.