Your agent runs the store.You approve the money.
Like a storefront with staff — it publishes the catalog, works the orders and ships the boxes, all inside Claude Code, Codex, or any agent that runs skills or MCP.
Free handle included · No credit card · Works in Claude Code, Codex & any agent that runs skills or MCP
#218 · $48 — “item arrived chipped”. Preview only: money moves when you confirm.
✓ Confirm refundYour agent works in the chat. The orders are real.
What it does for you
Four things people actually use it for — from day one.
Your agent writes the storefront and publishes the catalog — one deploy and it’s live on a real domain.
Nothing to wire up: checkout works immediately and every payment lands in your Clize balance — no payment account to set up.
Todo lists, supplier notes, tracking numbers — 17TRACK watches every shipment so delivery marks itself.
A refund only previews until you confirm — and every buyer email is drafted for your okay first.
The loop, in four panels
Every job runs the same way — and the money panel is always yours.
Up and running in a minute
Three steps. No dashboard, no config homework.
One package. clize install wires the skill into Claude Code, Codex, Pi — any agent that runs skills or MCP; log in once in the browser.
$ npm i -g @clize/clize $ clize install $ clize login
A catalog, a cart, and a live site on a free handle.
$ clize claim mystore $ clize shop init
From here it's plain language, inside your agent.
You: how's the
store today?Refunds preview and stop until you say so — every one lands in the audit log.
Shipping notices and replies are drafted, never sent unattended.
The checkout reads prices from the deployed catalog — a tampered cart can’t underpay.
How the first money reaches you
The question every new store asks before it asks anything else. There is no payment account to open — but read step 3 before you plan around it.
Your products sit in a _catalog.json file at the root of the deployed site. When a buyer checks out, the server re-reads that file and prices the cart from it — so a cart edited in the browser cannot underpay.
$ clize shop init # prints the contract: _catalog.json # + add-to-cart buttons + cart.js
No merchant onboarding, no keys, no waiting for approval. A buyer checks out on the store — or you charge once with a link, which is the shape a quote, a deposit or an invoice usually wants.
$ clize pay link --amount 48 \ --for "order 221"
The full amount the buyer paid, with no platform fee taken out of it. That balance is spendable inside Clize — domains, deploys, image, video and music generation, SEO research — and today it cannot be withdrawn to a bank.
$ clize balanceThat third step is the honest limit of the product right now, and it is better decided before you build a catalog around it. Paying out directly into your own Stripe account is built, but it is not switched on at the platform level yet; while it is off, every payment is collected for you instead, and recurring subscriptions are not available in that mode. When direct payout opens, connecting Stripe once in the web dashboard moves new payments across — your site, your catalog and your buttons stay exactly as they are. Until then, treat the balance as credit that pays for the running of the store: the domain it sits on, the deploys, the photography in the listings.
Three tools for the fiddly parts
Free, in the browser, nothing to install or sign up for.
Type your products in, get a _catalog.json that passes validation — or paste one you already have and see exactly which line the deploy will reject.
The card numbers for every outcome worth rehearsing — a clean success, a decline, an expired card — with the PaymentMethod token to use in server code instead of raw digits.
What Stripe keeps and what actually arrives, per charge. For the balance mode above Clize takes nothing, so this one is for the store you already run elsewhere.
Inside the agent you already use
Same store, same gates. What differs per host is where the skill lands and how the MCP server is registered.
Questions, answered
The short honest versions.
What is Agent Storefront?
Agent Storefront is the commerce product of Clize: your AI agent publishes a catalog to a live site, takes payments at a checkout, and runs fulfillment afterwards — orders, supplier orders, tracking numbers, shipping notices and refunds. It installs into Claude Code, Codex, and any agent that runs skills or MCP, as a CLI and MCP server, and the gates stay human: refunds only preview until you confirm, and customer email is drafted for your approval.
Can an AI agent run an online store?
Yes, for the mechanical half. An agent can write the storefront, publish the catalog, deploy it to a real domain, read the orders, record supplier orders and tracking numbers, draft the buyer emails and prepare refunds. What stays with you are the business calls — what to sell, at what price, whether a refund is fair — and the two actions that need a human: sending mail and moving money.
Do I need a Stripe account before I can collect money?
No. Collecting is zero-config: run clize pay link, or let a buyer check out on your storefront, and the payment goes through with nothing configured first. Today every payment lands in your Clize balance: no fee, spendable on Clize (domains, media, SEO research), not withdrawable to a bank. Direct payout to your own Stripe account is not enabled on the platform yet; when it opens, connecting Stripe in the web dashboard switches payments over automatically — nothing to change on your site.
Where does the money go?
Today every payment lands in your Clize balance: no fee, spendable on Clize (domains, media, SEO research), not withdrawable to a bank. Direct payout to your own Stripe account is not enabled on the platform yet; when it opens, connecting Stripe in the web dashboard switches payments over automatically — nothing to change on your site.
Can the agent refund a customer on its own?
No. clize shop refund prints a preview — order, amount, reason — and stops there. Money only moves when a human passes --confirm, and every refund is written to the audit log. The same shape of gate covers the buyer emails: clize shop notify drafts the shipping notice and waits for your okay.
How does this relate to agentic-commerce protocols like ACP, UCP and AP2?
Those protocols describe the buyer's side: how someone else's agent discovers products, checks out and pays. Agent Storefront is the other end of the same transaction — the store being bought from, run by your agent. A Clize storefront is an ordinary web store with a Stripe checkout, so it stays reachable however the buyer arrives: a person, a browser agent, or a protocol-driven one.
Does it work with Claude Code and Codex?
Yes. One install wires Clize into Claude Code, Codex, and any agent that runs skills or MCP — as a skill by default, or an MCP server if you prefer structured tools. The store, the support inbox and the domain it all runs on are reachable from the same session.
Open the store
A free handle gets you a live site, a checkout and a place for the money to land.
$ npm i -g @clize/clize && clize install && clize claim mystore && clize shop init
Get started free