How Grok Bot handles this
A Grok Bot keeps its context and works on a persistent cloud computer, so it can own a standing job such as keeping an eye on twelve client sites. You attach the xspeedhub plugin with @ in a chat and ask for a fleet action. For a picture of the whole workspace, the Bot calls run_benchmark with site set to "all", and the Hub measures each site's cached and uncached response time in turn, one second apart. For a change, such as clearing every cache after a shared template update, it calls purge_cache the same way. Either call returns one row per site with ok and either data or an error.
Routines are where a Bot differs from a chat. You tell the Bot when to run, what to check and what it must not do, it creates the routine and shows the next run, and background routines keep going while your laptop is closed. The Hub has no scheduler for agent prompts, so the timer is the Bot's. A routine that benchmarks every site each weekday is a good fit, because run_benchmark is a read. A routine that purges or toggles every site is not, because nobody is there to say yes, and xAI notes that even a Test run performs real work against connected tools.
When an action needs approval, Grok Bot offers Allow once, Always allow or Deny. Always allow saves a rule, and a rule on purge_cache covers its site: "all" form as well as a single site. Auto-review rules under Settings, General, Auto-review can force Ask first for named actions, and Ask first wins over an automatic allow when both match. xSpeed Hub has no confirmation step of its own, and its instruction to confirm once before a fleet-wide purge, toggle, settings or preloader call is guidance to the model that does not name optimize_site.
Set up Grok Bot once
Already connected? Skip to the prompts. Alternatives and troubleshooting are on the Grok Bot guide.
1Put your sites in xSpeed Hub
Sign in at app.xspeedcache.com with Google or email; the Hub is free and has no site cap. Then connect each WordPress site from its own dashboard: click Connect Hub in the xSpeed Cache top bar, then Connect via xSpeed Hub. Each site needs the free xSpeed Cache plugin.
2Ask your Bot to add xSpeed Hub
In a chat with your Bot, ask it to add a custom remote HTTPS MCP server with this URL. xAI says a plugin you add from your own chat is personal and account-wide, so every Bot on your account can use it. When the browser opens, approve access on the xSpeed Hub page.
Add a custom remote HTTPS MCP server called xspeedhub with the URL https://app.xspeedcache.com/xspeed/mcp and sign me in.
3Attach it and ask a first question
Type @ in a chat to attach the xspeedhub plugin to the task, then ask something that names xSpeed Hub. A list of your sites means the connection works.
Use @xspeedhub (xSpeed Hub) to list my sites and tell me which ones have page caching turned off.
Full Grok Bot setup, sign-in options and FAQ
Before you send a prompt that changes something
Reads change nothing on your sites, though contact_support emails xSpeed support. Writes run once your connection allows them, so your client's approval prompt and a read-only connection (the token's Read-only everywhere switch, or a Viewer sign-in) are the gates that matter. When an action needs approval, Grok Bot offers Allow once, Always allow or Deny. Always allow saves a rule, so the same kind of call no longer stops for you. Auto-review rules under Settings, General, Auto-review can force Ask first or allow matching actions automatically, and Ask first wins when both match. xSpeed Hub has no confirmation step of its own, so a Hub write tool you always allow runs as soon as your connection allows writes. Add Ask first rules for purge_cache, update_settings, toggle_cache, optimize_site and the other write tools. For read-only access, sign in as a Viewer member of the workspace.
What do I ask?
Three prompts written for Grok Bot. More for this job are below.
Every weekday at 7:00, use @xspeedhub (xSpeed Hub) to benchmark every site and post one line per site. Report only.
With xSpeed Hub, purge every site in my workspace after this template change and list any that failed.
Use xSpeed Hub to stop the preloader on every site while the hosts are under load, then confirm each one is idle.
What happens, step by step
If you run many WordPress sites, repeating one action on each is the slow part. Through xSpeed Hub, seven tools accept every site in a workspace, or a list of handles, in a single call. The Hub runs the sites one after another and returns a result for each, so a site that fails is named instead of hidden. Everything else in the Hub works on one site per call.
01
See what you can reach
list_sites returns each site's handle, URL, status and scopes. When you have more than one workspace, list_workspaces returns each one's handle, id, your role, its site count, which one is the default, and whether this connection can reach it.
02
Choose the scope of the call
The agent passes site: "all" for every site in one workspace, or an array of handles for exactly those sites. For a workspace other than the default it also passes the workspace argument. Omit workspace and the call acts on the default workspace.
03
Confirm once
Before a purge, toggle, settings change or preloader call that touches every site, the Hub tells the agent to say "this will touch all N sites" and wait for you, then make one call. That instruction does not name optimize_site, so for it your client's prompt is the gate. It is guidance to the agent, not a lock. It is one tool call, so one approval in your client covers every site in it.
04
Run it as one call
The Hub runs the sites one after another with a one-second pause between live calls, so a fleet purge is not a burst of traffic at your servers. Revoked sites are skipped from "all". Each site's action lands in the activity log as its own row.
05
Read the result per site
The reply is a summary of targets, succeeded and failed, plus one row per site with ok and either its data or its error. Some sites failing is a partial success. Only a run where every site failed comes back as an error.
06
Follow up on the failures
The agent reports which sites failed and why, then retries just those handles with an array. Tools that read one site, such as get_cache_status and get_health, do not fan out, so a fleet-wide check means one call per site.
Reference
| Fan-out tools | purge_cache, toggle_cache, update_settings, start_preloader, stop_preloader, optimize_site, run_benchmark |
|---|---|
| Selector | site: "all", or an array of handles |
| What all covers | Every site this connection can see in one workspace, minus revoked ones |
| Pacing | One after another, with a 1 second pause between live calls |
| Result | summary (targets, succeeded, failed) and a row per site: ok, then data or error |
| Partial failure | Reported per site; the call counts as an error only when every site failed |
| Workspace argument | Optional. Omit it for the default workspace; name one by its handle or id from list_workspaces |
| Reach | Fixed when you approve the connection; list_workspaces shows reachable: false for the rest |
| Not fan-out | get_health, get_cache_status and every other tool take one site per call |
| Slow tools | optimize_site takes up to 2 minutes per site; a target_score run is capped at 12 rounds per call |
| Read-only | The connection token with Read-only everywhere on, or a Viewer sign-in, refuses every fan-out write; run_benchmark works. An OAuth sign-in gets the scopes the client asks for |
| Hub daily pass | Re-verifies sites, snapshots cache status and hit ratio, reads stored reports, alerts by Slack webhook or email |
Rules worth keeping
- Confirm once, then call once. The Hub has no confirmation step of its own, so your client's approval prompt and a read-only connection (the connection token with Read-only everywhere on, or a Viewer sign-in) are the gates that matter. The Hub's "this will touch all N sites" is an instruction to the agent for purge, toggle, settings and preloader calls, and it does not name optimize_site.
- "all" is one workspace, never every workspace. To act in another workspace, name it. A write to a non-default workspace must name it, and an array of handles is looked up only in the workspace the call names.
- Read every result per site. Treat some sites failing as a partial result, and never accept a blanket "done" from the agent.
- Try a behaviour change on one site before you send it to the fleet. toggle_cache and update_settings on every site are one call, and each site checks values against its own settings, so a Pro setting can fail on a Free site.
- optimize_site on many sites is slow, because each site can take up to two minutes inside one call. Use dry_run first, or name a short list of handles.
- The Hub has no scheduler for agent prompts. Its own daily pass and alerts run without an agent, and an agent can only act when you send a prompt or your AI client runs one on a timer.
Good to know with Grok Bot
Add Ask first rules for the six fan-out tools that write (purge_cache, toggle_cache, update_settings, start_preloader, stop_preloader and optimize_site) before you write your first routine, and resist Always allow on any of them, because that grant covers every site in the workspace in one call. A plugin you add from your own chat is personal and account-wide, so every Bot on your account can reach all of your sites through it. If only one Bot should, use a Team Bot whose owner adds the plugin in its Setup panel, where each teammate signs in to xSpeed Hub with their own account and their own role. The sign-in is OAuth, so the Hub's Read-only everywhere switch does not apply; a Viewer member's sign-in is the read-only route, and it still allows a fleet benchmark. On a team plan, xAI says Grok Bot inherits your team's Cursor connector policy, so a blocked Hub shows as Disabled by team admin until an admin allows it.
More prompts for this job
They work in any client connected to xSpeed Hub.
Use xSpeed Hub to list every site I can reach, and every workspace, and say which workspace you act in by default.
With xSpeed Hub, purge the cache on every site in my workspace and tell me which ones failed.
Use xSpeed Hub to run a benchmark on all my sites and rank them by cached response time.
Use xSpeed Hub to start the preloader on blog, shop and docs only.
With xSpeed Hub, turn page caching on for every site where it is off. Check each site first.
Use xSpeed Hub to stop the preloader everywhere. The servers are busy.
Ask xSpeed Hub to preview a safe optimize_site pass on every site with dry_run and summarize what it would change.
Use xSpeed Hub to purge every site in the client-acme workspace, not my default one.
Frequently asked questions
Keep going
Manage every site at once with other agents
More with Grok Bot
Documentation
- Managing your fleet with xSpeed Hub
- Teams, roles and workspaces in xSpeed Hub
- Scoped AI connections in xSpeed Hub
- Connecting to xSpeed Hub
- How to write prompts for xSpeed Hub
- Grok Bot + xSpeed
- Every AI agent that works with xSpeed
From the blog