Your row budget stayed flat. Your scheduled starts multiplied.
You split a weekly company-directory refresh into smaller jobs, hoping to make failures less annoying. Then the event budget grows. The row allowance still looks innocent.
Splitting the same company-record allowance across more runs increases start-event fees. For Nimbryxo-studio's directory Actor, starts are memory-dependent, result events follow dataset items, and platform usage is charged separately.
Make the input part of the budget
Start with a restricted input your estimator actually understands. Supporting every mode would widen the billing assumptions before you need them.
Example: this input selects a bulk listing path, with enrichment explicitly disabled.
import assert from 'node:assert/strict' ; import { z } from 'zod' ; import pg from 'pg' ;
const BrowseInput = z . object ( { mode : z . literal ( 'browse' ) , location : z . literal ( 'chicago' ) , includeDetails : z . boolean ( ) , includeProfile : z .…