[ 01 ]What it looks like
Two or three picture fragments you drag into their slots on a forum or CMS form.
Captcha type · KeyCaptcha
KeyCaptcha drag-puzzle challenges solved from the four s_s_c parameters on the page. Returns the token the form expects.
Also searched askeycaptcha bypasskeycaptcha puzzle solvers_s_c_user_id parameterkeycaptcha drag puzzlekeycaptcha automation python
[ 01 ]What it looks like
Two or three picture fragments you drag into their slots on a forum or CMS form.
[ 02 ]Why it is hard
The puzzle itself is trivial. The work is in four page-embedded values (s_s_c_user_id, s_s_c_session_id, s_s_c_web_server_sign, s_s_c_web_server_sign2): they are session-scoped, must all come from the same page render, and a token built from a mismatched set is rejected without an error message. They rotate on every load, so a cached set never works.
[ 03 ]How we solve it
You post the four s_s_c values with the page URL and we return the finished token string for the hidden field. A dedicated worker pool covers the type, so low volume does not translate into long queues. If the target binds the session to an exit IP, the proxy variant of the task runs the solve through your own proxy instead.
[ 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": "KeyCaptchaTaskProxyless",
"websiteURL": "...",
"userId": "...",
"sessionId": "...",
"webServerSign": "..."
}
}'Required parameters
[ 05 ]Questions about this one
$4.49 per 1,000 successful solves. Failed solves are not billed, so the rate is per token delivered rather than per request submitted.
Median 3.4s, 95th percentile 7.8s. It is one of the faster types on the rate card because the puzzle is short and the answer is a fixed string, not a behavioural trace.
Not for KeyCaptchaTaskProxyless. Use the proxy task type only when the target ties the s_s_c session to the IP that requested the page, which is uncommon on the forum and CMS deployments where this type lives.
They are written into the page by the KeyCaptcha script block, usually as inline JavaScript above the form. Read all four from the same response you are going to submit against, and do not reuse them on a second request.
Create a key, paste it into the sample above, and watch a real token come back. No card, no sales call.