[ 01 ]What it looks like
Usually nothing; a flagged session gets a custom-branded grid or drag task, often mid-checkout.
Captcha type · Intuition Machines
Signed rqdata, matched proxy and matched user agent handled end to end. The hCaptcha variant most services quote at zero because they cannot solve it.
Also searched ashCaptcha rqdatahCaptcha enterprisePayloadhCaptcha Managed Defenseinvisible hCaptcha Enterprisehsw token
[ 01 ]What it looks like
Usually nothing; a flagged session gets a custom-branded grid or drag task, often mid-checkout.
[ 02 ]Why it is hard
Enterprise keys have the site’s own backend sign a per-session rqdata blob; a token minted without that exact value fails verification even when every image was right. Challenge sets are commissioned per customer, so there is no public label vocabulary to pretrain on. Scoring also runs at journey level across the session, which means the IP and user agent that requested the challenge must match the ones that submit the token.
[ 03 ]How we solve it
rqdata is passed through verbatim in enterprisePayload: we re-sign nothing and rewrite nothing, which is what keeps the token valid at the site’s backend. Your proxy and your user agent string are used for the whole solve, so the session the site scores is the session you submit from. Custom challenge sets go to the dedicated worker pool first and feed the retraining set, so a new customer’s puzzle stops being a cold start after the first few hundred solves.
[ 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": "HCaptchaEnterpriseTask",
"websiteURL": "...",
"websiteKey": "...",
"enterprisePayload": "...",
"proxy": "..."
}
}'Required parameters
[ 05 ]Questions about this one
Enterprise keys have the site’s backend sign a per-session rqdata blob that the widget sends along with the challenge request. A token minted without that exact blob is rejected at verification even when the images were answered correctly. Read rqdata out of the page and pass it through in enterprisePayload.
Most do not price it at all. 2Captcha has no current hCaptcha row on its rate card, and vendors that do list Enterprise usually quote it at the standard hCaptcha rate without supporting signed rqdata, so the tasks return tokens the site then rejects. We price it separately at $4.49 per 1,000 because it is a different job.
Yes. Enterprise scoring compares the IP and User-Agent that requested the challenge against the ones that submit the token. Pass the same proxy and the same user agent string your client will use for the submit, or the token is scored as a mismatch.
Standard hCaptcha checks a sitekey and returns a token any client can post. Enterprise adds signed rqdata, custom challenge sets and journey-level scoring. If your standard tasks return tokens that the site then refuses, or you can see an rqdata field in the page, you are on an Enterprise key.
Create a key, paste it into the sample above, and watch a real token come back. No card, no sales call.