Success-only billing
Proxy Compare records 1 of the 42 providers stating that they bill only for successful requests, read 5 Oct 2026. Check the definition of success and any billing exceptions. A returned response is not necessarily usable output.
Why it costs you money
The cost per usable page depends on which attempts are billed. A failed-request protection policy may exclude certain HTTP statuses or charge for requests you cancel early. Check those clauses before treating a successful-request billing statement as a cost guarantee. A credit price applies to the billed request; it does not predict how many attempts produce usable output. Compare the full subscription purchase and any charged extras against your own workload, with billable retries counted separately.
See it in the data
Related terms
- Success rateThe share of requests that get through. The number that decides everything, and the one no comparison table can give you.
- Credit (scraping API)Scraping APIs bill in credits, and one credit buys different amounts of work depending on the request. What each provider charges, with sources.
- Ban rateThe share of requests a target site refuses. The number that decides real cost, and the one nobody publishes.
- CAPTCHA rateHow often a target serves a challenge instead of the page. A softer signal than a ban and it costs the same bytes.
- Every term we define
Questions
Which providers here do it?
1 of the 42 providers state that they bill only for successful requests, read 5 Oct 2026. It is a scraping-API feature rather than a proxy one, which is why the count is small.
What counts as a success?
The provider defines the billable response. Review its treatment of error statuses, incomplete results and cancelled requests. A scraping API may include CAPTCHA handling in its request price; that does not automatically require an external solver purchase.
Is it worth a higher headline rate?
Compare the complete purchase against the requests your workload actually bills. A higher unit rate can cost less if it avoids charges on failed attempts, but the result depends on the policy and your workload. No failure rate is assumed here.