docs: update Gemini API documentation to 2.5 series#128
Merged
hoalongnatsu merged 1 commit intoVersusControl:mainfrom Mar 4, 2026
Merged
docs: update Gemini API documentation to 2.5 series#128hoalongnatsu merged 1 commit intoVersusControl:mainfrom
hoalongnatsu merged 1 commit intoVersusControl:mainfrom
Conversation
- Replace deprecated models (1.0/1.5/2.0) with Gemini 2.5 series - Update model table: gemini-2.5-pro, gemini-2.5-flash, gemini-2.5-flash-lite - Refresh pricing from ai.google.dev/pricing - Update CURL examples to use v1 API and gemini-2.5-flash - Change 'Generative Language API' to 'Gemini API' Closes VersusControl#98 Made-with: Cursor
There was a problem hiding this comment.
Pull request overview
Updates the Gemini API key setup guide to reflect the current Gemini 2.5 model lineup and associated setup examples, incorporating maintainer feedback from #116 and addressing the model freshness request in #98.
Changes:
- Replaces deprecated Gemini model references with the Gemini 2.5 series across model selection and configuration examples.
- Updates pricing table and cost tip to match current rates from Google AI pricing.
- Updates curl examples to use the
v1API withgemini-2.5-flash:generateContent, and renames “Generative Language API” references to “Gemini API”.
Comments suppressed due to low confidence (2)
docs/api-key-setup/gemini-api-setup.md:35
- The doc now instructs enabling/restricting the Gemini API, but later in the same guide ("Configure Google Cloud" step) it still says to enable the Generative AI API. Please align the API name throughout the document or add a brief clarification if these are intentionally different APIs for different setups.
3. Enable the **Gemini API**
4. Go to "Credentials" → "Create Credentials" → "API Key"
5. Restrict the API key to "Gemini API" for security
docs/api-key-setup/gemini-api-setup.md:176
- Because the guide is now branded as "Gemini API", using the
generativelanguage.googleapis.comhostname in the curl examples can be confusing for readers. Consider adding a short note near this example explaining that Gemini API requests are still sent to thegenerativelanguage.googleapis.comendpoint (and why), so users don’t think they’re using the wrong API.
curl -H "Content-Type: application/json" \
-d '{"contents":[{"parts":[{"text":"Hello"}]}]}' \
"https://generativelanguage.googleapis.com/v1/models/gemini-2.5-flash:generateContent?key=$GEMINI_API_KEY"
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Member
|
Thanks for PR |
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
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
Updates the Gemini API setup documentation to the latest Gemini 2.5 series per maintainer feedback on #116.
Changes
Closes #98