Skip to Content
AnySolver logo
AnySolver
Recognition

CoordinatesRecognition

Get click coordinates on an image from a human worker. Covers the request schema, an example and each provider's price per 1,000.

CoordinatesRecognition asks a worker to click one or more points on an image and returns those points. Use it for click CAPTCHAs ("click on the green apple"), or to measure distances between points, for example to move a custom slider.

What the image should contain

Send the CAPTCHA image as base64 in imageBase64. A data-URI prefix is removed for you.

The worker sees only the image and your instruction, so crop it to the CAPTCHA itself.

Instructions

  • comment is the instruction, such as click on the green apple. Skip it when the image already contains the instruction. SolveCaptcha limits it to 140 UTF-8 characters, and Anti-Captcha expects English.
  • imgInstructions is a base64 image with the instruction, for challenges that show it as a graphic. 2Captcha and SolveCaptcha limit it to 100 kB, and SolveCaptcha also to 400x150 px. Anti-Captcha does not accept it.
  • minClicks and maxClicks bound the number of clicks. 2Captcha and SolveCaptcha accept them, with minClicks defaulting to 1. Anti-Captcha does not accept them.

Read the answer

coordinates is a list of { x, y } points in pixels, measured from the top-left corner of the image (x=0, y=0). Scale them if you resized the image before sending it. The points come in the order the provider returns them, so for ordered clicks use the order in the list.

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

Supported Providers

ProviderPrice per 1,000Routing
2Captcha
$1.20
Anti-Captcha
$2.00
SolveCaptcha
$1.20

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 to solve with click coordinates. A data-URI prefix is removed for you. 2Captcha documents JPEG, PNG or GIF up to 600 kB and 1000 px on any side; Anti-Captcha downscales images wider or taller than 500 px for its workers.

Example: iVBORw0KGgoAAAANSUhEUgAA...

comment
stringNo

Optional text instruction shown to the worker, for example click on the green apple. Use this when the image does not already contain the instruction. SolveCaptcha limits it to 140 UTF-8 characters and Anti-Captcha expects English.

Example: click on the green apple

imgInstructions
stringNo

Optional base64-encoded instruction image shown together with the captcha. Use this when the challenge provides a separate instruction graphic. 2Captcha and SolveCaptcha limit it to 100 kB, and SolveCaptcha also to 400x150 px. Anti-Captcha does not accept it.

Example: iVBORw0KGgoAAAANSUhEUgAA...instructions

minClicks
numberNo

Minimum number of clicks expected in the answer. 2Captcha and SolveCaptcha accept it and default to 1. Anti-Captcha does not accept it.

Example: 1

maxClicks
numberNo

Maximum number of clicks expected in the answer. 2Captcha and SolveCaptcha accept it; Anti-Captcha does not accept it.

Example: 3

{
    "clientKey": "YOUR_API_KEY",
    "task": {
        "type": "CoordinatesRecognition",
        "imageBase64": "iVBORw0KGgoAAAANSUhEUgAA..."
    }
}

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
coordinates*
object[]Yes

Click points in the order returned by the provider, in pixels from the top-left corner of the image (x=0, y=0).

Example: [{"x":39,"y":59},{"x":252,"y":72}]

raw*
Record<string, unknown>Yes

Raw provider response data for advanced use cases.