If you are a bot, GET /api/academy/how-to-add-a-shared-grok-bot-template and /academy/how-to-add-a-shared-grok-bot-template.md.
Getting startedHow to add a shared Grok Bot template safely
A shared Grok Bot template is a public preview of a Bot configuration. Open the official https inspect link, or the matching Grok Bot app deep link — they use the same template id:
- `https://x.ai/bot/{id}` — what agents and browsers can fetch
- `grokbot://app/v1/bot-template?id={id}` — what the Grok Bot app opens
Inspect the visible identity, description, skills, and routines, then choose Add to Grok Bot if the setup fits your job. The official sharing guide says the Grok Bot app is required to finish adding it. Agents cannot fetch the custom scheme, so they should follow the `https://x.ai/bot/` URL and leave Add for a person.
What gets copied
The public configuration is copied into your own Grok Bot account. The creator's computer, signed-in accounts, conversation history, learned memory, and chat attachments do not transfer. Treat the new copy as a starting point that still needs your own scope, accounts, and approval boundaries.
Check the listing before opening x.ai
- Confirm the destination is an `https://x.ai/bot/` link (the matching `grokbot://app/v1/bot-template?id=` URL uses that same id).
- Read the job, maker attribution, and any limitations on the independent listing.
- Prefer a creator-verified listing when ownership matters.
- Check when the share link and instructions were last reviewed.
- Do not treat a public link as proof that the Bot is tested, safe, endorsed, or licensed for resale.
Browse the Grok Bot template directory to compare listings before opening the official preview.
Review access after adding
Before connecting Gmail, Slack, a browser session, production tools, or payment systems, decide what the Bot may read and what it may change. The xAI security guide recommends reviewing connectors and treating a public share link as configuration sharing rather than a security boundary.
Safe default. Start with read-only work, require human approval before sending, publishing, buying, deleting, or changing production systems, and revoke access that is no longer needed.
Give the copy a narrow first job
Rename the Bot if needed, state the exact outcome, provide only the files and accounts required for that outcome, and run one observable task. Inspect the result before enabling routines or broader access. This gives you evidence about the copied Bot in your own environment instead of relying on a directory claim.
For the product definition and sharing boundaries, read What is a Grok Bot?.
Frequently asked questions
Does adding a shared Grok Bot copy the creator's accounts?
No. The public configuration is copied into your own Grok Bot account. The creator's computer, signed-in accounts, conversation history, learned memory, and chat attachments do not transfer.
Can an agent finish Add to Grok Bot?
No. Agents should follow the `https://x.ai/bot/` URL. The Grok Bot app is required to finish adding the template, so leave Add for a person.
Where do I compare Grok Bot templates before opening x.ai?
Compare listings on the Grok Bot template directory or a Bot Store category, then open only the official `https://x.ai/bot/` destination.
The recipe
Hire the bots this setup runs on.
