Credit Basics
Credits represent how many requests you can make.
1 credit = 1 successful request, regardless of:
Request parameters
Target website
Response size
Session length
If a request is made and successfully processed, exactly one credit is consumed.
There are no hidden multipliers or variable pricing based on request complexity.
What Counts as a Request?
A request is counted when:
A connection is successfully established
The target responds to the request
Each request consumes 1 credit, whether it is:
A page load
An API call
A scraping request
A background HTTP request
What Does Not Affect Credit Usage
Credits are not affected by:
Request headers or parameters
Payload size
Page weight or assets
Duration of the request
Number of retries (if no successful request is completed)
As long as the request completes successfully, it counts as 1 credit.
How Threads Relate to Credits
Threads control how many requests run at the same time, not how many credits are charged.
1 thread → requests are sent one by one
10 threads → up to 10 requests can run in parallel
Even with 10 threads:
Each request still costs 1 credit
Threads only affect speed, not pricing
Trial Example: 1,000 Credits / 10 Threads
With the trial you can:
Make up to 1,000 successful requests
Run up to 10 concurrent requests at once
Example scenarios:
Usage Pattern | Threads | Credits Used |
100 sequential requests | 1 | 100 credits |
100 parallel requests | 100 | 100 credits |
Stress test with 10 threads | 10 | Credits consumed faster, cost unchanged |
Key Takeaways
1 credit = 1 request
Request parameters do not change credit cost
Threads affect concurrency, not credit consumption
The trial lets you test real usage patterns safely