Qwen3 Coder 30B:
Everything you need to know about the model

Qwen3 Coder 30B is a Qwen model available through Merge Gateway via Amazon Bedrock. Use it with Gateway routing policies, spend controls, request logs, and a 262,144 token context window. It supports streaming through at least one Gateway vendor route.

Qwen3 Coder 30B pricing

| Vendor | Input / 1M tokens | Output / 1M tokens | Zero data retention | | --- | ---: | ---: | --- | | Amazon Bedrock | $0.1500 | $0.6000 | Yes |

Test Qwen3 Coder 30B with Merge Gateway’s Simulator

Qwen3 Coder 30B
Synced
Synced
Run simulation to see response

Ready to try it out?

Start routing requests to hundreds of large language models in your product within minutes.

Route requests to Qwen3 Coder 30B with Merge Gateway

Merge Gateway is a unified LLM API that lets your product route requests to Qwen3 Coder 30B and every other major model through a single endpoint. You get built-in fallback routing, per-request cost tracking, zero data retention support, and observability without changing your application architecture.
To get started in seconds, add our Gateway Implementation skill to your project, or pick your preferred SDK below. Check out our other quick start skills here.
Install the Merge Gateway SDK
Python
1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11
Make your first API call
Python
1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11
Try a diffrent model
Python
1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11
Install the Merge Gateway SDK
Python
1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11
Make your first API call
Python
1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11
Try a diffrent model
Python
1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11
Install the Merge Gateway SDK
Python
1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11
Make your first API call
Python
1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11
Try a diffrent model
Python
1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11
Install the Merge Gateway SDK
Python
1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11
Make your first API call
Python
1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11
Try a diffrent model
Python
1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Explore other models available in Merge Gateway

model logo
GPT-4 Turbo
model logo
Gpt 4 Turbo 2024 04 09
model logo
Gpt 5
model logo
Gpt 5.1
model logo
Gpt 5.1 2025 11 13
model logo
Gpt 5.1 Chat Latest
model logo
Gpt 5.2
model logo
Gpt 5 2025 08 07
model logo
Gpt 5.2 2025 12 11
model logo
Gpt 5.2 Chat Latest
model logo
Gpt 5.3 Chat Latest
model logo
Gpt 5.4
model logo
Gpt 5.4 2026 03 05
model logo
Gpt 5.4 Mini
model logo
Gpt 5.4 Mini 2026 03 17
model logo
Gpt 5.4 Nano
model logo
Gpt 5.4 Nano 2026 03 17
model logo
GPT-5.5
model logo
Gpt 5.5 2026 04 23
model logo
Gpt 5 Chat Latest
model logo
Gpt 5 Mini
model logo
Gpt 5 Mini 2025 08 07
model logo
Gpt 5 Nano
model logo
Gpt 5 Nano 2025 08 07

Qwen3 Coder 30B FAQ

In case you have any more questions on using Qwen3 Coder 30B, we’ve addressed several below.

Heading

What provider owns Qwen3 Coder 30B?

Qwen3 Coder 30B is a Qwen model.

Which vendors can run Qwen3 Coder 30B?

Amazon Bedrock is the default listed vendor, and other active vendors may also be available.

What context window does Qwen3 Coder 30B support?

Qwen3 Coder 30B supports 262,144 tokens on the primary listed vendor route.

What capabilities does Qwen3 Coder 30B support?

Gateway currently lists streaming support for Qwen3 Coder 30B across its available vendor routes.

Try Qwen3 Coder 30B through Merge Gateway

Route, observe, and control AI requests across providers from one API.