CutCaptchaToken
Solve CutCaptcha through your own proxy from the misery key and API key and get the token for the form. With the schema, an example and provider prices.
CutCaptchaToken solves CutCaptcha through your proxy and returns the token the page expects. CutCaptcha is a CAPTCHA widget that renders inside an iframe. The task takes the page URL, the misery key and the API key.
Use CutCaptchaTokenProxyLess when the site accepts a token solved from another address.
Proxy
task.proxy is required on this task type, and the provider solves from that address. Send the proxy you use for your own requests to the site, and keep one IP for the whole solve: see Keep the same IP for the whole solve.
Find the parameters
miseryKeyis the value of theCUTCAPTCHA_MISERY_KEYvariable defined on the page. Search the page source or the Console forCUTCAPTCHA_MISERY_KEY.apiKeyis thedata-apikeyattribute of the CAPTCHA iframe'sbody. It is also the name of the JavaScript file the page includes for the widget.websiteURLis the full URL of the page that shows the widget.
Use the token
Set the solution token as the value of the input with the id cap_token, then submit the parent form. If the page defines a callback function, such as capResponseCallback, you can call it with the token instead.
If the site rejects the token, check that the proxy kept one IP for the whole solve, then that miseryKey and apiKey come from the page that shows the widget.
Check Provider stats for live success rates and solve times before you pick a provider.
Supported Providers
| Provider | Price per 1,000 | Routing |
|---|---|---|
2Captcha | $1.45 | |
SolveCaptcha | $1.45 |
Request Schema
| Field | Type | Required | Description |
|---|---|---|---|
clientKey* | string | Yes | Your API key. Create one in a workspace of the AnySolver dashboard. Example: |
task* | object | Yes | The task body. Required fields depend on the task type. See Tasks for per-task schemas. View task properties |
settings | object | No | 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:
| Field | Type | Required | Description |
|---|---|---|---|
type* | Yes | ||
websiteURL* | URL | Yes | Full URL of the page where the CAPTCHA is displayed. Example: |
miseryKey* | string | Yes | Value of the Example: |
apiKey* | string | Yes | CutCaptcha API key: the Example: |
proxy* | string | object | Yes | Proxy the provider solves through, as a string or an object. See Proxy configuration. View proxy configurationExample: |
{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "CutCaptchaToken",
"websiteURL": "https://example.cc/foo/bar.html",
"miseryKey": "a1488b66da00bf332a1488993a5443c79047e752",
"apiKey": "SAb83IIB",
"proxy": "http://user:pass@1.2.3.4:8080"
}
}Optional fields are not guaranteed across providers
Response Schema
| Field | Type | Required | Description |
|---|---|---|---|
status* | Yes | Task status: "processing", "ready", or "failed". Example: | |
errorId* | Yes |
Example: | |
taskId | string | No | Unique identifier returned when the task was created. Example: |
errorCode | No | Machine-readable error code. Example: | |
errorDescription | string | No | Human-readable error message with resolution hints. Example: |
cost | number | No | Actual cost charged for this task in USD. Example: |
taskType | No | The type of CAPTCHA task to solve. Example: | |
provider | No | Provider that handled this task. While processing, the provider currently solving it. Example: | |
solution | object | No |
Solution Object Properties
The solution field contains an object with the following properties:
| Field | Type | Required | Description |
|---|---|---|---|
token* | string | Yes | The solved CAPTCHA token to submit with your form. Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |