Understanding Max per Run
What max per run means, how the authorize–capture–release model charges you only the actual cost, and how each payment method applies it.
Written By Philippe
Last updated 3 days ago
Understanding "Max per run"
Every workflow on indie.money shows a Max per run — the most a single run canever cost you. It is set by the workflow's Builder when the workflow is published and cannever be exceeded: if a run tries to spend past it, the run is stopped.
The three parts
Max per run adds up to one number from up to three parts:
The parts are cumulative: Max per run = run price + usage budget + workflow-call budget.The total can never exceed the max, and the workflow-call budget is a hard cap onpayments to other workflows.
Exception — workflows that include AI usage in their price. When the Buildercovers AI usage from their own keys, their key safety limit is not part of what youpay or what is held: it is the Builder's private limit on their own spending. Forthose workflows the marketplace shows a single flat price instead of a range, andno separate "Max per run" figure.
The most one run can cost you is still that price plus the $0.001 payment-processingfee that pay-per-run calls add, and the workflow's page states that maximum besidethe price. Runs paid from a workflow balance or a free trial don't add the fee, sothose cost exactly the run price.
You pay actual costs, not the max
The max works like a card pre-authorization at a hotel:
- Authorize — when a run starts, the max is reserved.
- Capture — when it finishes, you are charged only what the run actually used.
- Release — the unused difference is returned automatically, usually within a few minutes.
You can see both numbers for every run on its execution page: Authorized max(what was reserved) and the actual charge (what you paid).
How each payment method uses it
- Pay-as-you-go — you authorize the max (plus the $0.001 payment-processing fee)when you call the workflow; the unused part is returned after the run.
- Prepaid balance — the max is held from your balance during the run, then thehold is released down to the actual cost.
- Workflow balance (Producer-funded) — the same hold happens against the workflow'sbudget. If the budget can't cover the max, the run doesn't start.
- Free trial runs — you pay nothing; the Builder covers the run's costs.
What happens when a run hits the max
The run stops immediately with a "Cost ceiling reached" error, and you are onlycharged for what was spent before the stop. If a workflow regularly hits its max, theBuilder set the cap too low for what the workflow does — let them know, or check theworkflow's page for an updated version.
Related articles
Was this helpful?
Still need help? Ask the team