Unmetered traffic or a gigabyte package
A package looks cheaper at the moment of purchase. The figure that matters is the monthly consumption, and it usually reverses the answer.
What a run actually consumes
An average catalogue page weighs about 120 kilobytes. Two hundred thousand pages come to roughly 24 gigabytes per run.
At one run a week that is around a hundred gigabytes a month. On daily monitoring the figure passes a terabyte.
The part nobody counts
Retries after failures consume traffic too. At a five percent failure rate you pay for them exactly as for successful requests.
Images and scripts add more. If the collector pulls whole pages, real usage runs half again above the estimate. Switching off the extras cuts up to two thirds.
When a package wins
A one-off job with a known scope: collect, export, close. There a package genuinely costs less.
Read the terms for what happens when it runs out: some vendors stop access, others keep going at a higher rate.
Deciding in five minutes
Measure one real run and read the figure from the report. If you have several, size on the heaviest: the heavy month is exactly when a package ends early.
pages per run 200,000 page weight ~120 KB traffic per run ~24 GB runs per month 4 total ~96 GB