AI Builder

Ask for a section, get two or three.

You write one sentence about the section you want. Two or three versions come back, and none of them touch your store until you pick one.

The Add Section dialog with Generate with AI selected: a typed request for a restock announcement bar, the day's remaining allowance, and eight starting points to pick from
Two or three versions
Written at the same time from the same sentence. You keep one and drop the rest.
600 characters
The length of one request. Your theme’s fonts, colors and sections are already in the picture.
Your colors, your fonts
A generated section can only use what your theme already ships, so it cannot invent a look of its own.

One section at a time

Point at a section. Say what to change.

Pick a section, or one element inside it, and type the change in your own words. Ask AI makes the smallest edit that does the job and leaves the rest of the page where it was.

Only what you picked
The name next to Ask AI is the whole reach of the edit. Drop it and the instruction goes to the section instead.
Keep or Reject
The edit is applied so you can look at it, with both buttons in the same box. Reject puts it back.
Starting points per section
Punchier title, stronger call to action, tighter spacing. One tap runs it, so you do not have to phrase it.
The Ask AI box open over the storefront it edits, scoped to the Hero by the chip beside it, with a typed instruction, three one-tap suggestions and Apply — the selected section outlined behind it and its toolbar above

Bigger changes

It plans the changes. You apply them.

Describe something that runs across the whole storefront and the chat comes back with the exact list of changes it wants to make. Nothing moves until you press Apply.

A list you read first
Every step is named with the values it would set. Dismiss it and your storefront was never touched.
Undo one step at a time
Applied changes land in the same history as your own edits, so ⌘Z walks back through them.
It notices when you moved on
Edit the page after asking and the plan says so before you apply it, instead of overwriting your newer work.
The AI Builder chat panel with the day’s remaining allowance in its header and a typed instruction in the composer

Advanced storefronts

An agent inside your own source.

An advanced storefront is React code you own, and the AI Editor works on it directly. It reads the files it needs, writes the change, and kicks off the build. One request is one round.

Twelve files at most
It picks the files the change needs and stops there. A round cannot wander through the whole storefront.
The build reports back
You see every file it touched and whether the build passed. When it fails, one button hands the log back to it.
Your open files are safe
A round starts from the saved version, so the panel holds itself shut until you have saved what is in the editor.
The AI Editor rail on a code storefront: the day’s usage meter, three example instructions, and a typed request in the composer

What it costs

Already in the platform fee.

There is no AI plan, no credit pack to keep topped up and no per-seat surcharge. Every shop gets the same allowance, and it comes back every day.

2,000,000

tokens per shop, per day, refilled at midnight UTC

The AI usage meter in the builder: 2M left of 2M today, marked included and resetting daily, with the available, used and total figures below it

Calls per shop, per day

chat
500
inline_edit
500
generate_section
200
code_agent
200
generate_image
25

Ceilings that sit alongside the token allowance. They are there to stop a runaway loop, not to ration a working day: two hundred generated sections is more than anyone builds.

Your own client

Hand one theme to the tool on your desk.

Edit with AI mints a key for a single theme, prints the install command for the client you picked, and lets your own assistant work against the same API the Builder uses. Nothing else in the shop is reachable with it.

Twenty-four hours
The key reads and writes that one theme, expires on its own, and can be revoked before it does.
51 commerce tools, 7 theme tools
Products, orders, customers, coupons and analytics on one server. Documents, settings and publishing on the other.
Five clients
Cursor, Claude Code, Codex, Claude Desktop and Windsurf. The CLI writes the config for whichever you choose.
The Edit with AI dialog: a local checkout path and an MCP connection path, a picker for Cursor, Claude Code, Codex, Claude Desktop and Windsurf, and a note that the generated key reaches this theme only and expires after 24 hours

$ npx @shoppexio/mcp-shoppex install --client cursor --api-key shx_…

installed · 58 tools available

One command per client. The installer writes into the config file that client already reads, so there is nothing to paste by hand.

Prefer files on disk? The other path checks the theme out with the CLI, previews it locally, and pushes it back when you are done.

Describe a section and see what comes back.

The allowance is on the free plan too, so your first section costs nothing but the sentence you write.