Skip to main content

Changelog · October 9, 2026

A sign-in form or an error page is a failure, not a result

Stop paying for, and storing, the page a site shows instead of yours.

By · Last updated: October 2026

TL;DR

A site that won't show a page doesn't always say so with a status code. When the answer is a 200 whose whole content is a notice that you are blocked, an error page saying the page does not exist, a sign-in form the visit was redirected to, or an application that never got past its loading screen, the request now fails with the matching error and costs nothing, on every endpoint that loads a page. Your pipeline stops storing a login form as an article.

Free plan, no credit card. 1,000 credits a month.

The errors are the ones a status code already produces: The requested page was not found, The page asked us to complete a bot check before it would load, The page could not be loaded. A sign-in wall has one of its own: The page asked us to sign in before it would show its content.

Only what is unmistakable is refused. A sign-in page you ask for by its own address is returned like any other page, and so is an article behind a paywall, as far as the site shows it to a visitor.

Endpoints

The endpoints on this page

FAQ

Frequently asked questions

No. Like every failed request, it costs nothing.

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.