Roder
Providers

Google Vertex AI

roder-ext-vertex adds provider id vertex for teams whose Google access runs through Vertex AI rather than the Gemini API-key path. It is a sibling of roder-ext-gemini, not a replacement.

What differs from Gemini API

  • Auth uses OAuth2 access tokens minted from service-account credentials or ADC.
  • Endpoints are regional Vertex AI URLs under a Google Cloud project and location.
  • Models are addressed as publisher paths, for example publishers/google/models/gemini-*.
RODER_PROVIDER=vertex RODER_MODEL=gemini-3.5-flash roder
VERTEX_PROJECT=my-project
VERTEX_LOCATION=us-central1
GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account.json

The provider streams Gemini-on-Vertex turns, maps tools, usage, cached-token counts, and finish reasons into canonical Roder inference events, and keeps registration independent from whether credentials are currently configured.