Qwen 3.8 27B

CodeVisionReasoningWeb searchFunction calling
Advertised as qwen-3-8-27bqwen-3.8-27b
Quick reference
Qwen 3.8 27B — TLDR
  • 🏢 Alibaba's Qwen team; dense 27B vision-language model, Apache 2.0 licensed.
  • 📏 Native 262,144-token context window, extensible further via YaRN scaling.
  • 👁️ Native image and video understanding built into the same model.
  • 🧠 Flexible thinking control: reasoning can be turned on or off.
  • 🔧 Focused on coding, professional work, research and agentic tasks.
  • ⚡ Served here in FP8; official FP8 weights published by Qwen.
  • 🆕 Successor to the 27B dense model of the Qwen 3.6 line.
  • 📚 Roughly 496K Hugging Face downloads at this catalog snapshot.
💰 Best price on Antseed
$0.0050 / $0.025−97%
per 1M · cheapest in / out
🐜 Sellers
7
advertising on Antseed
🔬 Model checks
2 of 2 sellers pass
0 failed · 7 Nov · details →
📏 Context
262K tokens
Provider

Alibaba Group is a Chinese multinational technology company founded in 1999 and headquartered in Hangzhou, Zhejiang. Originally built around e-commerce and cloud computing, Alibaba has become one of the most prolific contributors to open-weight AI research, developing the Qwen…

Explore 51 more models by Alibaba Group →
About this model

Qwen 3.8 27B is the compact dense member of Alibaba's Qwen 3.8 generation, released in 2026 under the Apache 2.0 license. The published model card describes it as a natively multimodal causal language model: a single set of weights handles text alongside image and video inputs, with a native context window of 262,144 tokens that can be extended further using YaRN-style rope scaling. Qwen also publishes an official FP8 checkpoint, which is the quantization served on this catalog, here with reasoning, vision, function calling and web search enabled.

Relative to its same-family predecessor Qwen 3.6 27B, the model keeps the same 27-billion-parameter dense footprint but is positioned by Qwen around stronger coding, professional and research work, and long-horizon agentic execution, together with flexible thinking control — reasoning can be enabled or disabled per request rather than requiring separate instruct and thinking checkpoints, as earlier Qwen releases such as Qwen 3 235B A22B Thinking 2507 did. Independent third-party benchmark results are not cited here.

Within the current lineup it sits below the flagship Qwen 3.8 2.4T mixture-of-experts model and the hosted Qwen 3.8 Max, while offering native vision that smaller dense builds like Qwen 3.5 9B did not carry in this catalog. That makes it a practical choice when you want multimodal input, tool use and a very long context at a size that fits a single accelerator.

View source on GitHub ↗View model card on HuggingFace ↗
Sources
huggingface.coQwen/Qwen3.8-27B · Hugging Face· huggingface.co

This About section is AI-generated from public sources via VeniceStats + Venice inference, with no human editing. It may contain inaccuracies.

Usage on Antseed · Qwen 3.8 27B
Tokens served
5.40M
input + output
Requests
2,794
settled calls
Buyers
14
distinct, on this model
Sellers used
9
of 7 advertising
Settled
$0.42
gross USDC, this model

Daily usage · Qwen 3.8 27B · Organic sellers

Top sellers · Qwen 3.8 27B · Organic

Sellers serving Qwen 3.8 27B (7)compare on the network explorer →model checks →
SellerHealthRep↓SalesTokensRoutingInput $/MCached
$/M
Output $/MSave1st tokentok/s

"Best price" and the seller table are live Antseed catalog data (advertised $/1M tokens — or $ per generated image for unit-billed image models — not settled amounts). Reputation = buyer trust score (0-100, the Antseed SDK's own formula). "Routing" = the SDK's default buyer routing (what the VPR desktop app ships with): a trust ≥ 60 gate on the effective reputation, then cheapest-first among routable sellers; live failover state (per-peer cooldowns) is buyer-side runtime and not included. Model knowledge (TLDR, provider, About) via the VeniceStats enrichment layer. Advertised catalog, not the model used in any specific purchase. "Usage on Antseed" counts only settlements whose buyers share the per-model split on-chain (metadata v2/v3, opt-in), so every usage figure is a lower bound.