A pay-per-event orchestrator started with maxTotalChargeUsd has no help keeping its children inside that budget. Each child accepts its own max_total_charge_usd, but splitting the parent's remaining budget across children, adjusting as earlier children finish under their cap, is left to the caller. The orchestrator skill (apify/agent-skills#90) lists this as a must-have, which means agents are currently writing it themselves.
Depends on #1127: the remaining budget is the parent's limit minus what tracked children have charged so far, and only the registry knows the children after a restart.
Proposal
When the parent run has maxTotalChargeUsd and a named child is started without an explicit max_total_charge_usd, the SDK sets it to the parent's remaining budget (parent limit minus the sum of usage_total_usd / charged amounts of tracked children, minus the parent's own charge so far). An explicit max_total_charge_usd on the child is capped at the remaining budget rather than passed through.
A budget_per_child option could let the caller reserve headroom for later children, but the default above already guarantees the subtree never exceeds the parent's limit.
Longer term this is better enforced on the platform for a parent's whole subtree, but the SDK version works today.
✍️ Drafted by Claude Code
A pay-per-event orchestrator started with
maxTotalChargeUsdhas no help keeping its children inside that budget. Each child accepts its ownmax_total_charge_usd, but splitting the parent's remaining budget across children, adjusting as earlier children finish under their cap, is left to the caller. The orchestrator skill (apify/agent-skills#90) lists this as a must-have, which means agents are currently writing it themselves.Depends on #1127: the remaining budget is the parent's limit minus what tracked children have charged so far, and only the registry knows the children after a restart.
Proposal
When the parent run has
maxTotalChargeUsdand a named child is started without an explicitmax_total_charge_usd, the SDK sets it to the parent's remaining budget (parent limit minus the sum ofusage_total_usd/ charged amounts of tracked children, minus the parent's own charge so far). An explicitmax_total_charge_usdon the child is capped at the remaining budget rather than passed through.A
budget_per_childoption could let the caller reserve headroom for later children, but the default above already guarantees the subtree never exceeds the parent's limit.Longer term this is better enforced on the platform for a parent's whole subtree, but the SDK version works today.
✍️ Drafted by Claude Code