You can proxy requests to Databricks AI models through AI Gateway by creating AI Model Provider and AI Model entities. This reference documents all supported AI capabilities, configuration requirements, and provider-specific details needed for proper integration.
Databricks provider
Upstream paths
AI Gateway automatically routes requests to the appropriate Databricks API endpoints. The following table shows the upstream paths used for each capability.
|
Capability |
Path template |
Description |
Upstream path or API |
|---|---|---|---|
| Generate |
/chat/completions, /completions, or /responses
|
Text generation for chat completions and responses | /serving-endpoints/v1/chat/completions |
Supported capabilities
The following tables show the AI capabilities supported by the Databricks provider when configuring AI Models.
By default, AI Gateway uses the path templates shown in the tables below (e.g.,
/chat/completions,/embeddings, etc.). To customize these paths, configure theconfig.pathsfield in your AI Model entity. Custom paths take the form{configured_path}/{template_path}— for example, if you set a custom path of/v2, requests to/embeddingswould be routed to/v2/embeddings.
Text generation
Support for Databricks text generation capabilities:
|
Capability |
Streaming |
Model example |
Path template |
Min version |
|---|---|---|---|---|
| generate | Supported | databricks-gpt-oss-20b |
/chat/completions, /completions, or /responses
|
2.0 |
Databricks base URL
The base URL is https://{databricks_instance}.cloud.databricks.com:443.
AI Gateway uses this URL automatically. You only need to configure a URL if you’re using a self-hosted or Databricks-compatible endpoint, in which case set the upstream_url option in your AI Model configuration.
Configure Databricks
To use Databricks with AI Gateway, configure a new AI Model Provider. You can then access supported AI Models from Databricks.
Here’s a minimal configuration for chat completions:
Configure a model target for Databricks
A target is an entry in the targets array on the AI Model entity, not the AI Model Provider. Beyond the common target options (name, provider, weight), a target routing to Databricks requires:
workspace_instance_id: The Databricks workspace instance ID hosting the model.
targets:
- name: databricks-dbrx-instruct
provider: my-databricks-account
config:
type: databricks
workspace_instance_id: my-workspace-instance-id