Requests & Threads Basics
Requests represent individual HTTP actions made through the scraper.
A request is any successfully processed interaction, such as:
A page load
An API call
A scraping request
A background HTTP request
Requests are unlimited
There are no request caps, no credit limits, and no per-request pricing. Our scraper now runs on a thread-based model. That means:
Unlimited requests
No credits
No hidden limits
You only choose how fast you want to go
What’s a Request?
A request is any successful action, such as:
Loading a webpage
Making an API call
Scraping data
Sending a background HTTP request
Requests are unlimited — you never run out, no matter how much you scrape.
No Credits. No Counting. No Surprises.
We’ve removed credit limits entirely.
Requests are not affected by:
Page size or assets
Request parameters or headers
Target website
Response size
Session length
Request duration
If it works, it works — and you don’t pay extra for it.
Threads = Speed Control
Threads define how many requests run at the same time.
Think of threads as lanes on a highway:
1 thread → steady, one-by-one scraping
10 threads → faster, parallel requests
More threads → maximum throughput
Threads affect speed, not cost per request.
Simple, Predictable Scaling
Want to scrape more data? → Run longer
Want to scrape faster? → Add more threads
Want full transparency? → It’s built in
There are no multipliers, no penalties for complexity, and no guesswork.
Example Usage
Threads | Behavior |
1 | Sequential requests |
10 | Up to 10 parallel requests |
100 | High-speed scraping at scale |
No matter the setup:
Requests stay unlimited
Pricing stays predictable