AltchaToken
Solve ALTCHA proof-of-work challenges through your own proxy from the challenge JSON and get the payload to submit. With the schema, example and prices.
AltchaToken solves the ALTCHA challenge you send, through your proxy, and returns the payload to submit with the form. ALTCHA is an open-source, proof-of-work CAPTCHA: the altcha-widget web component fetches a challenge from the site's server, solves it in the browser, and submits the result in a hidden form field named altcha by default.

Use AltchaTokenProxyLess when the site accepts a solution computed 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
The challenge URL is in the challenge attribute of the <altcha-widget> element (challengeurl on older versions), or in the widget's configuration. Open that URL, or watch the Network tab as the widget loads, to see the challenge response.
challengeJSONis the response of that request as a string. It carriesalgorithm,challenge,saltandsignature, andmaxnumberwhen the challenge has one. Fetch a new challenge for every task, because challenges expire and the server signs each one. Check that the challenge haschallenge,saltandsignaturefields before you create the task.challengeURLis optional. Providers solve thechallengeJSONyou send and do not fetch this URL.maxnumberis optional, and only some providers read it. Those use it instead of themaxnumberinchallengeJSON.
Challenge format
The task expects a challenge with challenge, salt and signature fields. Newer ALTCHA versions can issue
challenges with a different layout, such as the parameters object with PBKDF2/SHA-256. Check the challenge the
site returns before you create the task.
Use the token
The solution token is the payload for the form field the widget fills, altcha by default. Most providers return it Base64-encoded, and some return the solved JSON object as a string. Set it as the value of that field, or send it in the request where the page sends the widget's value, before you submit.
If the site rejects the payload, fetch a new challenge and create a new task, and check that the proxy kept one IP for the whole solve.
Check Provider stats for live success rates and solve times before you pick a provider.
Supported Providers
| Provider | Price per 1,000 | Routing |
|---|---|---|
2Captcha | $2.99 | |
Anti-Captcha | $2.00 | |
CapMonster | $0.80 | |
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: |
challengeJSON* | string | Yes | Challenge JSON returned by the challenge URL, as a string, with Example: |
proxy* | string | object | Yes | Proxy the provider solves through, as a string or an object. See Proxy configuration. View proxy configurationExample: |
challengeURL | string | No | URL the widget fetches the challenge from (the Example: |
maxnumber | number | No | Maximum puzzle number of the challenge. Only some providers read it: they use it instead of the Example: |
{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "AltchaToken",
"websiteURL": "https://example.com/contact",
"challengeJSON": "{\"algorithm\":\"SHA-256\",\"challenge\":\"4f2d...\",\"maxnumber\":50000,\"salt\":\"8b9a...\",\"signature\":\"MEUCIQ...\"}",
"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 | ALTCHA payload to submit to the target site, usually in the Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |
userAgent | string | No | User-Agent string used during solving. |