Skip to content

[Docs] Note third-party gateway availability for Gemini 4 Argon - #67

Draft
zoomote[bot] wants to merge 1 commit into
mainfrom
docs/gemini-4-argon-2dha6g2aub37r
Draft

zoomote[bot] wants to merge 1 commit into
mainfrom
docs/gemini-4-argon-2dha6g2aub37r

Conversation

@zoomote

@zoomote zoomote Bot commented Oct 16, 2026

Copy link
Copy Markdown

​Opened on behalf of @taltas. Follow up by mentioning @roomote, in the web UI, or in Discord.

What changed

Follow-up to the merged #66. Adds one "Other providers" bullet to the Gemini 4 Argon section of docs/providers/gemini.md: the model is also available through OpenRouter (google/gemini-4-argon), Vercel AI Gateway (google/gemini-4-argon), and Requesty (vertex/gemini-4-argon), and Zoo Code fetches those provider catalogs automatically.

Why this change was made

A provider re-audit (requested by a maintainer via Discord) confirmed these three gateways now list Gemini 4 Argon in their live catalogs. The paired Zoo-Code follow-up PR (Zoo-Code-Org/Zoo-Code#2073) fixes wrong context/output limits that the Vercel AI Gateway catalog reports for this model.

Impact

Users can see at a glance which third-party providers carry Gemini 4 Argon, without implying the Gemini API is the only option. No structural docs changes.

pnpm run check-types passes. Availability was verified against the live OpenRouter, Vercel AI Gateway, and Requesty model catalogs, and the page was rendered locally in the Docusaurus dev server (see screenshot).

Screenshots

Google Gemini provider page with the Gemini 4 Argon section including the new Other providers bullet

Related PRs

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant