> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hitpayapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Grok Bot Templates

> Add HitPay templates to your Grok Bot in one click. Start with HitPay Store Builder: turn your current website into a custom-branded online store with HitPay checkout.

A **Grok Bot template** is a ready-made AI assistant setup, with its instructions and skills, that you add to your own Grok Bot. Adding a template copies the setup, not anyone's data. After you add it, you connect your own HitPay account. See xAI's [guide to templates for Grok Bot](https://x.ai/bot/guides/templates-for-grok-bot).

## HitPay Store Builder

Give **HitPay Store Builder** your current website domain (for example `brand.com`). It reads your site, pulls your branding, products, collections, pages and blog posts, imports your products into HitPay, and builds a fast, custom-branded online store with HitPay checkout.

Orders, inventory, customers and payments stay in your [HitPay dashboard](https://dashboard.hit-pay.com). Your store is hosted by HitPay by default.

> [!NOTE]
>
> **Add to Grok Bot:** Template link coming soon.

### How it works

**1. Add the template**

Add HitPay Store Builder to your Grok Bot.

**2. Sign in to HitPay**

When it asks, sign in to HitPay and approve access (OAuth). You never paste an API key.

**3. Give it your domain**

Tell it your current website domain, for example `brand.com`.

**4. Review the preview**

It sends you a preview link of your new store and a list of what migrated and what didn't.

**5. Approve to go live**

Nothing goes live until you approve. When you do, it sets up 301 redirects from your old URLs, carries over your SEO titles and descriptions, and gives you the exact DNS records to connect your own domain.

### Permissions it asks for

When you sign in, HitPay Store Builder asks for these permissions:

* `commerce:read`
* `commerce:create`
* `commerce:update`
* `customer:read`

It never asks for delete, refund or cancel permissions unless you opt in.

### What doesn't migrate

* Customer passwords and accounts
* Past orders
* App features, such as reviews or loyalty points

### Safety

* Nothing goes live without your approval, and every later change goes to a preview first.
* It never emails your customers.
* It never deletes data or issues refunds.
* It never asks for passwords or API secrets in chat.

## Related guides

* [AI developer tools overview](https://docs.hitpayapp.com/apis/guide/ai-developer-tools.md): MCP Server, Agent Skills, CLI and more
* [HitPay MCP Server](https://docs.hitpayapp.com/apis/guide/mcp-server.md): query your business data from Claude, Cursor and other AI assistants
* [Set up your online store](https://docs.hitpayapp.com/store/setup-online-store.md): manage your HitPay online store
* [Custom domain](https://docs.hitpayapp.com/store/custom-domain.md): connect your own domain to your store


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.