Skip to main content
Catalyst can proxy Vertex AI in two modes:
  • OpenAI-compatible Vertex endpoint: use the OpenAI SDK and set x-inference-provider-url to your Vertex /endpoints/openapi URL.
  • Native Vertex APIs: call the Vertex model operation path through the Catalyst gateway and set x-inference-provider-url to the global or regional aiplatform.googleapis.com base URL.
Use x-inference-provider: vertex-ai for both modes so Catalyst applies Vertex-specific URL and authentication handling.
This guide is for Gemini and Anthropic through Google Cloud Vertex AI. For direct Gemini API calls using generativelanguage.googleapis.com, see the Google Gemini guide.

Supported Vertex endpoints

Environment

For regional Vertex endpoints, use the regional host:
For the global location, use:

OpenAI-compatible Vertex

Use this path when you want to keep the OpenAI SDK shape for Vertex Gemini models.

Native Gemini on Vertex

Use native Gemini paths when you need Vertex’s generateContent or streamGenerateContent request format.
If you are using a Google API key instead of an OAuth access token for Gemini, pass GEMINI_VERTEX_API_KEY as x-inference-provider-api-key. Catalyst forwards Google API keys to Vertex as the key query parameter.
For Gemini streaming, use :streamGenerateContent. Add ?alt=sse if you want Vertex to return server-sent events.

Anthropic on Vertex

Anthropic models on Vertex use Vertex operation paths and Anthropic’s Vertex payload shape. Use a Google Cloud OAuth access token or service-account-minted access token as x-inference-provider-api-key.
For streaming Anthropic responses on Vertex, use :streamRawPredict and include "stream": true in the body.

Header summary