What you set and what the platform sets
You set the per-task price, the share of items sampled for human review, and the per-expert task cap. The platform sets generation token rates and review-call prices. Human-review pricing uses the per-task price you set, scaled by review time divided by labeling time, plus a 10% premium. For expert labeling, Expert Service Cost shows the per-task price plus the platform commission, displayed as 33%.The cost breakdown forecast
Open Cost breakdown (forecast) to compare Price, Quantity, Expected, and Maximum for each billable line and the run’s Total. Rows are grouped by node; expand LLM review lines to inspect individual quality criteria. Invalid nodes appear in a separate collapsible section and are excluded from the totals. Each line carries two totals, and so does the run:- Expected is the average forecast, or the run’s likely cost.
- Maximum is the run’s cost if every item triggered every billable event. It is the forecast ceiling.
The cost lines
Each billable line applies to one labeling path and is priced by one unit. The Cost breakdown (forecast) window lists the lines your pipeline actually incurs.The contract freeze
Deployment fixes the run’s per-item prices for its lifetime, even if platform prices later change. Each clone receives a new estimate and contract when it deploys. Click Contract on the run to reopen its frozen breakdown.Pay from the team balance
Pipeline runs use the balance shared by every project in the team. The deploy window can recommend funding levels, and a run can pause automatically if it cannot reserve the next node’s cost. Billing covers the balance requirement, funding levels, automatic pause, top-up, and resume flow.What a canceled or failed item costs
When an item starts on a node, the platform reserves the node’s maximum cost for the item from your balance. When the item completes or is canceled on the node, you pay for the work recorded on the item, and the rest of the reserved amount returns to your balance. For the reserved lines, you never pay more than the reserved amount. Human QA and the lines marked one-time per expert are not reserved. You pay for them when the node ends. How the item ends on the node sets what you pay:
On a canceled item, each reserved line counts this work:
For example, LLM QA rejects a Generation item, and you cancel the run before the expert’s redo. The item pays for the LLM QA calls made, and for 1 Video tool call if its LLM QA watches a video. The rest of the reserved amount returns to your balance. An item canceled before any work is recorded costs nothing.
How a Match node shapes the estimate
Routing an item through a Match node costs nothing on its own. Branching changes the totals: Expected assumes items spread evenly across the branches, while Maximum sends the full item count down the most expensive complete path. The exact rules live on the Match node reference. The forecast does not know your real match rates. A Generation node with human review stops reviewing at the Maximum of its Human QA line: 3 reviews for each item of the run. This cap counts every item of the run, not only the node’s even share. A branch that receives more items than its share still gets human review on them.Related
- Billing — fund a pipeline run and recover from an automatic funding pause
- Label a large dataset in batches — use the cost window in the deploy workflow and size a monthly volume
- Quality control — understand what review costs and why
- Generation node — configure the per-task price, review, and token settings that drive these lines
- Quorum node — understand how the expert count scales the expert and review lines