TestingOps.ai

AI model providers · Model provider

xAI Grok and TestingOps: test agents on your own xAI key

Add an xAI API key and the agents on your TestingOps projects run Grok on your own xAI account, with two limits worth knowing first.

  • Model provider
  • Available with limits
Request a demo xAI API documentation
Connection
Model provider
Writes back
Nothing, only model requests
Last checked
7 Nov 2026

In short

xAI Grok and TestingOps in short

The xAI connection lets your organisation run TestingOps agents on Grok with its own xAI API key, which the customer admin saves under Integrations → AI models.

While xAI (Grok) is your first provider, your agents switch to the Grok adapter and use that key on all of your projects.

Grok is available only with your own key, not as a platform model, and agents running on Grok do not receive MCP tools.

What it does

What it does for your testing

  1. 1

    Agents on Grok, billed by xAI

    Input
    Your xAI API key, first under Your providers
    TestingOps
    Switches your organisation's agents to the Grok adapter and attaches the key to all of your projects as XAI_API_KEY
    Output
    Agent runs on your projects that use Grok with your key
  2. 2

    A tested key and model

    Input
    The saved key and the Model field
    TestingOps
    Test connection sends one short request to xAI's OpenAI-compatible API at api.x.ai
    Output
    A Reachable or Unreachable mark before agents depend on it
  3. 3

    The same account on RunningOps

    Input
    An organisation linked to RunningOps
    TestingOps
    Copies the key there as an OpenAI-compatible provider pointing at api.x.ai
    Output
    Grok set up on the execution side without typing the key twice

Step by step

How it works

  1. Save the xAI keyThe customer admin picks xAI (Grok) under Add a model provider in Integrations → AI models, pastes the key, optionally enters a model and saves.
  2. Attached to your projectsThe key is stored encrypted and attached to every project of your organisation as XAI_API_KEY.
  3. Grok at the top drives the agentsWhen xAI (Grok) is marked Default · drives agents, your agents switch to the Grok adapter at their next run. Before a run, TestingOps checks the key against xAI and stops the run if xAI rejects it.
  4. No MCP tools on Grok runsThe Grok adapter is not wired for MCP. Tools connected under Extra tools your agents may use are not passed to agents while they run on Grok.

TestingOps does not offer Grok on the platform's own account: it is available only with a key of your own.

Connect

Setup

  1. Create an API key in your xAI account.
  2. In TestingOps, as customer admin, open Integrations → AI models and pick xAI (Grok) under Add a model provider.
  3. Paste the key into API key, enter a Model if agents should use one Grok model, select Save and then Test connection.
  4. If xAI (Grok) is not marked Default · drives agents, move it to the top under Your providers and select Save order.

Documentation: xAI API documentation

Where you connect it in TestingOps: Integrations → AI models → Your providers → xAI Grok

Use cases

Use cases

Try Grok on real test work

Trigger
Your team wants to see how Grok handles your projects' test design
Uses
Your xAI key, moved to the top of Your providers for the trial
Agent activity
Agents write and review cases on Grok from their next run
Result
Real output on your own projects to compare with your previous provider
Condition
Move the previous provider back to the top to switch back

Keep AI spend on your xAI account

Trigger
Your company already pays for xAI usage
Uses
Your xAI API key
Agent activity
Agents working on your projects run on the Grok adapter with that key
Result
Agent usage billed by xAI to your account

Design on Grok, execute on RunningOps

Trigger
Your cases run on RunningOps and you want Grok for test design
Uses
Your xAI key and the RunningOps link
Agent activity
TestingOps agents use Grok; the key is also copied to your RunningOps organisation
Result
One xAI account on both sides
Condition
Grok agents work without MCP tools

Capabilities

Capabilities and limits

What is read

  • Grok's responses while agents work on your projects
  • xAI's model list for your key, for the check before a run

What is produced

  • Agent runs on your projects that use Grok with your key
  • A Reachable or Unreachable mark after Test connection

Where it can write

Nothing in your xAI account; only model requests are sent with your key.

How it connects

xAI's API with your key: agents through the Grok adapter, the connection test through the OpenAI-compatible API at api.x.ai. A linked RunningOps organisation gets the key as an OpenAI-compatible provider.

Account and permissions

  • An xAI API key
  • Customer admin rights in TestingOps, or a company admin of the TestingOps workspace managing keys for your organisation

Limits

  • Agents running on Grok receive no MCP tools, including tools connected under Extra tools your agents may use
  • Only with your own key: TestingOps does not offer Grok on the platform's account
  • One key per organisation for all of its projects, and not every TestingOps AI feature uses it

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A team wants to compare Grok with its current provider on real work. The customer admin adds the team's xAI key, moves xAI (Grok) to the top of Your providers and lets the agents write the next sprint's cases on Grok.

Because Grok agents do not receive MCP tools, the team runs the trial on design work that does not need a connected tool such as Datadog, and decides after the sprint which provider stays at the top.

Frequently asked questions

Can agents on Grok use MCP tools?

No. The Grok adapter is not wired for MCP, so tools you connect under Integrations → API & MCP are not available to agents while they run on Grok.

Can we use Grok without our own xAI key?

No. TestingOps does not offer Grok on the platform's account. Without your key, your agents follow your other providers or, if your package allows it, the platform's models.

Is the xAI key checked before a run?

Yes. Before a run on your key, TestingOps asks xAI for its model list with the key. If xAI rejects it, the run does not start and the task shows xAI's message.

Which model do the agents use?

The model you enter in Model. If you leave it empty, agents that switch to Grok get a default Grok model.

Does RunningOps get the key too?

If your organisation is linked to RunningOps, TestingOps copies the key there as an OpenAI-compatible provider pointing at api.x.ai.

Next step

Request a demo to try your own xAI key on a test project before moving your agents to Grok.

Request a demoMore ai models integrations