How do I know a site is Enterprise vs. standard v3?

Look at the script tag: /recaptcha/enterprise.js = Enterprise, /recaptcha/api.js = standard. Also, sites using Enterprise usually call grecaptcha.enterprise.execute() instead of grecaptcha.execute().

Why use the Enterprise task type instead of isEnterprise: true?

Both work; the Enterprise task type makes your intent explicit and routes to the Enterprise-tuned scoring path. Use whichever reads more clearly in your code.

Will my score be different from standard v3?

Enterprise risk analysis can be stricter on flagged IPs and browser signals. Expect slightly lower scores than standard v3 on the same IP — the same as a real user would experience.

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.

pageAction must match the site's real action. Enterprise sitekeys are stricter than standard v3 about action mismatches — use the exact string the site's JS passes to grecaptcha.enterprise.execute().
websiteURL must be the exact page URL where reCAPTCHA Enterprise loads. Domain-only URLs or wrong paths produce invalid tokens.
Proxy quality is the #1 factor in your score. Google's Enterprise risk analysis is harsher on flagged IPs than standard v3 — a high-reputation IP from your own provider will always score higher than the ProxyLess path.
Don't use the standard ReCaptchaV3Task type — Enterprise sitekeys require the Enterprise task type (ReCaptchaV3EnterpriseTask or ReCaptchaV3EnterpriseTaskProxyLess). Using the wrong type produces a token Google rejects.

reCAPTCHA v3 Enterprise

ReCaptchaV3EnterpriseTaskProxyLess

reCAPTCHA v3 Enterprise Solver, solved in 5.0s.

Bypass reCAPTCHA v3 Enterprise with AI-generated tokens. Same 0.0-1.0 scoring as standard v3, with additional Enterprise-only risk signals.

Get API Key Try Demo Examples

Avg Speed~5.0s

Success99%+

Cost / 1k$2.00

Throughput12/m

reCAPTCHA v3 Enterprise is Google's paid tier of v3 — same invisible scoring model (0.0 bot to 1.0 human), same grecaptcha.execute() API, but loads from /recaptcha/enterprise.js and includes additional risk signals that Google only exposes to Enterprise customers. If a site's JavaScript loads enterprise.js or the sitekey was registered as Enterprise in Google's admin console, standard v3 tokens will not verify — you need the Enterprise task type.

Quick Integration

solve.py

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": "ReCaptchaV3EnterpriseTaskProxyLess",
        "websiteURL": "https://example.com/login",
        "websiteKey": "6LcR_RsTAAAAADHmXXPJh-Lr7Mz4aCezAo3vKWiq",
        "pageAction": "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 the result

use_result.py

# Step 3: Use the result — paste the token into g-recaptcha-response
token = result["solution"]["gRecaptchaResponse"]
# Browser side: document.querySelector('textarea[name="g-recaptcha-response"]').value = token
# Or include it in your form POST:
resp = requests.post("https://target.example.com/login", data={
    "username": "...",
    "password": "...",
    "g-recaptcha-response": token,
})
print(resp.status_code)

1. Send Payload

Dispatch your ReCaptchaV3EnterpriseTaskProxyLess to our processing cluster via the secure API endpoint.

2. Solving Engine

Capzy's proprietary solver returns valid reCAPTCHA v3 Enterprise tokens. Same operational guarantees as standard v3 — score depends on the requesting IP, so use the Task variant with your own proxy when score sensitivity matters.

3. Get Result

Poll getTaskResult for the validated token, then finalize your automated request.

Using your own proxy

Use ReCaptchaV3EnterpriseTask instead of ReCaptchaV3EnterpriseTaskProxyLess to route the solve through your own proxy — useful when the target site checks that the solving IP matches the submitting IP.

solve_proxy.py

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": "ReCaptchaV3EnterpriseTask",
        "websiteURL": "https://example.com/login",
        "websiteKey": "6LcR_RsTAAAAADHmXXPJh-Lr7Mz4aCezAo3vKWiq",
        "pageAction": "login",
        "proxyType": "http",
        "proxyAddress": "123.45.67.89",
        "proxyPort": "8080",
        "proxyLogin": "user",
        "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

fieldtyperequireddescription

proxyTypetypestringreqyesProxy protocol: http, https, socks4, or socks5

proxyAddresstypestringreqyesProxy IP address or hostname

proxyPorttypenumberreqyesProxy port number

proxyLogintypestringreqnoProxy username (if auth required)

proxyPasswordtypestringreqnoProxy password (if auth required)

userAgenttypestringreqnoUser-Agent string to use. Must match the UA you use when submitting the token

Task Parameters

API Spec

fieldtyperequireddescription

typetypestringreqyesReCaptchaV3EnterpriseTaskProxyLess or ReCaptchaV3EnterpriseTask

websiteURLtypestringreqyesThe URL of the page where reCAPTCHA v3 Enterprise is loaded

websiteKeytypestringreqyesThe Enterprise sitekey (starts with 6L...)

pageActiontypestringreqnoThe action passed to grecaptcha.enterprise.execute(). Must match the site's JS

websiteTitletypestringreqnoThe page's document.title. Lets the solver present a document that matches your site for a more coherent solve. Optional but recommended.

enterprisePayloadtypeobjectreqnoExtra Enterprise parameters merged into grecaptcha.enterprise.execute(), e.g. { s: '...' }.

userAgenttypestringreqnoThe User-Agent to mint the token under. Send the same UA from your backend if siteverify enforces UA binding.

cookiestypearrayreqnoCookies to load before the solve, each { name, value, domain, path }.

minScoretypenumberreqnoMinimum score required (0.1-0.9). When set ≥ 0.7, routes through the high-quality solver path and is billed at 2× the standard rate. Omit for the standard tier.

Response Shape

fieldtypedescription

gRecaptchaResponsetypestringThe solved Enterprise token — submit to your Enterprise siteverify endpoint

userAgenttypestringThe 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).

Example response

{
  "errorId": 0,
  "status": "ready",
  "solution": {
    "gRecaptchaResponse": "03AGdBq25...<long Enterprise v3 token>...",
    "userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36",
    "expireTime": 1735689720000
  }
}

Error response

{
  "errorId": 1,
  "errorCode": "ERROR_CAPTCHA_UNSOLVABLE",
  "errorDescription": "Solver gave up."
}

Features

Enterprise-specific bundle (enterprise.js)

Correct grecaptcha.enterprise.execute() invocation

pageAction support — stricter matching than standard v3

Bring your own proxy on the Task variant

Drop-in compatible with Google Enterprise siteverify

Pricing & Stats

Per 1,000 solves$2.00

Avg solve time~5.0s

Success rate99%+