Skip to content

Clarify Google Vertex AI API schema usage - #128648

Open
brendonmatheson wants to merge 1 commit into
MicrosoftDocs:mainfrom
brendonmatheson:patch-1
Open

Clarify Google Vertex AI API schema usage#128648
brendonmatheson wants to merge 1 commit into
MicrosoftDocs:mainfrom
brendonmatheson:patch-1

Conversation

@brendonmatheson

Copy link
Copy Markdown

Google support both their native generateDontent API and the OpenAI compatible API on their platform.

The mention of Google Vertex AI API leads one to believe it's the native format, not the OpenAI compatible format. But from my testing and scouring the internet, we do not support the generateContent API schema, only the OpenAI schema for Google Gemini models.

Therefore, I'm proposing to add the clarification so that readers are not confused and don't waste time trying to get generateContent working.

@prmerger-automator

Copy link
Copy Markdown
Contributor

@brendonmatheson : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. @dlepow

@prmerger-automator

Copy link
Copy Markdown
Contributor

@brendonmatheson : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. @dlepow

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 89b8d6e:

✅ Validation status: passed

File Status Preview URL Details
includes/api-management-llm-models.md ✅Succeeded

For more details, please refer to the build report.

@v-regandowner

Copy link
Copy Markdown
Contributor

@PatAltimore

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator Bot added the aq-pr-triaged tracking label for the PR review team label Jul 21, 2026
@brendonmatheson

Copy link
Copy Markdown
Author

My proposed change should be verified with the product team - I've made the proposal based on a day of testing and searching but I'm blackbox testing this since I cannot find any docs that show how to get generateContent to work.

The go-to AI Gateway sample project uses the Open AI schema rather than generateContent: https://github.com/Azure-Samples/AI-Gateway/tree/main/labs/google-gemini-api

And I have been unable to find any samples or docs that show llm-emit-token-metrics grabbing token counts from the usageMetadata element of a generateContent response. But the absence of such docs doesnt necessarily mean the feature doesn't exist.

@PatAltimore

Copy link
Copy Markdown
Contributor

Adding @anishtallapureddy. Anish, could you comment on the change? Thanks.

@v-dirichards

Copy link
Copy Markdown
Contributor

#assign: @anishtallapureddy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants