xAI

The bundled grok web-search provider uses XAI_API_KEY too:

openclaw config set tools.web.search.provider grok

The bundled xai plugin registers video generation through the shared video_generate tool.

• Default video model: xai/grok-imagine-video
• Modes: text-to-video, image-to-video, reference-image generation, remote video edit, and remote video extension
• Aspect ratios: 1:1, 16:9, 9:16, 4:3, 3:4, 3:2, 2:3
• Resolutions: 480P, 720P
• Duration: 1-15 seconds for generation/image-to-video, 1-10 seconds when using reference_image roles, 2-10 seconds for extension
• Reference-image generation: set imageRoles to reference_image for every supplied image; xAI accepts up to 7 such images

To use xAI as the default video provider:

{
  agents: {
    defaults: {
      videoGenerationModel: {
        primary: "xai/grok-imagine-video",
      },
    },
  },
}

The bundled xai plugin registers image generation through the shared image_generate tool.

• Default image model: xai/grok-imagine-image
• Additional model: xai/grok-imagine-image-pro
• Modes: text-to-image and reference-image edit
• Reference inputs: one image or up to five images
• Aspect ratios: 1:1, 16:9, 9:16, 4:3, 3:4, 2:3, 3:2
• Resolutions: 1K, 2K
• Count: up to 4 images

OpenClaw asks xAI for b64_json image responses so generated media can be stored and delivered through the normal channel attachment path. Local reference images are converted to data URLs; remote http(s) references are passed through.

To use xAI as the default image provider:

{
  agents: {
    defaults: {
      imageGenerationModel: {
        primary: "xai/grok-imagine-image",
      },
    },
  },
}

The bundled xai plugin registers text-to-speech through the shared tts provider surface.

• Voices: eve, ara, rex, sal, leo, una
• Default voice: eve
• Formats: mp3, wav, pcm, mulaw, alaw
• Language: BCP-47 code or auto
• Speed: provider-native speed override
• Native Opus voice-note format is not supported

To use xAI as the default TTS provider:

{
  messages: {
    tts: {
      provider: "xai",
      providers: {
        xai: {
          voiceId: "eve",
        },
      },
    },
  },
}

The bundled xai plugin registers batch speech-to-text through OpenClaw's media-understanding transcription surface.

• Default model: grok-stt
• Endpoint: xAI REST /v1/stt
• Input path: multipart audio file upload
• Supported by OpenClaw wherever inbound audio transcription uses tools.media.audio, including Discord voice-channel segments and channel audio attachments

To force xAI for inbound audio transcription:

{
  tools: {
    media: {
      audio: {
        models: [
          {
            type: "provider",
            provider: "xai",
            model: "grok-stt",
          },
        ],
      },
    },
  },
}

Language can be supplied through the shared audio media config or per-call transcription request. Prompt hints are accepted by the shared OpenClaw surface, but the xAI REST STT integration only forwards file, model, and language because those map cleanly to the current public xAI endpoint.

The bundled xai plugin also registers a realtime transcription provider for live voice-call audio.

• Endpoint: xAI WebSocket wss://api.x.ai/v1/stt
• Default encoding: mulaw
• Default sample rate: 8000
• Default endpointing: 800ms
• Interim transcripts: enabled by default

Voice Call's Twilio media stream sends G.711 µ-law audio frames, so the xAI provider can forward those frames directly without transcoding:

{
  plugins: {
    entries: {
      "voice-call": {
        config: {
          streaming: {
            enabled: true,
            provider: "xai",
            providers: {
              xai: {
                apiKey: "${XAI_API_KEY}",
                endpointingMs: 800,
                language: "en",
              },
            },
          },
        },
      },
    },
  },
}

Provider-owned config lives under plugins.entries.voice-call.config.streaming.providers.xai. Supported keys are apiKey, baseUrl, sampleRate, encoding (pcm, mulaw, or alaw), interimResults, endpointingMs, and language.

The bundled xAI plugin exposes x_search as an OpenClaw tool for searching X (formerly Twitter) content via Grok.

Config path: plugins.entries.xai.config.xSearch

{
  plugins: {
    entries: {
      xai: {
        config: {
          xSearch: {
            enabled: true,
            model: "grok-4-1-fast",
            baseUrl: "https://api.x.ai/v1",
            inlineCitations: true,
          },
        },
      },
    },
  },
}

The bundled xAI plugin exposes code_execution as an OpenClaw tool for remote code execution in xAI's sandbox environment.

Config path: plugins.entries.xai.config.codeExecution

{
  plugins: {
    entries: {
      xai: {
        config: {
          codeExecution: {
            enabled: true,
            model: "grok-4-1-fast",
          },
        },
      },
    },
  },
}

• Auth is API-key only today. There is no xAI OAuth or device-code flow in OpenClaw yet.
• grok-4.20-multi-agent-experimental-beta-0304 is not supported on the normal xAI provider path because it requires a different upstream API surface than the standard OpenClaw xAI transport.
• xAI Realtime voice is not registered as an OpenClaw provider yet. It needs a different bidirectional voice session contract than batch STT or streaming transcription.
• xAI image quality, image mask, and extra native-only aspect ratios are not exposed until the shared image_generate tool has corresponding cross-provider controls.

• OpenClaw applies xAI-specific tool-schema and tool-call compatibility fixes automatically on the shared runner path.
• Native xAI requests default tool_stream: true. Set agents.defaults.models["xai/<model>"].params.tool_stream to false to disable it.
• The bundled xAI wrapper strips unsupported strict tool-schema flags and reasoning payload keys before sending native xAI requests.
• web_search, x_search, and code_execution are exposed as OpenClaw tools. OpenClaw enables the specific xAI built-in it needs inside each tool request instead of attaching all native tools to every chat turn.
• Grok web_search reads plugins.entries.xai.config.webSearch.baseUrl. x_search reads plugins.entries.xai.config.xSearch.baseUrl, then falls back to the Grok web-search base URL.
• x_search and code_execution are owned by the bundled xAI plugin rather than hardcoded into the core model runtime.
• code_execution is remote xAI sandbox execution, not local exec.