Quickstart: Grok Bot

Grok Bot connects the same way as Meta Muse: you ask for the connection in a chat, Grok Bot opens a Guardyx sign-in, and you pick the agent on a consent screen. There’s no API key, client ID, or config file to copy.

1. In the Guardyx portal, open My Agents and choose Connect new agent.
2. Under Which app will you chat with?, pick Grok Bot (A Grok chat agent, connected from a chat).
3. Choose the apps it should use and what it may do, then connect your accounts.
4. On the last step, copy the chat prompt. Leave the page open. Its status turns to Connected once Grok Bot reaches Guardyx.

1. Send the prompt from the portal in a Grok Bot chat. It reads like this:

   Connect Grok Bot to the Guardyx MCP server at https://app.guardyx.ai/v1/mcp. Connect by signing in to Guardyx (OAuth), not with an API key.

   Keep the second sentence. If you only ask Grok Bot to connect, it reaches for an API key.

2. Grok Bot opens a Guardyx sign-in window. The window names the app Cursor cloud agent, not Grok Bot. That is expected: Grok Bot’s MCP connection runs on Cursor’s cloud agent. Sign in.

3. On the consent screen, choose the agent you created and select Allow. Only Grok Bot agents are listed. Grok Bot registered itself, so the screen also asks you to confirm that you started this connection. If someone sent you the link, cancel.

4. Back in the portal, the status changes to Connected.

1. Ask Grok Bot for something that uses one of your connected apps, for example “What’s on my calendar today?”

   If Grok Bot answers that no calendar is connected, it didn’t look in Guardyx. Your apps sit behind Guardyx’s search tool, so Grok Bot doesn’t see them on its own. Name Guardyx in the request: “Use Guardyx to check what’s on my calendar today.”

2. Open Runs in Guardyx. The call is there, with its inputs, the policy decision, and the outcome.

3. Ask for something your policy holds for review. Grok Bot waits while the request is in Approvals.

Grok Bot sees three Guardyx tools: guardyx_search_tools, guardyx_describe_tool, and guardyx_execute_tool. That is expected. Grok Bot finds your toolbox’s tools by searching through them.

What you see	What to do
Grok Bot asks for an API key	Don’t create one. Ask it to connect by signing in to Guardyx.
“redirect_uri is not allowed for registration without sign-in”	Grok Bot asked Guardyx for a sign-in callback Guardyx doesn’t recognize yet. Contact support with the time you tried. Don’t give Grok Bot an API key or a client secret instead.
The consent screen lists no agent	Create a Grok Bot agent first. The sign-in can’t be approved for any other kind of agent.
“This agent has no bound tools”	Bind a toolbox to the agent on its page in Guardyx.
A tool shows not_connected	Connect that app’s account from the agent page, then retry.

This guide is for Grok Bot. A bot you wrote yourself on the xAI API connects with a key instead:

1. In Connect new agent, pick Custom MCP (Another app that supports custom connections) and copy the API key (gx_live_…) from the last step.
2. In your code, point the xAI remote MCP tool at https://app.guardyx.ai/v1/mcp and send the key in its headers field (extra_headers in the xai-sdk) as X-API-Key. Read the key from the environment, never from source control.

Every AI action passes through Guardyx. Each tool call Grok Bot makes is checked against your policy, sensitive ones wait for your approval, and each request, decision, and outcome is recorded in a tamper-evident run trace.