Your agent gets a studio.You approve every job.
Images, video and music — generated from a chat, saved as real files in your project. Every job is priced before a cent moves — and runs only on your confirm.
No model API keys · Quotes are free · Works in Claude Code, Codex & any agent that runs skills or MCP
15s veo clip + music bed, priced and not started. Nothing has been charged.
One conversation in Claude Code — and the poster, the clip and the track are ordinary files in your repo.
What people have their agents make
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 and runs only on your --confirm — and every charge lands in clize audit.
The loop, in four panels
Ask → price → nod → file. Panel three is always yours.
Up and running in a minute
Three steps. No model keys, no vendor dashboards.
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
Without --confirm a command only quotes. Add it, and the job runs.
$ clize gen image "launch poster" --out poster.png # quote: $0.05 · nothing charged $ clize gen image "launch poster" --out poster.png --confirm
In plain language, inside your coding agent.
You: make a poster for
the launch pageNo --confirm means no charge — a quote is always free.
The agent cannot approve its own spend; every generation carries your --confirm and lands in the audit log.
Everything lands in your repo as an ordinary file. No expiring URLs, no lock-in.
Questions, answered
The short honest versions.
What is Agent Media?
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.
How does pricing work?
Every generation is priced before it runs. Without --confirm a command only quotes — nothing is charged. Pass --confirm to run it. For a batch, pre-approve one round in the conversation; the agent still passes --confirm per job, so every charge shows in clize audit.
Do I need OpenAI or Google API keys?
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.
Can it keep a character or product consistent?
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.
What happens to long video or music jobs?
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.
How is this different from fal.ai or Replicate?
Those are model APIs for developers. Agent Media is an agent-first surface: quotes before spend, your --confirm on every job, files on disk, and the same account that already runs your domains, email, deploys and store.
Where do the files end up?
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.
Give your agent a studio
Install, log in, and ask for your first poster — it's a one-liner.
$ npm i -g @clize/clize && clize install && clize login && clize gen image "a launch poster"
Get started free