Billing Overview
When using the Scrapingbypass SDK, credit consumption is calculated based on the total volume of network activity generated to complete your request. Unlike the standard API, the SDK accounts for multi-hop navigation and automated challenge resolution.
Consumption Breakdown
- Request Base Fee: 1 credit per request.
- This applies to every individual HTTP request initiated by the SDK.
- Redirects: Each redirect (e.g., 301 or 302 status codes) is counted as a separate request and consumes 1 credit per hop.
- Challenge Resolution Fee: 2 credits per challenge.
- When the SDK detects a Cloudflare JS Challenge, Turnstile, or WAF barrier, it automatically triggers the solving engine.
- Each successful solve incurs a flat fee of 2 credits, independent of the base request fee.
Calculation Logic Example
| Action Sequence | Credit Cost | Total |
|---|---|---|
| Initial request triggers a JS Challenge | 1 (Request) + 2 (Challenge) | 3 |
| Target site redirects to a login page | 1 (Redirect) | 1 |
| Total Session Cost | 4 Credits |
Key Considerations
- Successful Execution Only: Credits are only deducted when the SDK successfully handles the request or challenge.
- Granular Billing: Because the SDK operates at a lower level than the V2 API, it provides more transparency into how credits are applied during complex navigation flows.
- Session Reuse: To minimize costs, maintain persistent sessions within the SDK to reduce the frequency of re-triggering challenges.
Technical Note on Redirects
If your target URL involves multiple redirects (e.g., a tracking link leading to a landing page), ensure your credit balance is sufficient to cover the total number of hops in the chain.
