How billing works
Workflows do not add an orchestration surcharge. Their total is the model and billed tool work performed by their steps.
- A workflow conversion step uses the same 1-credit conversion rate as the standalone API.
- Model calls keep their selected model's pricing.
- Budgets can stop execution before known billable work begins.
Price in practice
An agent run is a container for steps, not a separately priced product. Inspect the model and tool steps it can call to understand the possible total.
A budget is useful because the system checks known tool costs before each step instead of charging a single opaque workflow fee.
Rate card
ServicePriceHow it is applied
Agent or workflow shell0 CrNo standalone orchestration price
Model callsVariableCharged at the selected model rate
Billed tool stepsVariableCharged at the relevant tool rate
Questions
How can I control a workflow's cost?
Set a budget before the run. The API checks known tool costs before execution and records the credits used by every step.
Is there a fee to start a workflow?
No. A workflow shell has no standalone orchestration charge.
What makes a workflow cost credits?
Its model calls and any billed tool steps use their respective published rates.