qwen1.5_moe_a2.7b_chat_w_fp6_e3m2_a_fp6_e3m2
qwen1.5_moe_a2.7b_chat_w_fp6_e3m2_a_fp6_e3m2 (fxmarty, 2025) is an chat model. qwen1.5_moe_a2.7b_chat_w_fp6_e3m2_a_fp6_e3m2 is an open-weights chat model.
by fxmarty
Best for
- low-latency chat and routing
- request routing and triage
- text classification
Ways to use qwen1.5_moe_a2.7b_chat_w_fp6_e3m2_a_fp6_e3m2 in osFoundry
Connect with your own key (BYOK)
Open the key dialog and paste your fxmarty API key. osFoundry discovers qwen1.5_moe_a2.7b_chat_w_fp6_e3m2_a_fp6_e3m2 automatically — assign it to a Maestro role (router, direct, orchestrator, or fallback) in the Pipeline tab and it is live in every chat. Your key, your provider account — no token markup.
Deploy a dedicated endpoint
qwen1.5_moe_a2.7b_chat_w_fp6_e3m2_a_fp6_e3m2 is open-weights — run it locally for free, or deploy a dedicated GPU endpoint in your workspace for reserved capacity with no rate limits.
Use it in a Room App
Room Apps declare AI features in their manifest, then call them with invokeAI:
import { invokeAI } from '@osfoundry/app-sdk'
// 'summarize' is an AI feature declared in your app manifest.
const result = await invokeAI('summarize', userText)
Call it from your own apps
Once a model is wired into your workspace you can host it as an API and reach it from your own services, scripts, or CI — outside osFoundry.
qwen1.5_moe_a2.7b_chat_w_fp6_e3m2_a_fp6_e3m2 vs similar models
Licence
Unspecified — Licence terms not specified — verify the upstream model card before commercial use.
Check upstream documentation.
Frequently asked about qwen1.5_moe_a2.7b_chat_w_fp6_e3m2_a_fp6_e3m2
Is qwen1.5_moe_a2.7b_chat_w_fp6_e3m2_a_fp6_e3m2 free to use?
qwen1.5_moe_a2.7b_chat_w_fp6_e3m2_a_fp6_e3m2 is free to run locally on your own hardware. Hosted access through osFoundry is metered (input Free (local), output Free (local)). You can switch between local and hosted at any time.
Can I use qwen1.5_moe_a2.7b_chat_w_fp6_e3m2_a_fp6_e3m2 commercially?
Commercial use is allowed with conditions. Licence terms not specified — verify the upstream model card before commercial use. Check upstream documentation.
Can I run qwen1.5_moe_a2.7b_chat_w_fp6_e3m2_a_fp6_e3m2 locally?
Yes. qwen1.5_moe_a2.7b_chat_w_fp6_e3m2_a_fp6_e3m2 is open-weights and runs locally on a workstation GPU. osFoundry's local runtime handles model loading, quantisation, and routing.
What is qwen1.5_moe_a2.7b_chat_w_fp6_e3m2_a_fp6_e3m2 best at?
qwen1.5_moe_a2.7b_chat_w_fp6_e3m2_a_fp6_e3m2 is well-suited to low-latency chat and routing, request routing and triage, text classification.
How do I use qwen1.5_moe_a2.7b_chat_w_fp6_e3m2_a_fp6_e3m2 in osFoundry?
Paste your fxmarty API key in the key dialog (or deploy the open weights for self-hostable models), assign qwen1.5_moe_a2.7b_chat_w_fp6_e3m2_a_fp6_e3m2 to a Maestro role in the Pipeline tab, then use it in chat, Room Apps via invokeAI, or your own apps.
Published by fxmarty on July 11, 2025. Source: https://huggingface.co/fxmarty/qwen1.5_moe_a2.7b_chat_w_fp6_e3m2_a_fp6_e3m2