Check whether the CapSkip desktop app is running and reachable. Call this first when a solve fails unexpectedly, to tell "CapSkip is not running" apart from "the sitekey was wrong". Takes no arguments.

Read the text out of a distorted-text captcha image. Returns the recognized text, which you type into the page's captcha field. Proxies are not supported for image captchas.

Solve a Google reCAPTCHA v2 or v3 widget, including invisible and Enterprise variants. Returns a token to place in the page's "g-recaptcha-response" field before submitting the form. Read the sitekey from the page first — a guessed sitekey fails. Note that reCAPTCHA v3 returns a score assigned by Google; no solver can raise it.

Solve a Cloudflare Turnstile widget or interstitial challenge page. Returns a token for the page's "cf-turnstile-response" field. IMPORTANT: submit the token using the returned userAgent — Cloudflare rejects a token replayed under a different User-Agent. For an interstitial challenge page, also pass cdata and pagedata read from the page.

Solve a GeeTest v3 slide-puzzle captcha. Returns geetest_challenge, geetest_validate, and geetest_seccode to post back exactly as the site's own front-end would. IMPORTANT: the challenge value is single-use and expires in roughly a minute, so fetch gt and challenge from the page immediately before calling. A stale challenge is the most common failure.

Solve an ALTCHA proof-of-work challenge. ALTCHA is not a recognition captcha — there is nothing to read; the client brute-forces a number that satisfies a challenge, so a solve is deterministic and takes milliseconds. Give it either challenge_url (the endpoint the fetches from, which CapSkip will fetch) or challenge_json (the challenge document itself). Returns a token to put in the page's form field named altcha, verbatim. IMPORTANT: challenges expire quickly — some sites inside two minutes — so read the challenge immediately before calling and submit the token promptly. An expired challenge is rejected with a bare "verification failed" that looks exactly like a wrong answer.

Solve a Capy Puzzle captcha — a slide puzzle where a piece is dragged into a hole cut out of a photograph. IMPORTANT: unlike every other captcha tool here, the answer is NOT a single token. It is three values — captchakey, challengekey and answer — which all go into the target form, in fields named 'capy_captchakey', 'capy_challengekey' and 'capy_answer'. Submit the answer verbatim: it is the drag path the widget would have recorded, so trimming or re-encoding it invalidates the solve. The challenge key is single-use and short-lived, so submit promptly rather than caching the three values. A solve takes about two seconds — Capy refuses answers that arrive faster than a human could have produced them, so CapSkip holds the result back deliberately.

Solve a CaptchaFox challenge. CaptchaFox scores the browser itself rather than asking the visitor to read anything, so most solves draw no puzzle at all. Returns a token to put in the form field named 'cf-captcha-response', verbatim — it is verified server side against the session that produced it, so any edit invalidates it. IMPORTANT: the url must be the page the widget actually runs on. CaptchaFox checks it against the domains the key is registered for and refuses a mismatch permanently, not intermittently — so a sitekey that fails immediately and consistently usually means the wrong page URL, not a bad key. The result also carries the User-Agent the token was minted under; submit under that one, not your own.

Solve a Friendly Captcha proof-of-work challenge. Nothing is shown on screen — the widget does arithmetic instead of asking the visitor to do anything. IMPORTANT: two entirely different protocols ship under this one name, sharing a brand and a sitekey namespace and nothing else, and a sitekey does not tell you which a site uses. Send version (v1 or v2), or send module_script and let CapSkip read the version off the build the site loads. Solving the wrong one returns a well-formed token the site rejects, with nothing to indicate the version was the problem. The form field also differs by version: v1 uses 'frc-captcha-solution', v2 uses 'frc-captcha-response'. Solve time is not a constant — the service sets the difficulty per request — so budget for that rather than assuming a fixed duration.