Qwen/Qwen3-Next-80B-A3B-Instruct is a Qwen model available through Merge Gateway via Parasail. Use it with Gateway routing policies, spend controls, request logs, and a 262,144 token context window. It supports streaming, tool calling through at least one Gateway vendor route.
Qwen/Qwen3-Next-80B-A3B-Instruct performance*
Intelligence - general reasoning and knowledge
20%
Coding - code generation and problem-solving
15%
*Performance data is provided by Artificial Analysis and is subject to change.
Qwen/Qwen3-Next-80B-A3B-Instruct pricing
| Vendor | Input / 1M tokens | Output / 1M tokens | Zero data retention |
| --- | ---: | ---: | --- |
| Parasail | $0.1000 | $1.10 | Yes |
Test Qwen/Qwen3-Next-80B-A3B-Instruct with Merge Gateway’s Simulator
Qwen/Qwen3-Next-80B-A3B-Instruct
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 Qwen/Qwen3-Next-80B-A3B-Instruct with Merge Gateway
Merge Gateway is a unified LLM API that lets your product route requests to Qwen/Qwen3-Next-80B-A3B-Instruct 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}
11Make 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}
11Try 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}
11Install 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}
11Make 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}
11Try 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}
11Install 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}
11Make 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}
11Try 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}
11Install 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}
11Make 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}
11Try 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}
11Explore other models available in Merge Gateway
Qwen/Qwen3-Next-80B-A3B-Instruct FAQ
In case you have any more questions on using Qwen/Qwen3-Next-80B-A3B-Instruct, we’ve addressed several below.
Heading
What provider owns Qwen/Qwen3-Next-80B-A3B-Instruct?
Qwen/Qwen3-Next-80B-A3B-Instruct is a Qwen model.
Which vendors can run Qwen/Qwen3-Next-80B-A3B-Instruct?
Parasail is the default listed vendor, and other active vendors may also be available.
What context window does Qwen/Qwen3-Next-80B-A3B-Instruct support?
Qwen/Qwen3-Next-80B-A3B-Instruct supports 262,144 tokens on the primary listed vendor route.
What capabilities does Qwen/Qwen3-Next-80B-A3B-Instruct support?
Gateway currently lists streaming, tool calling support for Qwen/Qwen3-Next-80B-A3B-Instruct across its available vendor routes.
Try Qwen/Qwen3-Next-80B-A3B-Instruct through Merge Gateway
Route, observe, and control AI requests across providers from one API.
