Loading model details...
Fetching the latest models and pricing from the API.
Loading model details...
Fetching the latest models and pricing from the API.
Qwen3-Coder-Next is an open-weight MoE language model designed specifically for coding agents. With only 3B activated parameters out of 79.7B total, it achieves performance comparable to models with 10–20x more active parameters. It features a hybrid Gated Attention + Gated DeltaNet MoE architecture with 512 experts (10 active per token), 262K native context, and achieves 74.2% on SWE-Bench Verified — making it highly cost-effective for production agent deployment.
Input <= 32k
Save 20%/ 1M input tokens
/ 1M output tokens
from openai import OpenAI
# Initialize the OpenAI client with Qubrid base URL
client = OpenAI(
base_url="https://qubrid.com/v1",
api_key="QUBRID_API_KEY",
)
response = client.chat.completions.create(
model="Qwen/Qwen3-Coder-Next",
messages=[
{
"role": "user",
"content": "Generate unit tests for a Node.js Express route handler, including edge cases."
}
],
max_tokens=8192,
temperature=1,
top_p=0.95,
stream=False
)
print(response.choices[0].message.content)from openai import OpenAI
# Initialize the OpenAI client with Qubrid base URL
client = OpenAI(
base_url="https://qubrid.com/v1",
api_key="QUBRID_API_KEY",
)
response = client.chat.completions.create(
model="Qwen/Qwen3-Coder-Next",
messages=[
{
"role": "user",
"content": "Generate unit tests for a Node.js Express route handler, including edge cases."
}
],
max_tokens=8192,
temperature=1,
top_p=0.95,
stream=False
)
print(response.choices[0].message.content)Example response
A chat completion API provides a standard way to send conversational input and receive model-generated text in a single request. Key benefits include: • Interoperability: any client can use HTTP with JSON request and response bodies. • Flexibility: system prompts, user messages, and parameters such as temperature and max tokens are easy to configure. • Observability: responses typically include token usage fields for cost and performance tracking. A typical integration sends a POST request with the model name and messages array, then reads the assistant message from the first choice in the response.
from openai import OpenAI
# Initialize the OpenAI client with Qubrid base URL
client = OpenAI(
base_url="https://qubrid.com/v1",
api_key="QUBRID_API_KEY",
)
response = client.chat.completions.create(
model="Qwen/Qwen3-Coder-Next",
messages=[
{
"role": "user",
"content": "Generate unit tests for a Node.js Express route handler, including edge cases."
}
],
max_tokens=8192,
temperature=1,
top_p=0.95,
stream=False
)
print(response.choices[0].message.content)from openai import OpenAI
# Initialize the OpenAI client with Qubrid base URL
client = OpenAI(
base_url="https://qubrid.com/v1",
api_key="QUBRID_API_KEY",
)
response = client.chat.completions.create(
model="Qwen/Qwen3-Coder-Next",
messages=[
{
"role": "user",
"content": "Generate unit tests for a Node.js Express route handler, including edge cases."
}
],
max_tokens=8192,
temperature=1,
top_p=0.95,
stream=False
)
print(response.choices[0].message.content)Example response
A chat completion API provides a standard way to send conversational input and receive model-generated text in a single request. Key benefits include: • Interoperability: any client can use HTTP with JSON request and response bodies. • Flexibility: system prompts, user messages, and parameters such as temperature and max tokens are easy to configure. • Observability: responses typically include token usage fields for cost and performance tracking. A typical integration sends a POST request with the model name and messages array, then reads the assistant message from the first choice in the response.
Streaming supported • Function calling supported • See all examples in Playground Open in Playground for streaming, files, and all parameters.
Open in Playground