Changelog · July 18, 2026
Failed requests are never charged
You pay for answers, not for attempts.
By Roger Campos · Last updated: July 2026
TL;DR
A failed analysis never costs you anything, whatever the reason: a DNS failure, a timeout, a connection or TLS error, an error of ours, or the target site's own 4xx or 5xx. A target that answers 404 or 500 is now reported as a failed request with a 422 instead of its error page being returned as a successful result.
Free plan, no credit card. 1,000 credits a month.
Usage counts only requests that produced a result. A target's 4xx or 5xx used to come back as a "successful" page that was really the site's error page; it is now a failed analysis with a neutral error kind — not_found for a 404, internal_server_error for a 5xx, bad_request for any other 4xx — answered with a 422.
The same rule holds everywhere it was later extended: a bot check we couldn't clear, a robots.txt refusal, a residential request with no exit available and a screenshot option that couldn't be met are all free.
Endpoints
The endpoints on this page
- Get the rendered HTML of any URL
Paste a link and get the page's HTML after JavaScript has run and redirects have been followed — the DOM a real browser sees, not the empty shell curl returns.
Try it free - Check any website for JavaScript errors
Paste a link and see the console errors, warnings and uncaught exceptions logged while the page loads in a real browser — no DevTools, no local setup.
Try it free
FAQ
Frequently asked questions
Am I charged if the target site returns a 404?
Is a timeout billed?
How do I tell a failed request from a result?
Try it on the free plan.
Free plan, no card. Confirm your email and your API key is live — you'll be making real requests in minutes.