01
Request volume
Pages × sites × checks × active days gives the base number of monthly page loads.
FREE CAPACITY PLANNER
Estimate your scraping workload before you buy proxy capacity.
Turn pages, target sites, check frequency, retries, and rendering complexity into a transparent monthly credit estimate — in under a minute.
- No signup
- Shareable estimate
- Transparent formula
Build your workload estimate
Start with the number of pages you monitor, how often you check them, and how each page is loaded. Advanced settings add retry overhead and a safety buffer.
INSPECT EVERY ASSUMPTION
A capacity estimate you can audit
The result is not a black box. ScrapeBudget shows each part of the calculation so you can change assumptions and see exactly what moves the total.
02
Retry overhead
Timeouts, rate limits, and transient failures create extra attempts. Model that overhead before production.
03
Rendering complexity
Raw HTML may be close to one credit per request, while browser rendering can trigger many downstream assets.
04
Safety buffer
A configurable buffer reduces the chance of choosing a capacity tier that is too tight.
MATCH THE WORKFLOW
Capacity is only half of the decision
The correct proxy pattern depends on whether each page load is independent, whether a session must persist, and how aggressively the target protects access.
| Pattern | Best fit | Watch out for |
|---|---|---|
| Per-request rotating | Independent catalog pages, recurring public-data checks, distributed crawling | Not suitable when the same IP must persist across a multi-step session |
| Static dedicated | Stable IP identity, allowlisted APIs, long-running sessions | Smaller IP pool and more manual rotation logic |
| Static ISP | Sticky sessions and targets that place more trust in ISP-classified addresses | Usually more expensive than datacenter capacity |
Start with the least complex option that works, validate it against the real target, and scale only after measuring success rate and credit consumption.
A PRACTICAL SEQUENCE
Plan, test, measure, then scale
- STEP 1
Model the workload
Estimate page volume, check frequency, rendering mode, retries, and buffer.
- STEP 2
Choose a capacity range
Select a tier with enough headroom instead of buying directly against the base request count.
- STEP 3
Validate the target
Run a small test against the real pages. Measure successful responses, timeouts, blocks, and actual credits per useful result.
- STEP 4
Tune production
Reduce unnecessary assets, avoid browser rendering where raw requests work, and adjust pacing before adding more capacity.
PORTABLE BY DESIGN
Keep proxy configuration outside your scraper logic
Use an environment variable for the proxy URL, add explicit timeouts, and treat retries as measured overhead rather than an unlimited loop.
Use proxies only for lawful, authorized collection. Respect website terms, robots directives where applicable, rate limits, privacy obligations, and access controls.
import os
import requests
target_url = "https://example.com/public-page"
proxy_url = os.environ["PROXY_URL"]
response = requests.get(
target_url,
proxies={
"http": proxy_url,
"https": proxy_url,
},
headers={
"User-Agent": "YourApp/1.0 (+https://your-domain.example)"
},
timeout=30,
)
response.raise_for_status()
print(response.status_code)import { fetch, ProxyAgent } from "undici";
const targetUrl = "https://example.com/public-page";
const proxyUrl = process.env.PROXY_URL;
if (!proxyUrl) {
throw new Error("PROXY_URL is required");
}
const dispatcher = new ProxyAgent(proxyUrl);
try {
const response = await fetch(targetUrl, {
dispatcher,
headers: {
"user-agent": "YourApp/1.0 (+https://your-domain.example)",
},
signal: AbortSignal.timeout(30_000),
});
if (!response.ok) {
throw new Error(`Request failed: ${response.status}`);
}
console.log(response.status);
} finally {
await dispatcher.close();
}SPONSORED PROVIDER SNAPSHOT
A current capacity option
FineProxy currently offers per-request rotating datacenter plans from 2.5M credits to 400M credits, plus a small test allocation. A simple HTML or JSON request is approximately 1 credit. Browser-based loads can consume substantially more because downstream assets count separately.
Per-request rotation is designed for independent requests. If your workflow needs the same IP across login, navigation, or checkout steps, use a static or sticky option instead.
Source reviewed: Review the official source
COMMON QUESTIONS
Capacity planning, clarified
The short answers behind credits, request modes, safety buffers, and proxy patterns.
What is an API credit?
An API credit is a provider-specific unit used to measure request load. A simple request may use about one credit, while a page that loads scripts, images, fonts, APIs, and browser resources can use more.
Why can one page load consume multiple credits?
A browser-rendered page may trigger many downstream requests. If the provider counts those requests individually, one visible page can consume several credits.
Do failed requests count?
They can. Requests that reach provider infrastructure may consume capacity even when the target returns an error or times out. That is why the calculator includes retry overhead.
Which request mode should I choose?
Choose Raw HTML / JSON when one network response is enough. Choose Browser, no JavaScript for basic DOM loading. Use JavaScript rendering only when the page genuinely requires it. Select Heavy browser page when many assets and scripts are unavoidable.
How much safety buffer should I add?
Twenty percent is a reasonable planning default for an unmeasured workflow. Lower it after collecting reliable production data; increase it when targets are unstable or usage is close to a tier boundary.
Do I need rotating or static proxies?
Rotating proxies fit independent page loads. Static dedicated or ISP proxies are better when a workflow needs the same IP across multiple steps, account sessions, or allowlisted access.
Is this a price quote?
No. ScrapeBudget estimates request capacity. It does not quote provider pricing or guarantee actual credit consumption.
Does ScrapeBudget sell proxies?
No. ScrapeBudget is an independent planning tool. Some outbound provider links are sponsored affiliate links, which may earn us a commission at no additional cost to you.