Manhours are Opus’s unit of measurement for usage. They represent the work your jobs do. You’re only charged when a job completes successfully—failed jobs don’t cost anything.
How Manhours Work
| Term | What it means |
|---|
| Estimate | What Opus thinks the job will cost before it runs |
| Actual charge | What you actually pay, based on what ran |
| Conditional paths | If your workflow has branches, the estimate shows the most expensive path—but you only pay for the path that actually runs |
Estimates are always worst-case. Your actual charge is often lower.
When You’re Charged
Jobs
You’re only charged when a job completes successfully:
| Job status | Charged? |
|---|
| Created | No |
| Queued | No |
| Running | No |
| Completed | Yes |
| Failed | No |
If a job fails, you don’t pay—so you can retry without worrying about double charges.
Builder Activities
Manhours are also consumed when:
- Running previews in the Builder to test your workflows
- Using Prompt to Workflow to generate workflows from natural language
- Using Opus AI Assist to edit and modify workflows in the Builder
Viewing Your Usage
Every charge is logged with full details:
- When it happened
- Which workflow and workspace
- How many Manhours were used
- Your remaining balance
- Who ran the job
Find this log in Organization settings → Plan & Usage → Usage.
