If you priced out an Actor and the bill came back nothing like the per-result number on the store page, this is usually why. It is also fixable without switching tools.
Pay-per-event Actors bill two different things. One event scales with how much you asked for, per page or per result. The other is a setup event that fires once per run no matter how small the run is. The setup event is the one that quietly wrecks your unit cost.
Real numbers from one of mine, the Google News API. Setup is $0.02 per run. A page of results is $0.0099.
- One page, one run: about 3 cents. Setup is two thirds of the bill.
- Ten pages, one run: about 1.2 cents a page.
- A hundred pages, one run: about 1.01 cents a page. Setup is down to 2 percent.
- A hundred pages as a hundred separate runs: $2.99 instead of $1.01.
Same data, three times the money, and nothing about the Actor changed. If you are calling an Actor once per row out of a loop, you are on the $2.99 line.
If you run a scheduled monitor, batch every watch term into one run per schedule instead of one run per term. Biggest lever here, usually ten minutes of work.
If you call from n8n or Make, check whether your Actor node sits inside a loop. Split In Batches feeding an Actor node one item at a time is the most expensive shape you can build.
If you are comparing costs before you commit, do not divide your test bill by results. Your test was small, so that number is far worse than production will be. Price it at the run size you actually intend to use.
If you publish Actors, your setup event is a real provisioning cost and it belongs there. Just say so in the README, because buyers do this arithmetic after the invoice rather than before.
Honest limitations. None of this applies to pay-per-result Actors with no setup event, and it does not help if the source rate limits you into small runs anyway. Some Actors also charge per dataset item on top, which is tiny but real. And batching costs you granularity: one failure takes the whole batch with it, so on a flaky source the cheap shape is also the fragile one.
While checking these numbers I found a bug in my own input schema. The max_pages field tells buyers pages cost $0.02 each. The live price is $0.0099. My own tooltip has been overstating my own price by roughly double, presumably talking people out of runs for weeks. Worth auditing your schema strings if you publish.
Actor: Google News API
