Grok
Stream meeting audio to a Grok Voice Agent and play its responses back into the meeting.
Recall.ai connects to xAI's Voice API over WebSocket. Configure the voice, instructions, and provider-hosted tools in the bot request; Recall.ai handles meeting audio, playback, and interruptions.
Setup
1. Get an xAI API key
Create an API key in the xAI console with access to the Voice API. The integration starts a session from the settings in your request, so you do not need a saved agent ID.
2. Add your credentials to Recall.ai
Open Agents → Grok in the Recall region where you create bots:
Select the workspace used by your Recall API key, then save your xAI key. This key is shared with Grok transcription. Changes apply to new connections.
Quickstart
Call Create Bot with your meeting URL and session settings.
We recommend setting the relevant meeting platform in variant to web_4_core when pairing this audio agent with a video provider or a kind: "webpage" source. See bot sizing guidance.
{
"meeting_url": "MEETING_URL",
"variant": {
"zoom": "web_4_core",
"google_meet": "web_4_core",
"microsoft_teams": "web_4_core",
"webex": "web_4_core"
},
"output_media": {
"audio": {
"kind": "grok",
"config": {
"session": {
"voice": "eve",
"instructions": "You are a helpful meeting assistant. Keep spoken replies brief.",
"turn_detection": {
"type": "server_vad"
}
}
}
}
}
}Once the bot joins, Recall.ai connects to Grok and sends the meeting audio mix. Grok detects when a participant finishes speaking and generates a reply.
For recording the agent's voice, see Recording meeting agents. For response controls, see the Meeting agents FAQ.
Additional configurations
The output_media.audio.config object supports:
| Field | Required | Description |
|---|---|---|
session | Yes | The session object from xAI's session.update schema. Supply the inner object; Recall.ai creates the surrounding message. An empty object uses the integration's defaults. |
model | No | Model sent in the WebSocket connection's model parameter. See xAI's supported voice models. Defaults to grok-voice-latest. Use 1–128 ASCII letters, digits, underscores, periods, or hyphens. |
The xAI API key is read from saved credentials. api_key and credential_id are not accepted in this config.
Configure voice, instructions, and tools
Common fields inside session include:
| Field | Description |
|---|---|
voice | Voice supported by xAI. Defaults to eve. |
instructions | Instructions for the conversation. |
turn_detection | Must use type: "server_vad". Defaults to that setting when omitted. create_response and interrupt_response must not be false. |
tools | Tools supported and executed by xAI, such as web search or remote MCP tools. Recall.ai adds bot context headers to MCP tools as described below. |
For example, this config enables web search:
{
"model": "grok-voice-latest",
"session": {
"voice": "eve",
"instructions": "You are a meeting assistant. Use web search when asked for current information, and keep replies brief.",
"tools": [
{
"type": "web_search"
}
]
}
}See xAI's Speech to Speech documentation for supported voices, tools, and session options. Supply the session object directly; Recall.ai creates the session.update message.
Use Recall bot context in tools
For each entry in session.tools with type: "mcp", Recall.ai automatically adds these values to the tool's headers object. xAI sends them to your MCP server:
| Header | Value |
|---|---|
X-Recall-Bot-Id | The Recall bot's ID, matching the ID returned by Create Bot. |
X-Recall-Api-Base-Url | The bot's regional Recall API base URL, without an API version path, such as https://us-west-2.recall.ai. |
Your MCP server can use these values to act on the meeting bot. It still needs your Recall API key to authenticate Recall API requests; the context contains no Recall credentials.
These header names are reserved. Recall.ai replaces supplied values regardless of capitalization, preserving other headers and MCP settings such as authorization and allowed_tools. This applies to every configured MCP tool; web-search and client-side function definitions are unchanged.
Append the endpoint's versioned path to this base URL when making Recall API requests.
Add a camera or avatar
Grok is supported under output_media.audio. You can combine it with an independent camera or screenshare source. When audio is configured, the meeting audio mix goes only to the audio agent; camera and screenshare sources do not receive it.
To use an automatic avatar, combine output_media.audio with automatic_video_output, leaving output_media.camera and output_media.screenshare absent.
FAQ
Can I turn off automatic replies or interruptions?
This integration requires automatic replies and interruptions through server VAD. turn_detection: null, other turn-detection modes, and setting create_response or interrupt_response to false are not supported.
Where should I implement tool calls?
Use xAI's server-side tools or expose your application through a remote MCP server supported by xAI. Recall.ai does not execute client-side functions: it returns an unsupported-function result and emits a customer-visible warning so the conversation can continue.
To add chat messages, screensharing, and a leave action, see Add meeting tools.
Updated about 2 hours ago
