docs: Google Vertex AI (issue #85) - #91
Open
SebConejo wants to merge 1 commit into
Open
Conversation
…lain Google entry (issue #85)
This was referenced Aug 20, 2026
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.
Processes the two findings of #85, recommended options, verified against the registry entry PR #2736 shipped.
Finding 1 (option 1) — the dashboard offers a Google Vertex AI card and no page named it. The provider joins the Supported providers table, the Key prefixes table (
AQ., enforced in the form with a 40-character minimum), the page description, and the keywords. The name cell stays unlinked:cloud.google.com/vertex-airedirects to a differently branded page, and unlinked name cells already exist in the corpus.Finding 2 (option 1) — a reader now has a basis for choosing between the two Google cards: a short subsection says Vertex AI serves Gemini models through Google Cloud on an express mode API key, while the plain Google entry takes an AI Studio key with no enforced prefix. The wording names no region, no project and no model list, matching what the connect form actually shows.
One caveat from the issue's open questions: nothing here asserts an end-to-end routed request through a real
AQ.key, because neither the audit nor I hold one. The wording describes the connect form and the registry, both code-verified. If you have a Vertex express key, one routed request would close that question.Coherence GREEN (48 pages, 57 vars).
Closes #85