E2EE Qwen 3.6 27B FP8
e2ee-qwen3-6-27b- 🔒 Runs in a TEE with verifiable hardware attestation
- 🆕 Dense member of Alibaba's Qwen3.6 family
- 📏 Context window around 256K tokens
- 🔧 FP8 quantization roughly halves the weight footprint
- 🧠 Reasoning, agentic coding, and function-calling focused
- 🌐 Venice build surfaces web-search capability
- 📚 Apache 2.0 license permits commercial use and fine-tuning
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 33 more models by Alibaba Group →Qwen 3.6 27B FP8 is Venice's confidential-computing deployment of Alibaba's Qwen3.6-27B, a dense text model in the Qwen3.6 family.[1] It runs inside a Trusted Execution Environment, exposing hardware attestation evidence so users can independently verify enclave identity and configuration. The Venice build advertises reasoning, code-optimized generation, function-calling, and web-search capabilities, with a context window of roughly 256K tokens. The model is distributed under Apache 2.0, permitting commercial use, fine-tuning, and redistribution.[1]
The FP8 checkpoint quantizes the weights to 8-bit floating point, a path Alibaba publishes alongside its BF16 release to reduce the weight footprint for cost-sensitive deployment.[2] This mirrors the FP8 variant Alibaba offered for the preceding Qwen3.5-27B, so the two generations share the same deployment pattern.[8]
Compared with its same-family sibling [[sibling:e2ee-qwen3-6-35b-a3b|Qwen 3.6 35B A3B FP8]], a mixture-of-experts model with 35B total and roughly 3B active parameters, this 27B checkpoint is a dense architecture — trading MoE sparsity for a single dense design at a smaller total parameter count. Both are offered here in FP8 inside the same TEE-backed serving environment.
For prospective users, the practical distinction is architectural and operational rather than a ranking claim: the dense 27B activates all parameters per token, while the A3B sibling activates only a fraction of its larger expert pool. Alibaba's Hugging Face model cards remain the authoritative reference for the precise configuration and supported features.[1][2]
This About section is AI-generated from public sources via VeniceStats + Venice inference, with no human editing. It may contain inaccuracies.
| Seller | Reputation↓ | Routing | Input $/M | Cached $/M | Output $/M | Categories | API |
|---|---|---|---|---|---|---|---|
| Fire Ant 🔥🐜 0xbe05…bc5d | 37 | gated | $0.3114 | $0.1525 | $3.0866 | base-usdc,chat,code,coding,github,json,low-cost,math,monitored,openai-compatible,qwen,reasoning,response-auth,surplus,tasks,tee,value,verified,vision | — |
| antseed-opal-badger-2580 0xc85d…2580 | 2 | gated | $0.173 | $0.173 | $1.73 | chat | openai-chat-completions |
"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 = on-chain trust (0-100). "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.