Images, video and music — generated from a chat, saved as real files in your project. Every job is priced before a cent moves; inside your budget it just makes things.
No model API keys · Quotes are free · Works in Claude Code & Codex
15s veo clip + music bed, quoted and waiting for your OK. Nothing has been charged.
One conversation in Claude Code — and the poster, the clip and the track are ordinary files in your repo.
Four everyday jobs — each one lands as a file, not a link that expires.

Launch art, store product images, blog headers — with reference images (up to 16), your character or product stays on-model across a whole set.

Teasers and social clips from a prompt or a still. Long renders run as jobs — close the laptop, gen status reconnects, the file is there.

Background tracks for videos, demos and stores — generated to length, saved as audio files you own outright.

Every job is quoted first. Set gen budget once: the agent creates freely inside it, and stops to ask the moment a job would cross the line.
Ask → price → nod → file. With a budget set, panel three usually isn't needed.
Three steps. No model keys, no vendor dashboards.
One package puts it into Claude Code and Codex.
$ npm i -g @clize/media $ clize login
The only switch that matters — quotes below it run without asking.
$ clize gen budget set 2.00In plain language, inside your coding agent.
You: make a poster for
the launch pageNo --confirm and no budget means no charge — a quote is always free.
Raise it, lower it, approve one-offs — the agent can't move the cap itself.
Everything lands in your repo as an ordinary file. No expiring URLs, no lock-in.
The short honest versions.
A media studio your AI coding agent operates from a chat: images (gpt-image, nano-banana), video (veo) and music, generated on your Clize balance and saved as ordinary files in your project — no model API keys to configure.
Every generation is priced before it runs. Without --confirm a command only quotes — nothing is charged. Approve one job with --confirm, or set clize gen budget set 2.00 once and jobs inside the cap run without asking each time.
No. One Clize account covers the image, video and music models. Your agent never handles a model key, so there is nothing to rotate or leak.
Yes — gen image takes reference images (up to 16 for gpt-image, 14 for nano-banana). Feed it your mascot or product shots and the whole set stays on-model. The robot illustrations on this page were made exactly that way.
They run as tracked jobs. Close the laptop mid-render: clize gen jobs lists what's running, clize gen status reconnects, and the file lands when it's done.
Those are model APIs for developers. Agent Media is an agent-first surface: quotes before spend, a budget gate, files on disk, and the same account that already runs your domains, email, deploys and store.
In clize-assets/ inside your project — ordinary files you own. From there your agent can deploy them into a site, attach them to an email, or list them in your store.
Install, set a budget, and ask for your first poster — it's a one-liner.
$ npm i -g @clize/media && clize login && clize gen image "a launch poster"