A mathematical captcha is the "3 + 7 = ?" kind of image: a small arithmetic question painted into a picture. Send it to our API and the answer comes back as a string — it is the cheapest type we handle, one credit per solve.
It is one of the oldest CAPTCHA forms: the server picks a small arithmetic question and renders it into an image with distortion, noise and crossing lines, then expects the visitor to type the result. The question can be digits (7 + 5), English words (three + four) or Chinese numerals, and some sites ask for the sum of the digits already shown.
Doing it yourself means solving three problems at once: distortion and noise, fonts and rotation, and the arithmetic semantics (three + four has to become digits before you add them). A pay-per-solve endpoint removes the model and the maintenance, and a retry costs one credit.
No. Recognition only uses the image. You fetch the picture, submit it and put the answer back inside your own browser or scraper session — we never see or need your cookies or account.
curl -X POST https://fuckcaptcha.top/v1/recognition/textcaptcha \\
-H "Authorization: Basic $NSK_KEY" \\
-d '{"image_data":"<base64>"}'Charged per solve: one credit for each recognition request, and polling for the result is free. Signing up includes 200 free solves.
It is a special case: the image holds an arithmetic question instead of a random string, so the answer has to be worked out (three + four becomes 7). Our textcaptcha endpoint covers both, so you do not call a different type.
One credit, the cheapest tier we offer. Signing up includes 200 free solves, and failed solves are not charged.
Yes. Digit questions, English word questions, Chinese numeral questions and noisy or rotated images all go through the same endpoint.
The answer as a string, for example "7". On most sites you simply type that into the input box — there is no arithmetic left for you to do.
Yes — the browser extension recognises these and fills them in automatically, drawing on the same allowance as the API.