Endpoint coverage
Exposes 1 public endpoint(s): chat_completion.
Open-weight Qwen coding model for agents (3B active); 256K context; OpenAI-compatible API
# Base URL
https://runapi.ai
# Endpoints
POST /v1/chat/completions
POST /v1/responses
POST /v1/messages
POST /v1beta/models/qwen3-coder-next:generateContent
POST /v1beta/models/qwen3-coder-next:streamGenerateContent
curl https://runapi.ai/v1/chat/completions \
-H "Authorization: Bearer $RUNAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "qwen3-coder-next",
"messages": [
{
"role": "user",
"content": "Read this screenshot of a failing dashboard, explain what the error message means, and suggest the code change that would fix it."
}
]
}'
from openai import OpenAI
client = OpenAI(
base_url="https://runapi.ai/v1",
api_key="your-runapi-key"
)
response = client.chat.completions.create(
model="qwen3-coder-next",
messages=[{"role": "user", "content": "Read this screenshot of a failing dashboard, explain what the error message means, and suggest the code change that would fix it."}]
)
import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://runapi.ai/v1",
apiKey: "your-runapi-key"
});
const response = await client.chat.completions.create({
model: "qwen3-coder-next",
messages: [{ role: "user", content: "Read this screenshot of a failing dashboard, explain what the error message means, and suggest the code change that would fix it." }]
});
9 versions available
Qwen3-Coder-Next is an open-weight coding model from Alibaba Qwen, released under Apache 2.0 on February 3, 2026. It is built on Qwen3-Next-80B-A3B, a sparse Mixture-of-Experts model with hybrid attention that has 80B total parameters and 3B active per token. Qwen trained it for coding agents and repository-level work.
Qwen's model card says it runs in non-thinking mode only and does not produce thinking blocks, so a response starts with the answer or the tool call. Alibaba's API serves it with a 262,144-token context window, up to 204,800 input tokens, and up to 65,536 output tokens.
On RunAPI, call qwen3-coder-next through the OpenAI-compatible Chat Completions endpoint (/v1/chat/completions) with an OpenAI SDK pointed at https://runapi.ai/v1. It takes text input. Tools use the standard OpenAI tools format, and the model returns tool_calls in the response.
| Provider | Alibaba |
| Model ID | qwen3-coder-next |
| Modality | Text |
| Task types | Synchronous |
| API endpoint | /v1/chat/completions |
| /v1/responses |
| /v1/messages | |
| /v1beta/models/qwen3-coder-next:generateContent | |
| /v1beta/models/qwen3-coder-next:streamGenerateContent | |
| Billing unit | 1K tokens |
| Catalog status | Retired |
Sign up for free and create an API key for qwen3-coder-next from the dashboard.
POST to /v1/chat/completions with the qwen3-coder-next model slug and your parameters.
Read the completed qwen3-coder-next response directly from the endpoint.
Exposes 1 public endpoint(s): chat_completion.
Metered by 1K tokens with no subscription requirement.
No request parameters are published for this endpoint.
Answer customer questions from a private knowledge base, reducing ticket volume.
Draft contract summaries and flag key clauses for attorney review.
Auto-generate unit tests, code reviews, and refactoring suggestions in CI.
Coding agents and repository-level work, such as reading a codebase, editing several files, and calling tools in a loop. Qwen reports SWE-Bench-Pro results comparable to models with 10 to 20 times more active parameters.
Yes. Send tools in the OpenAI format on Chat Completions and the model returns tool_calls. Qwen's model card describes tool calling as one of the model's main strengths.
No. Qwen's model card says it supports non-thinking mode only and does not generate thinking blocks. If a task needs a reasoning step, use a Qwen3.5 or Qwen3.6 model, which have a thinking mode.
3B of its 80B parameters are active for each token. The model is built on Qwen3-Next-80B-A3B, which combines a sparse Mixture-of-Experts design with hybrid attention.
Pass the model ID shown in the quickstart.
Per-key rate limits scale with your usage tier. The pricing page shows current limits. If you need higher throughput, contact support to discuss tier upgrades.
Yes. Variant is a parameter in the request. Switch by changing the model ID — no code changes, no re-authentication, no separate billing setup. All variants share the same API key and request shape.
Where streaming is available, RunAPI streams end-to-end. LLM models support token-level streaming. Media models use async task polling or webhook callbacks for result delivery.
Open an issue on the public GitHub repo or email support at [email protected]. Include the task ID and model ID so the team can investigate the specific generation.
No. Your RunAPI API key is enough to access this variant and every other model in the catalog. You do not need accounts with the underlying provider.
We're here to help with enterprise setup, integrations, and technical questions.
Contact Us