Endpoint coverage
Exposes 1 public endpoint(s): chat_completion.
Dense open-weight Qwen3.5 vision model; 256K context, hybrid thinking; OpenAI-compatible API
# Base URL
https://runapi.ai
# Endpoints
POST /v1/chat/completions
POST /v1/responses
POST /v1/messages
POST /v1beta/models/qwen3.5-27b:generateContent
POST /v1beta/models/qwen3.5-27b:streamGenerateContent
curl https://runapi.ai/v1/chat/completions \
-H "Authorization: Bearer $RUNAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "qwen3.5-27b",
"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.5-27b",
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.5-27b",
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.5-27B is a dense native vision-language model from Alibaba's Qwen3.5 Medium series, released with open weights under Apache 2.0 on February 24, 2026. It uses linear attention for fast responses, and Alibaba rates its overall performance as comparable to Qwen3.5-122B-A10B.
It is a hybrid model with thinking on by default, a 262,144-token context window, and up to 65,536 output tokens. Alibaba lists function calling and structured outputs as supported.
On RunAPI, call qwen3.5-27b through the OpenAI-compatible Chat Completions endpoint (/v1/chat/completions) with an OpenAI SDK pointed at https://runapi.ai/v1. Images go in image_url parts inside messages[].content[], and tools use the standard OpenAI tools format.
Pick any model and generate in seconds.
| Provider | Alibaba |
| Model ID | qwen3.5-27b |
| Modality | Text |
| Task types | Synchronous |
| API endpoint | /v1/chat/completions |
| /v1/responses |
| /v1/messages | |
| /v1beta/models/qwen3.5-27b:generateContent | |
| /v1beta/models/qwen3.5-27b:streamGenerateContent | |
| Billing unit | 1K tokens |
| Catalog status | Operational |
Sign up for free and create an API key for qwen3.5-27b from the dashboard.
POST to /v1/chat/completions with the qwen3.5-27b model slug and your parameters.
Read the completed qwen3.5-27b 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.
Verified customer feedback is not available for this model yet.
Dense. All 27B parameters run for every token, unlike the Qwen3.5 MoE models such as Qwen3.5-35B-A3B, which activates 3B parameters per token.
Alibaba rates the two as comparable overall. Both have a 262,144-token context window, image input, hybrid thinking, and function calling.
Qwen3.6-27B is built on Qwen3.5-27B. Qwen reports stronger agentic coding, STEM reasoning, OCR, and video understanding for the 3.6 model. Keep Qwen3.5-27B for prompts and evaluations already tuned on it.
Yes. Send image_url parts with the text in a Chat Completions request. Alibaba also lists video input; video requests are not verified on RunAPI.
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