Agent Storefront

Clize

Clize is a CLI and MCP server that gives AI coding agents real-world actions: domains, email, deploys, payments, and media generation. Your agent already has a brain — Clize gives it hands: a domain, a working inbox, a live website. One CLI (plus an MCP server) so coding agents in Claude Code / Codex can register domains, run real email, build & ship sites and short clips, generate media, and collect payments from their customers — across as many projects as you run.

→ [clize.ai](https://clize.ai)

Install

npm i -g @clize/clize

clize install # wire clize into your coding agent (Claude Code / Codex)

clize install is the step that makes your agent actually *reach for* clize — a binary on your PATH doesn't tell the agent it exists. By default it drops clize's skill (when to use it + the safety gates) into each agent's skills dir; the skill is lightweight — only its short description sits in context until something triggers it. It auto-detects Claude Code (~/.claude), Codex (~/.codex) and Pi (~/.pi); Codex and Pi share the open ~/.agents/skills directory, so any agent that reads it gets the skill too. Scope with --claude / --codex / --pi, preview with --dry-run. Add --mcp to also register the clize-mcp server — opt-in, because an MCP server's tool list stays in context every session.

Update later with one command — pulls the latest release and refreshes the skill together:

clize update            # or `clize update --check` to only check for a newer version

If something looks stale after an update, clize doctor prints what's installed vs what's actually running — CLI version (and the upgrade command that works for your install manager: volta / pnpm / asdf / …), skill drift, and control-plane reachability.

Output is English by default. CLIZE_LANG=zh (or a zh* system locale) switches the CLI, the MCP tool descriptions and the control plane's messages to Chinese; the dictionary lives in src/i18n/zh.ts.

Quickstart (hosted)

Log in and go — your agent never touches Cloudflare:

clize login                              # browser authorize; the first login creates your account

clize claim acme --email # free identity: acme.clize.app + support@acme.clize.app clize init --handle acme # bind this directory (deploy / send / inbox infer the rest) clize email inbox --wait-for "verify" # give the new inbox a minute, then the agent signs up with support@acme.clize.app and reads the code here clize status # who is waiting (real people + codes only), this month's spend clize email send --to a@b.com --subject "Re: …" --text "…" # queued for a one-tap approval in the console; --confirm sends now clize deploy ./site # ship a static site → https://acme.clize.app

Examples you can run (recorded 2026-10-01, with timings, costs and what failed)

Each one is Clize's own account and site (self-use), not a customer story.

Hosted — just log in

clize is a thin client: the CLI / MCP carry no infrastructure credentials and talk only to the clize control plane — domains, email, deploy, and media all run hosted. (Credentials live in your dashboard; bring-your-own Cloudflare / Vercel is configured there, not on your machine.)

A few specifics worth knowing:

• clize deploy and clize email send need --domain / --from — unless the directory is bound with clize init --handle , which infers both from ./clize.json. Deploy is directory-based (multi-file static sites).
• gen image --ref/--mask (image-to-image / inpainting / multi-image composition) work hosted — reference-image caps follow the upstream model: 16 for gpt-image-2, 14 for nano-banana-2 (video/veo takes 3); each ≤10 MB, ≤80 MB total. gpt-image-2 runs as an async task (heavy multi-ref jobs take minutes — no sync-pipe timeouts): the CLI waits by default (--timeout, default 300 s), or use --async and collect with gen status ; one image per task (--n > 1 → split), --mask inpainting is nano-banana-2 only. gen budget pre-approval isn't hosted yet: every generation confirms individually with --confirm.
• Free *.clize.app handle: clize claim . Your own domain: clize domain buy / clize domain import. Run clize check to verify your login.
• Free-tier quotas (anti-abuse, per tenant): 3 handles · 5 mailboxes · 10 claim attempts/day · 30 outbound emails/day · 20 deploys/day · 500 MB per site. Any top-up lifts you to the trusted tier (10 · 30 · 30 · 200 · 100 · 5 GB). Over-limit calls return a plain 429 — nothing is charged.
• A deploy target is a free handle or a whole domain in your account; a subdomain of your domain (blog.example.com) is not a separate deploy target today. Names bought with clize domain buy are registered with Clize's registrant contact at the underlying registrar — to be the registrant of record, register elsewhere and clize domain import. Some ccTLDs (.de .fr .es .jp .kr .com.br .uk .eu) are not registrable through Clize; clize domain tlds lists the 555 that are.

What it does

| Deploy | clize deploy --domain — multi-file static sites; free *.clize.app or your own domain. Preview locally first with clize serve (proper Range support — pages actually play in Safari). Deploy runs the same guards as build site check before uploading — doorway-shaped near-duplicates block the upload (--allow-similar to override), and after upload every _redirects rule is probed live; the result rides along in the deploy output as guards (including the three GEO warnings from build site check). Deploy only adds or overwrites: a live path missing from stays online and is listed under `o