xAI API and Dome

1. 01

   Add the connections

   The provider id is xai. Dome uses https://api.x.ai/v1 and xAI's own model ids.

   $ dome models add grok-4-7-xai \
     --provider xai \
     --model grok-4.7 \
     --api-key "$XAI_API_KEY" \
     --attributes '{"use":"internal"}' \
     --gateway prod-gateway
    
   $ dome models add grok-4-6-xai \
     --provider xai \
     --model grok-4.6 \
     --api-key "$XAI_API_KEY" \
     --attributes '{"use":"internal"}' \
     --gateway prod-gateway

2. 02

   Pool them

   4.7 is tried first and 4.6 next. Agents name the pool, grok-4.7.

   $ dome models pool create grok-4.7 \
     --failover-max all --gateway prod-gateway
    
   $ dome models pool member add grok-4.7 grok-4-7-xai --priority 0
   $ dome models pool member add grok-4.7 grok-4-6-xai --priority 1

3. 03

   Point your agent at the Gateway

   Use any client that speaks Chat Completions. It sends the agent's Dome key where the xAI key used to go.

   from openai import OpenAI
    
   client = OpenAI(base_url=f"{GATEWAY_URL}/v1", api_key=DOME_AGENT_KEY)
   client.chat.completions.create(
       model="grok-4.7",
       messages=[{"role": "user", "content": "Summarize this incident report."}],
   )

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

forbid (principal, action == Dome::Action::"llm:invoke", resource is Dome::LLMModel)
when { resource has use && resource.use == "internal" };