[ 01 ]What it looks like
Nothing at all: the page scores behaviour in the background and returns 0.0 to 1.0.
Captcha type · Google
reCAPTCHA v3 tokens returned at score 0.7 or above, or the task is not billed. Bind your own action name and request a higher minimum score per task.
Also searched asscore-based reCAPTCHAreCAPTCHA v3 scorepageAction tokenminScore 0.9frictionless reCAPTCHA
[ 01 ]What it looks like
Nothing at all: the page scores behaviour in the background and returns 0.0 to 1.0.
[ 02 ]Why it is hard
There is nothing to solve. The deliverable is a token carrying a high score, and the score comes from IP reputation, cookie age, browser entropy and how closely pageAction matches what the backend expects. A structurally valid token scoring 0.1 is worthless, so the real unit of work is the score band rather than the solve.
[ 03 ]How we solve it
Sessions are warmed on matched residential exits before a token is minted, and the action string you send is bound into the execute call rather than defaulted. You pick the band with minScore at 0.3, 0.7 or 0.9, and the token comes back at or above it. If the band cannot be reached, the task is returned unbilled instead of delivered at a lower score.
[ 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": "RecaptchaV3TaskProxyless",
"websiteURL": "...",
"websiteKey": "...",
"pageAction": "...",
"minScore": "..."
}
}'Required parameters
[ 03 ]Where this one shows up
Web Scraping & Data Collection
Keep a crawl moving when challenges start firing at volume.
QA & Test Automation
Run signup and checkout specs in CI instead of skipping them.
AI Agents & Browser Automation
One tool call returns a token and the agent keeps going.
Security Research & Pentesting
Authorised testing, where a challenge hides the attack surface.
Ad Verification & Brand Protection
Check live placements from the consumer’s geo, continuously.
[ 05 ]Questions about this one
You set minScore per task at 0.3, 0.7 or 0.9. The token comes back at or above the band you asked for, or the task is not billed. Most sites gate somewhere near 0.5, so 0.7 is the usual choice.
Almost always the action string. pageAction has to match exactly what the site passes to grecaptcha.execute, because the backend compares it during assessment. A token minted for the action homepage fails on a login endpoint even at score 0.9.
$2.18 per 1,000 tokens at the requested band. Median 5.6 seconds, 95th percentile 12.4 seconds. Higher bands sit nearer the upper end of that range because the session has to be warmed further before the token is minted.
Invisible v2 still has a challenge behind it and a pass or fail outcome. v3 never challenges anyone, it only emits a score, so there is nothing to solve and the deliverable is a token in a score band. They are separate sitekeys and separate task types.
Create a key, paste it into the sample above, and watch a real token come back. No card, no sales call.