Usage units and credits

Usage units

A usage unit is roughly one bounded agent or execution step. Units come from your plan's monthly allowance.

Work	Units	Per
Ask the design agent (a message or quick action)	5	message, at most, unless you approve more
Generate two design directions	6	request, at most
Make a design system from a reference	6	run (up to 6; colours alone 1)
Analyse a reference	1	reference
Scan a code repository	5	scan
Preview components from code (builds and renders them)	15	preview
Preview components a preview run has not drawn yet	2	up to 20 components (1 more per further 20, at most 11), at most
Capture a live app	8	first variant (less for each extra)
Translate strings	2	batch of strings per language, at most
Publish store listings	2	store and language
Taste check judgment (headlines and overall look)	2	check, at most
Implementation run (build a pull request)	25	run

Reserved up front, charged for what was used

Every run reserves its cost before it starts. When it finishes you're charged what it actually used and the rest returns to your allowance. If you cancel a run, or it fails, the unused reservation is released, and failures on M1rror's side aren't charged.

The design agent's auto-approve limit

The design agent runs small requests straight away, up to 5 units per message by default. People who manage billing can set the limit anywhere from 0 ("always ask") to 50 under Design agent approvals. Bigger work is quoted first; approving reserves the top of the quote (at most 60 units), and quotes themselves are free.

Credits

Generating images, vectors and video spends credits, not units. One credit is $0.01.

• Each plan includes credits every month; included credits are used first and don't roll over.
• Credit packs: 500 for $5, 2,500 for $20, 12,000 for $80. Purchased credits are valid for 12 months.
• A workspace can spend at most 2,500 credits per day (UTC) by default; owners can change this, and 0 pauses generation.

The price of each generation is shown before it starts.