Let your AI agent generate images, video, and music as real files

Brain vs. hands

Your agent is good at one half of media generation and physically can't do the other. It can understand what the image should be and write a sharp prompt — that's the brain's job. It can't emit a PNG, an MP4, or a WAV; a language model produces text, not bytes. Clize is the hands: the agent (or you) writes the prompt, Clize calls the models, and the actual file comes back. The prompt is thinking; generating the file is doing — and now your agent can do both.

No model keys to manage (hosted)

In hosted mode you bring no model keys of your own. You don't sign up with an image provider, a video provider, and a music provider, juggle three billing accounts, or paste API keys into your agent's environment. Clize pays the providers and returns the result; your Clize balance is the only thing to top up. If you'd rather own the relationship, self-host mode lets you bring your own provider keys and pay them directly — same commands, your account.

The commands

Generation is a small, honest command surface. Each gen verb maps to a modality; the job-management verbs let an agent reconnect to long renders after the session that started them is gone.

$ clize gen image <prompt> --confirm   # synchronous — file lands on disk
$ clize gen video <prompt>             # async — returns a job id
$ clize gen music <prompt>             # async — returns a job id
$ clize gen jobs                       # list jobs, running ones first
$ clize gen status <id>              # pull a finished render
$ clize gen list                       # past generations
$ clize gen budget                     # pre-approve spend (self-host)

No flag means no charge: run a gen command without --confirm and Clize returns a price quote instead of spending. It pairs naturally with Claude Code or Codex — the same agent that writes your code writes your prompts.

The output contract

Results land as files on disk and URLs — never a giant base64 blob dumped into the transcript. An image comes back as a path under ./clize-assets (or wherever --out points); video and music come back as durable URLs the CLI writes down for you. stdout carries compact metadata JSON, so the agent gets a path it can act on, not a wall of binary it has to choke through. From there the file is just a file: ready to deploy to a site or attach to an email.

What comes back — three prompts, three files

Everything below was generated for this page with the exact command you just read — prompt in, file out, priced before it spent. Three prompts, three deliberately different styles, $0.15 total.

Where the bytes go next

A generated file isn't the finish line — it's an input to the next real-world action. That's where Clize's other hands take over:

• Generate a hero image → ship it. Make the artwork, drop it into your build, and deploy with clize deploy. The image your agent couldn't draw is live on the page minutes later.
• Generate an image → attach it. Pass the path straight to email: clize email send --attach <path>. Generated asset, out the door, under your name.
• Generate video or music → review first. The expensive, slow modalities get a human's eyes before they're used anywhere. The agent produces; you approve.

Safety & cost

Spending money on a model is a real-world action, so it sits behind the same gate as everything else Clize does with your wallet:

• Quote, then confirm. Every generation quotes a price up front and won't spend without an explicit --confirm. In self-host mode a pre-approved gen budget can clear small jobs within a ceiling you set; hosted mode confirms each one.
• Failed jobs are refunded. Clize charges before it generates, and if the provider fails or produces nothing, the charge is returned. You pay for output, not attempts.
• No blind retries. A failed job stops and reports — it doesn't silently loop and re-spend trying to brute-force a result. The agent treats a failure as data to read, not a button to mash.

$ npm i -g @clize/clize
$ clize login
$ clize install   # wires Clize into Claude Code & Codex