Skip to Content
AnySolver logo
AnySolver
Recognition

HumanRecognition

Have human workers read and transcribe a CAPTCHA image, with instructions and answer constraints. Shows the request schema, an example and provider prices.

HumanRecognition sends the CAPTCHA image to human workers, who type the text back in solution.text. Use it when TextRecognition does not read the image correctly or when the image needs instructions, such as colour rules, a separate instruction image, or a math expression.

A distorted text CAPTCHA image

Guide the worker

Set the fields that match the image you know, so the workers get it right.

FieldWhat it does
commentA text instruction shown to the worker, for example enter only the red characters.
imgInstructionsA separate base64 image shown next to the CAPTCHA, for when text is not enough.
mathSet to true when the image shows an expression. The worker returns the result (2+6= returns 8).
phraseSet to true when the answer has at least two words separated by a space.
caseSensitiveSet to true to make the worker keep the upper and lower case of the image.
numericThe character types of the answer: 0 no preference, 1 only numbers, 2 only letters, 3 only numbers or only letters, 4 numbers and letters.
minLengthThe minimum answer length. 0 means no limit.
maxLengthThe maximum answer length. 0 means no limit.
languagePoolRoutes the task to workers who speak a language. Accepted values depend on the provider.

languagePool takes en and rn on Anti-Captcha, and language codes such as en, ru or zh on 2Captcha. Providers support different subsets of these fields. Anti-Captcha supports only numeric values 0 to 2; AnySolver treats 3 and 4 as 0 for it.

Check Provider stats for live success rates and solve times before you pick a provider.

Supported Providers

ProviderPrice per 1,000Routing
2Captcha
$0.50–$1.00
Anti-Captcha
$0.70
SolveCaptcha
$0.35

Request Schema

FieldTypeRequiredDescription
clientKey*
stringYes

Your API key. Create one in a workspace of the AnySolver dashboard.

Example: your-api-key-from-dashboard

task*
objectYes

The task body. Required fields depend on the task type. See Tasks for per-task schemas.

View task properties
settings
objectNo

Per-request settings for routing, Auto Retry, Auto Fallback, proxy reuse, response statistics and detailed analytics. Each field overrides the API key's value. See Routing modes.

View settings reference

Task Object Properties

The task field accepts an object with the following properties:

FieldTypeRequiredDescription
type*
Yes
imageBase64*
stringYes

Base64-encoded captcha image that a human worker will read and transcribe.

Example: /9j/4AAQSkZJRgABA...

websiteURL*
URLYes

Page URL where the captcha appears. Not every provider forwards it.

Example: https://example.com/login

comment
stringNo

Text instruction for the worker describing what to enter, for example enter only the red characters or ignore the strikethrough text.

Example: enter only the red characters

imgInstructions
stringNo

Separate base64-encoded instruction image shown alongside the captcha as a visual reference. Use when the captcha format is unusual and workers need an example of what to look for.

phrase
booleanNo

When true, the answer must contain at least two words separated by a space.

caseSensitive
booleanNo

When true, workers must preserve upper and lowercase exactly as shown in the image.

numeric
numberNo

Expected character types in the answer. 0 = no preference, 1 = numbers only, 2 = letters only, 3 = only numbers or only letters, 4 = must contain both numbers and letters.

Example: 0

math
booleanNo

When true, the captcha shows a math expression and the worker returns the calculated result (e.g. 2+6= returns 8).

minLength
numberNo

Minimum expected answer length. 0 means no constraint.

Example: 0

maxLength
numberNo

Maximum expected answer length. 0 means no constraint.

Example: 0

languagePool
stringNo

Routes the task to a worker pool by language. The accepted values depend on the provider: Anti-Captcha takes en (English) and rn (Russian, Ukrainian, Belorussian, Kazakh); 2Captcha takes language codes such as en, ru, es or zh.

Example: en

{
    "clientKey": "YOUR_API_KEY",
    "task": {
        "type": "HumanRecognition",
        "imageBase64": "/9j/4AAQSkZJRgABA...",
        "websiteURL": "https://example.com/login"
    }
}

Optional fields are not guaranteed across providers

Required fields are guaranteed across every provider that supports this task. Optional fields may be honored by some providers and silently ignored by others. AnySolver does not document per-provider parameter support, so before relying on an optional field, check that provider's own docs for the task you are using.

Response Schema

FieldTypeRequiredDescription
status*
Yes

Task status: "processing", "ready", or "failed".

Example: ready

errorId*
Yes

0 on success; 1 or 2 on an error. Branch on errorCode: Error IDs explains the two error groups.

Example: 0

taskId
stringNo

Unique identifier returned when the task was created.

Example: 01KFNDF328KAN2AJ3BNHCQYE88

errorCode
No

Machine-readable error code.

Example: CAPTCHA_UNSOLVABLE

errorDescription
stringNo

Human-readable error message with resolution hints.

Example: The captcha could not be solved.

cost
numberNo

Actual cost charged for this task in USD.

Example: 0.002

taskType
No

The type of CAPTCHA task to solve.

Example: ReCaptchaV2TokenProxyLess

provider
No

Provider that handled this task. While processing, the provider currently solving it.

Example: Multibot

solution
objectNo

Solution Object Properties

The solution field contains an object with the following properties:

FieldTypeRequiredDescription
text*
stringYes

Text from the captcha image as entered by the human worker.

Example: W68HP

raw*
Record<string, unknown>Yes

Raw provider response data for advanced use cases.