Qwen and Dome

1. 01

   Connect Together AI

   Tag it family: qwen. The Together key is Dome's to hold; the coding agent gets a Dome key.

   $ dome models add qwen-together \
     --provider together \
     --model Qwen/Qwen3.8-2.4T-A95B \
     --api-key "$TOGETHER_API_KEY" \
     --attributes '{"family":"qwen"}' \
     --gateway prod-gateway

2. 02

   Connect DeepInfra

   DeepInfra serves the same weights under the same id.

   $ dome models add qwen-deepinfra \
     --provider deepinfra \
     --model Qwen/Qwen3.8-2.4T-A95B \
     --api-key "$DEEPINFRA_API_KEY" \
     --attributes '{"family":"qwen"}' \
     --gateway prod-gateway

3. 03

   Pool them for failover

   Same id on both hosts, so the pool is a straight priority list: Together, then DeepInfra.

   $ dome models pool create qwen3.8 \
     --failover-max all --gateway prod-gateway
    
   $ dome models pool member add qwen3.8 qwen-together --priority 0
   $ dome models pool member add qwen3.8 qwen-deepinfra --priority 1

4. 04

   Point your agent at the Gateway

   The code assistant's OpenAI client sends qwen3.8 to the Gateway with its own key.

   from openai import OpenAI
    
   client = OpenAI(base_url=f"{GATEWAY_URL}/v1", api_key=DOME_AGENT_KEY)
   client.chat.completions.create(
       model="qwen3.8",
       messages=[{"role": "user", "content": "Write unit tests for parse_invoice()."}],
   )

5. 05

   Cap spend per agent

   Each agent's budget follows it across pools, so a second model doesn't open a second budget.

   $ dome quotas set --subject agent --agent migration-agent \
     --dimension llm --unit provider_usd --limit 150 --window monthly

Commands and rules tested against a Dome workspace on October 1, 2026. For anything about Qwen itself, see Alibaba's documentation.

forbid (principal, action == Dome::Action::"llm:invoke", resource is Dome::LLMModel)
unless { resource has family && resource.family == "qwen" };