Choose a Provider Upstream
A provider upstream is the model service AISIX AI Gateway calls after resolving a caller-facing model alias. AISIX stores the upstream credential in a provider key and uses an adapter to send requests in the format that the upstream expects.
Choose the setup path for the endpoint and account you use, not only for the model family. Configure Gemini through Google AI Studio when you have an AI Studio API key. Use Google Vertex AI when the model is hosted in a Google Cloud project.
Setup Paths
Choose among the direct provider and managed-platform setups:
| Setup | Use When | Adapter |
|---|---|---|
| OpenAI | You call models through an OpenAI API account. | openai |
| Azure OpenAI | An Azure OpenAI deployment hosts the model. | azure-openai |
| Anthropic | You call Claude through the Anthropic API. | anthropic |
| AWS Bedrock | AWS Bedrock hosts the model or inference profile. | bedrock |
| Gemini (Google AI Studio) | You call Gemini with a Google AI Studio API key. | openai |
| Google Vertex AI | A Google Cloud project hosts Gemini or another Vertex publisher model. | vertex |
| Qwen (Alibaba Cloud) | You call Qwen through Alibaba Cloud Model Studio. | openai |
| DeepSeek | You call models through the DeepSeek API. | openai |
| Groq | You call Groq-hosted models. | openai |
| Mistral AI | You call models through the Mistral API. | openai |
| Together AI | You call models from the Together AI catalog. | openai |
For another public or private endpoint that accepts OpenAI-compatible chat-completions requests, choose the corresponding general setup:
| Setup | Use When | Adapter |
|---|---|---|
| Other OpenAI-Compatible Providers | A public provider exposes an OpenAI-compatible API and does not have a dedicated setup guide. | openai |
| Bring Your Own Endpoint | You operate a private or self-hosted OpenAI-compatible endpoint such as vLLM, SGLang, or Ollama. | openai |
Each setup creates the same gateway resources: a provider key, a model alias, and a caller API key. The setup page provides the credential, upstream model identifier, and base URL shape for that path. Compare route support in Provider Compatibility, or review the upstream request formats in Adapter Protocol Families.