Before you submit — these must be correct
If any of these are wrong, your token may be accepted by our solver but rejected or scored poorly by the target site. We can’t detect these mismatches for you.
- pageAction must match the site's real action. Google scores the token against the action you request — if the site calls grecaptcha.execute(sitekey, {action: 'login'}) and you send pageAction: 'verify', the score will drop. Inspect the site's JS for the exact string. We default to 'verify' only when none is provided.
- websiteURL must be the exact page URL where reCAPTCHA loads. Domain-only URLs or wrong paths cause invalid tokens — use the full URL of the page that contains the widget.
- Proxy quality is the #1 factor in your score. Google evaluates the IP that fetches /recaptcha/api2/*. Shared proxyless pools (including ours and every other provider) produce lower scores than a dedicated residential or mobile IP you supply yourself. For 0.7-0.9 scores on strict sitekeys, use ReCaptchaV3Task with your own residential or mobile proxy.
- isEnterprise must match the site. Enterprise v3 uses a different bundle (enterprise.js) and scoring endpoint. Setting it wrong will produce an invalid token.
What is reCAPTCHA v3?
reCAPTCHA v3 is Google's invisible captcha that runs in the background without user interaction. Instead of showing a challenge, it analyzes user behavior and returns a risk score between 0.0 (bot) and 1.0 (human). Websites set a threshold (typically 0.3-0.7) and block requests below it. Unlike v2, there's no checkbox or image puzzle — the captcha is completely invisible. This makes it harder to detect but also harder to bypass, since you need to produce a token that results in a high enough score.
How It Works
Send Task
POST your ReCaptchaV3TaskProxyLess with the target URL and sitekey to our API. We'll queue it instantly.
We Solve
Capzy's proprietary solver returns valid reCAPTCHA v3 tokens. Final score is determined by Google when your backend calls siteverify — the score depends heavily on the IP that makes the request, so for the highest scores use ReCaptchaV3Task with your own residential proxy.
Get Token
Poll getTaskResult — when status is 'ready', the solution contains the token to inject into the target page.
Quick Integration
import requests, time
API = "https://api.capzy.ai"
KEY = "capzy_your_key_here"
# Step 1: Create task
task = requests.post(f"{API}/createTask", json={
"clientKey": KEY,
"task": {
"type": "ReCaptchaV3TaskProxyLess",
"pageAction": "login",
"websiteKey": "6LcR_RsTAAAAADHmXXPJh-Lr7Mz4aCezAo3vKWiq",
"websiteURL": "https://example.com/login"
}
}).json()
task_id = task["taskId"]
print(f"Task created: {task_id}")
# Step 2: Poll for result
while True:
result = requests.post(f"{API}/getTaskResult", json={
"clientKey": KEY,
"taskId": task_id
}).json()
if result["status"] == "ready":
print("Solved!", result["solution"])
break
elif result["status"] == "failed":
print("Failed:", result.get("errorDescription"))
break
time.sleep(1)Using Your Own Proxy
Use ReCaptchaV3Task instead of ReCaptchaV3TaskProxyLess to route the solve through your own proxy. This is useful when the target site checks the IP that solved the captcha matches the IP submitting the form.
import requests, time
API = "https://api.capzy.ai"
KEY = "capzy_your_key_here"
# Step 1: Create task
task = requests.post(f"{API}/createTask", json={
"clientKey": KEY,
"task": {
"type": "ReCaptchaV3Task",
"proxyPort": "8080",
"proxyType": "http",
"pageAction": "login",
"proxyLogin": "user",
"websiteKey": "6LcR_RsTAAAAADHmXXPJh-Lr7Mz4aCezAo3vKWiq",
"websiteURL": "https://example.com/login",
"proxyAddress": "123.45.67.89",
"proxyPassword": "pass"
}
}).json()
task_id = task["taskId"]
print(f"Task created: {task_id}")
# Step 2: Poll for result
while True:
result = requests.post(f"{API}/getTaskResult", json={
"clientKey": KEY,
"taskId": task_id
}).json()
if result["status"] == "ready":
print("Solved!", result["solution"])
break
elif result["status"] == "failed":
print("Failed:", result.get("errorDescription"))
break
time.sleep(1)additional proxy parameters
proxyTypetypestringreqyesProxy protocol: http, https, socks4, or socks5proxyAddresstypestringreqyesProxy IP address or hostnameproxyPorttypenumberreqyesProxy port numberproxyLogintypestringreqnoProxy username (if auth required)proxyPasswordtypestringreqnoProxy password (if auth required)userAgenttypestringreqnoUser-Agent string to use. Must match the UA you use when submitting the tokentask parameters.
typetypestringreqyesReCaptchaV3TaskProxyLess or ReCaptchaV3TaskwebsiteURLtypestringreqyesThe URL of the page where reCAPTCHA v3 is loadedwebsiteKeytypestringreqyesThe sitekey found in the page source (starts with 6L...)pageActiontypestringreqnoThe action parameter passed to grecaptcha.execute(). Found in the site's JS codeisEnterprisetypebooleanreqnoSet true if the site uses reCAPTCHA Enterprisesolution response.
gRecaptchaResponsetypestringThe solved token — submit this in the g-recaptcha-response field or the callback parameteruserAgenttypestringThe User-Agent string the solver used to mint the token. Submit it from the same UA on your backend if Google's siteverify enforces UA binding.expireTimetypenumberUnix milliseconds when the token expires (issued time + 120s — Google v3 tokens have a 2-minute lifetime).Features
ProxyLess Task Type
ReCaptchaV3TaskProxyLessWith Proxy
ReCaptchaV3TaskFrequently Asked Questions
start solving recaptcha v3.
$0.10 in free credits — no card. ~250 free solves to test before you spend.