Billing design
No payments or paid API calls are available in this preview. The following describes the design.
Before execution
Section titled “Before execution”Validate the input, source support and spending ceiling. The task’s maximum authorized charge is reserved from available balance before work begins. A reservation is not an additional fee.
At settlement
Section titled “At settlement”Charge the delivered quantity at the task’s published price version and release unused reserved balance. For Job Scraper, the unit is a delivered record. Source failure, exclusions and a completed search with no matches are not billed as delivered records.
Price transparency
Section titled “Price transparency”Publish each operation’s billing unit and rate before it opens. Do not treat an illustrative $0.003-per-record sample as a live price. Duration-based operations will specify their duration definition and rounding rules.
Repeated reads
Section titled “Repeated reads”Reading the same stored result does not start another collection. A new collection is a new request requiring its own authorization and budget.
See the pricing approach for the preview account defaults and release boundaries.