Dashscope provider

Uses: Kong Gateway AI Gateway Admin API deck KIC Konnect API Terraform

Upstream paths

AI Gateway automatically routes requests to the appropriate Dashscope API endpoints. The following table shows the upstream paths used for each capability.

Capability	Upstream path or API
Chat completions	`/compatible-mode/v1/chat/completions`
Embeddings	`/compatible-mode/v1/embeddings`
Image generations	`/api/v1/services/aigc/multimodal-generation/generation`
Image edits	`/api/v1/services/aigc/image2image/image-synthesis`

Supported capabilities

The following tables show the AI capabilities supported by Dashscope provider when used with the AI Proxy or the AI Proxy Advanced plugin.

Set the plugin’s route_type based on the capability you want to use. See the tables below for supported route types.

Text generation

Support for Dashscope basic text generation capabilities including chat, completions, and embeddings:

Capability	Route type	Streaming	Model example	Min version
Chat completions	`llm/v1/chat`		qwen-plus	3.13
Embeddings	`llm/v1/embeddings`		text-embedding-v1	3.13

Image

Support for Dashscope image generation and editing capabilities:

Capability	Route type	Model example	Min version
Generations	`image/v1/images/generations`	qwen-image-plus	3.13
Edits	`image/v1/images/edits`	qwen-image-plus	3.13

For requests with large payloads, consider increasing config.max_request_body_size to three times the raw binary size.

Supported image sizes and formats vary by model. Refer to your provider’s documentation for allowed dimensions and requirements.

Dashscope base URL

The base URL is https://dashscope.aliyuncs.com or https://dashscope-intl.aliyuncs.com, where {route_type_path} is determined by the capability.

AI Gateway uses this URL automatically. You only need to configure a URL if you’re using a self-hosted or Dashscope-compatible endpoint, in which case set the upstream_url plugin option.

Configure Dashscope with AI Proxy

To use Dashscope with AI Gateway, configure the AI Proxy or AI Proxy Advanced.

Here’s a minimal configuration for chat completions:

kong.yaml

Copied!

_format_version: "3.0"
plugins:
  - name: ai-proxy
    config:
      route_type: llm/v1/chat
      auth:
        header_name: Authorization
        header_value: Bearer ${{ env "DECK_DASHSCOPE_API_KEY" }}
      model:
        provider: dashscope
        name: qwen-plus
        options:
          max_tokens: 512
          temperature: 1.0

curl -i -X POST http://localhost:8001/plugins/ \
    --header "Accept: application/json" \
    --header "Content-Type: application/json" \
    --data '
    {
      "name": "ai-proxy",
      "config": {
        "route_type": "llm/v1/chat",
        "auth": {
          "header_name": "Authorization",
          "header_value": "Bearer '$DASHSCOPE_API_KEY'"
        },
        "model": {
          "provider": "dashscope",
          "name": "qwen-plus",
          "options": {
            "max_tokens": 512,
            "temperature": 1.0
          }
        }
      }
    }
    '

Copied!

Make the following request:

curl -X POST https://{region}.api.konghq.com/v2/control-planes/{controlPlaneId}/core-entities/plugins/ \
    --header "accept: application/json" \
    --header "Content-Type: application/json" \
    --header "Authorization: Bearer $KONNECT_TOKEN" \
    --data '
    {
      "name": "ai-proxy",
      "config": {
        "route_type": "llm/v1/chat",
        "auth": {
          "header_name": "Authorization",
          "header_value": "Bearer '$DASHSCOPE_API_KEY'"
        },
        "model": {
          "provider": "dashscope",
          "name": "qwen-plus",
          "options": {
            "max_tokens": 512,
            "temperature": 1.0
          }
        }
      }
    }
    '

Copied!

echo "
apiVersion: configuration.konghq.com/v1
kind: KongClusterPlugin
metadata:
  name: ai-proxy
  namespace: kong
  annotations:
    kubernetes.io/ingress.class: kong
  labels:
    global: 'true'
config:
  route_type: llm/v1/chat
  auth:
    header_name: Authorization
    header_value: Bearer $DASHSCOPE_API_KEY
  model:
    provider: dashscope
    name: qwen-plus
    options:
      max_tokens: 512
      temperature: 1.0
plugin: ai-proxy
" | kubectl apply -f -

Copied!

resource "konnect_gateway_plugin_ai_proxy" "my_ai_proxy" {
  enabled = true

  config = {
    route_type = "llm/v1/chat"

    auth = {
      header_name = "Authorization"
      header_value = "Bearer var.dashscope_api_key"
    }

    model = {
      provider = "dashscope"
      name = "qwen-plus"

      options = {
        max_tokens = 512
        temperature = 1.0
      }
    }
  }

  control_plane_id = konnect_gateway_control_plane.my_konnect_cp.id
}

Copied!

This example requires the following variables to be added to your manifest. You can specify values at runtime by setting TF_VAR_name=value.

variable "dashscope_api_key" {
  type = string
}

Copied!

For more configuration options and examples, see:

AI Proxy examples

AI Proxy Advanced examples

Tutorials

Route Claude CLI traffic through AI Gateway and DashScope View →

Dashscope provider

Upstream paths

Supported capabilities

Text generation

Image

Dashscope base URL

Configure Dashscope with AI Proxy

Tutorials

Help us make these docs great!

Still need help