How Grok Bot templates work

A Grok Bot template is a Grok Bot shared as a public link. The recipient opens a preview on x.ai, chooses Add to Grok Bot, and a copy lands in their own account. According to xAI's documentation, the copy "carries the profile, settings, enabled skills, routines, and avatar" and "does not copy conversation history, learned memory, or chat attachments" (docs.x.ai, Bots). It also arrives without API keys, signed-in sessions, scripts or MCP servers, because none of those belong to the bot. So a template can only sell what fits in those four places: the outcome the bot owns, the evidence standard it holds itself to, the line between what it may do alone and what needs a human, and the point where it stops and asks. A one-paragraph persona has none of that. The 17 templates here carry 147 skills and 103 routines of it, plus six documents per bot that a share link cannot carry at all.

A template carries instructions, skills, routines and first-party integrations.

It does not carry conversation history, learned memory, chat attachments, API keys, signed-in sessions, scripts or MCP servers.

Grok Bot gives one computer per account, shared by every bot on it, so bots on different accounts share nothing. xAI's documentation puts it plainly: "The computer is assigned to your user account, not an individual Bot," and "Every Bot on your account uses the same computer" (docs.x.ai, Computer and apps).

Those are xAI's facts, verified against their Bots documentation, which also tells the sharer to "remove API keys, internal URLs, customer data, and anything else you would not put in a public document" before sharing. Any template that claims to arrive with memory, or with your logins, is describing software that does not exist. The bots here are built on the opposite assumption: anything durable lives in the instructions, a skill, a routine or a file in the workspace, and anything the bot must know next week gets written to a sheet this week.

The buy button opens a checkout hosted by Polar. Polar is the merchant of record, so the receipt, the tax and any refund come from them. When the payment goes through, Polar shows its own confirmation page and, about a minute later, emails you the receipt. The download is in that email. It is a ZIP holding:

• The six documents for the bot you bought.
• LINK.txt, a text file holding the share link. Open it in Grok Bot and the bot is in your account.

The Operator Pack is one ZIP with five folders, and Everything is one ZIP with 17. Nothing is sent by hand, nothing waits on us, and nothing carries your name. If the email is not there in five minutes, check spam, then write to us. The same email links Polar's customer portal, where the download stays available under the address you paid with. Once you have the ZIP, start here gives the first steps in order.

There is no call to book. SETUP.md inside each bot does that job. It gives the order: create the Grok Bot account under the member who will own the bot, add the bot from the link, then authorise connectors one at a time. Which connectors depends on the bot. Stripe, QuickBooks, HubSpot or Salesforce, Gmail, Slack, Shopify, Linear, and the Google Sheet that holds the register.

Connector authorisation is where template buyers give up, and a buyer who never finishes setup never sees value. So SETUP.md is written for that hour and nothing else. Every step names the scope the connector needs, what the bot does with it, and what to check before the next step. Most buyers are through it in under an hour. If you get stuck on a step, write to us and name the step.

Each bot ships with EVAL.md, a set of acceptance tests you run on day one against your real data with sending disabled. They tell you whether the bot reconciles your systems correctly, stays silent when it should, escalates when it should, and refuses the things it must refuse, before you let it near a customer or a vendor.

The tests are also the refund condition. If a test fails, tell us which one and you get your money back within 14 days. Most of the time the fix is a placeholder or a connector scope, and the refund request turns into a support request. The ones that survive that are genuine.