Credit Usage
The table below outlines the credit cost for a single successful request to each endpoint.| API Endpoint | Credits Per Request |
|---|---|
| DNS Lookup | 1 |
| DNSSEC Lookup | 1 |
| Site Load Time | 1 |
| URL Redirection | 1 |
| TLS Scan | 1 |
| Ping | 2 |
| MTR (Traceroute) | 2 |
| Port Scanner | 2 |
| Meta Scraping | 2 |
| Web Scraping | 2 |
| Proxy | 2 |
| Mixed Content | 2 |
| Screenshot | 5 |
| PDF Generator | 5 |
| Broken Link Checker | 5 |
| Lighthouse Audit | 10 |
Usage Mechanics
1. Calculation Logic
Credits are deducted immediately upon the successful execution of an API call. Example: If you make 10 calls to the Web Scraping API, you will consume
20 credits (10 calls × 2 credits). 2. Failed Requests
We value fairness. You are generally not charged for API errors caused by our infrastructure (HTTP 5xx status codes).- 4xx Errors: Requests that fail due to invalid user input (e.g., specific bad URLs, missing parameters, or unauthorized access) generally do not consume credits.
3. Proxy Usage (Add-on Cost)
The Premium Proxy feature costs 2 credits per request. This is an additional cost applied on top of the base API endpoint. The proxy feature can be enabled on various HTTP-based APIs (such as Web Scraping, Screenshot, and Headers). Please refer to our Using Proxies documentation for the full list of supported endpoints. Calculation Example: If you make a Web Scraping request and enable the Proxy feature:- Web Scraping Cost: 2 Credits
- Proxy Add-on Cost: + 2 Credits
- Total Consumed: 4 Credits