How the bandwidth estimate works
The calculator converts each response size to megabytes, multiplies it by request count, and adds the percentage you enter for retries and overhead. It uses decimal units: 1,000KB equals 1MB and 1,000MB equals 1GB.
The recommendation checks the exact unrounded estimate against the package data used by the store. If the estimate exceeds the largest package, the calculator says so instead of inventing another tier.
How to measure average response size
- Run a small sample with the same HTTP client or browser planned for production.
- Record transferred bytes, not only the uncompressed document or response body.
- Include representative successes, redirects, error pages, and downloads.
- Divide total transferred data by completed sample requests.
- Enter a retry allowance based on observed failures and normal request overhead.
Browser automation often transfers far more than a direct API request because supporting assets load through the proxy. If you block images, fonts, or media in the sample, only do so when the real workflow will use the same rules.
What the estimate does not guarantee
Actual metering can vary with headers, uploads, redirects, compression, retries, and upstream accounting. The estimate does not promise a number of successful results or uninterrupted routes. Validate it by comparing a small run with the balance shown in your dashboard.
Continue with the detailed bandwidth planning guide, review workflow-specific use cases, or use the setup documentation to configure a test connection.
