[ 01 ]What it looks like
A full-page Just a moment screen that spins for several seconds, then redirects to the real page.
Captcha type · Cloudflare
Full interstitial challenges solved and returned as a cf_clearance cookie bound to your IP. For the 403s that Turnstile solving will not fix.
Also searched ascf_clearance cookieJust a moment cloudflareCloudflare 5 second shieldManaged ChallengeCloudflare JS challengechecking your browser before accessing
[ 01 ]What it looks like
A full-page Just a moment screen that spins for several seconds, then redirects to the real page.
[ 02 ]Why it is hard
What you need here is not a token but the cf_clearance cookie, and Cloudflare binds that cookie to the exit IP, the TLS fingerprint and the user agent that earned it. Replay it from another IP or another HTTP client and it is rejected on the first request. The challenge itself also needs the action, cData and chlPageData values read out of the interstitial, and those change on every page load.
[ 03 ]How we solve it
You pass your own proxy and we run the interstitial through that exact exit, so the cookie is issued to the IP you will actually scrape from. The response carries cf_clearance together with the user agent it was solved with, so you can pin both onto your session. Page type is detected from the challenge data rather than declared by you: non-interactive, Managed Challenge and Interactive Challenge escalate automatically inside one task.
[ 02 ]Solve it in five lines
Post the task, get the token. Our SDKs collapse creation, polling and retries into one call.
curl -s https://api.nexcaptcha.net/createTask \
-H "Content-Type: application/json" \
-d '{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "AntiCloudflareTask",
"websiteURL": "...",
"proxy": "..."
}
}'Required parameters
[ 03 ]Where this one shows up
[ 05 ]Questions about this one
A cf_clearance cookie plus the exact user agent the challenge was solved with. Set both on your session and keep requesting through the same proxy, and the interstitial stops firing. The cookie is Secure, SameSite=None and Partitioned, so it only travels over HTTPS.
Cloudflare binds it to the IP, the TLS fingerprint and the user agent that earned it. Reusing it from a different exit IP, a different HTTP client, or with a different User-Agent header invalidates it immediately. Pin one cookie to one proxy and one client.
Yes. The cookie is only useful on the IP it was issued to, so you supply the proxy and we solve through it. Residential and ISP exits clear noticeably more often than datacentre ranges on hardened sites.
$4.49 per 1,000 against $2.18 for the widget. The interstitial needs a full browser session held open on your proxy for the whole solve and returns a cookie rather than a token. Median is 8.2s, p95 is 19.5s and success is 97.6%; failed and timed-out tasks are not billed.
Create a key, paste it into the sample above, and watch a real token come back. No card, no sales call.