capskip 1.2.0 → 1.4.0

package/docs/API_REFERENCE.md

@@ -9,7 +9,7 @@ POST http://<host>:<port>/in.php   → submit captcha
 GET  http://<host>:<port>/res.php  → poll result
 ```
 
-The SDK only supports the four captcha types documented by CapSkip. Every solve
+The SDK only supports the captcha types documented by CapSkip. Every solve
 method returns a `Promise`.
 
 ---
@@ -24,9 +24,14 @@ method returns a `Promise`.
 | Cloudflare Turnstile | `turnstile()` | `turnstile` |
 | GeeTest v3 (slide) | `geetest()` | `geetest` |
 | ALTCHA (proof-of-work) | `altcha()` | `altcha` |
+| Capy Puzzle (slide) | `capy()` | `capy` |
+| CaptchaFox (widget) | `captchafox()` | `captchafox` |
+| Friendly Captcha (proof-of-work) | `friendlyCaptcha()` | `friendly_captcha` |
+| AWS WAF (challenge page or widget) | `amazonWaf()` | `amazon_waf` |
 
-**Proxy** is supported for reCAPTCHA, Turnstile, GeeTest, and ALTCHA — not for image
-captcha. For ALTCHA the proxy is used only for the `challengeUrl` fetch.
+**Proxy** is supported for every method except image captcha. For ALTCHA the
+proxy is used only for the `challengeUrl` fetch; for Capy, only for the
+puzzle-image fetch, which is the only request a Capy solve makes.
 
 ---
 
@@ -377,6 +382,337 @@ purely visual and never reaches CapSkip.
 
 ---
 
+## 7. Capy Puzzle — `capy(sitekey, url, { ... })`
+
+Capy is a slide puzzle: a piece has to be dragged into the hole cut out of a
+photograph. CapSkip locates the hole and produces the drag path — one HTTP fetch
+plus pixel math, no browser.
+
+### POST `/in.php`
+
+| Parameter | Type | Required | Description |
+|---|---|---|---|
+| `key` | string | Yes | CapSkip API key |
+| `method` | string | Yes | `capy` |
+| `captchakey` | string | Yes | The site's public Capy key, conventionally prefixed `PUZZLE_`. The SDK sends its `sitekey` argument here. |
+| `pageurl` | string | Yes | Full URL of the page the captcha is on |
+| `api_server` | string | No | Root of the Capy API the key lives behind. Default `https://jp.api.capy.me` |
+| `version` | string | No | `puzzle` (the default). Only the puzzle family is solved |
+| `useragent` | string | No | User-Agent to send with the puzzle request |
+| `json` | int | No | `0` plain text, `1` JSON |
+| `proxy` | string | No | Proxy address |
+| `proxytype` | string | No | Proxy type |
+
+`sitekey` and `websiteKey` are accepted by the server as aliases for
+`captchakey`; the SDK sends the documented name.
+
+`version: 'avatar'` is refused by the SDK before the request is made. Avatar is a
+different challenge behind a different endpoint, and answering it with a puzzle
+answer would bill for a solve the target site rejects, indistinguishably from a
+broken solver.
+
+> `api.capy.me` no longer resolves, although several solver services still
+> document it. The live host is `jp.api.capy.me`; if a site's widget points
+> somewhere else, pass that as `api_server`.
+
+### Getting the captcha key
+
+It is in the page source as `capy_captchakey`, or in the widget script URL:
+`<script src="https://jp.api.capy.me/puzzle/get_js/?k=PUZZLE_XXXX">`.
+
+### GET `/res.php`
+
+The answer is **not a token**. It is an object, which the SDK expands into three
+result fields. See [Return value](#return-value).
+
+### SDK usage
+
+```js
+const result = await solver.capy(
+  'PUZZLE_Abc1dEFghIJKLM2no34P56q7rStu8v',
+  'https://example.com/login',
+);
+
+// With a non-default API server
+const result = await solver.capy(
+  'PUZZLE_Abc1dEFghIJKLM2no34P56q7rStu8v',
+  'https://example.com/login',
+  { api_server: 'https://jp.api.capy.me/' },
+);
+
+// capy_captchakey, capy_challengekey, capy_answer
+result.captchakey, result.challengekey, result.answer;
+```
+
+### Timing
+
+Capy grades the wall-clock gap between issuing the puzzle and verifying the
+answer, and refuses anything superhuman with `CAPTCHA verification failed` — the
+same message a wrong answer gets. CapSkip therefore holds every result until two
+seconds have elapsed since it drew the puzzle. This is invisible if you poll: the
+task simply takes about two seconds instead of a fifth of one. Nothing to
+configure.
+
+The challenge key is single-use and short-lived, so submit the three values
+promptly rather than caching them.
+
+---
+
+## 8. CaptchaFox — `captchafox(sitekey, url, { ... })`
+
+CaptchaFox scores the browser itself rather than asking the visitor to read
+anything; most visitors never see a puzzle. CapSkip drives the real widget in a
+real browser and returns the verification token.
+
+### POST `/in.php`
+
+| Parameter | Type | Required | Description |
+|---|---|---|---|
+| `key` | string | Yes | CapSkip API key |
+| `method` | string | Yes | `captchafox` |
+| `sitekey` | string | Yes | The public key the widget renders with, conventionally prefixed `sk_` |
+| `pageurl` | string | Yes | Full URL of the page the widget appears on |
+| `api_server` | string | No | Widget entry point. Default `https://cdn.captchafox.com/` |
+| `useragent` | string | No | Accepted for compatibility and not applied — CapSkip uses its own browser's identity |
+| `json` | int | No | `0` plain text, `1` JSON |
+| `proxy` | string | No | Proxy address |
+| `proxytype` | string | No | Proxy type |
+
+### Choosing the widget source
+
+| `api_server` | Token | Default |
+|---|---|---|
+| `https://cdn.captchafox.com/` | Plain | Yes |
+| `https://s.uicdn.com/mampkg/…` | `MAM_` prefixed | No |
+
+Read the value from the `<script>` tag that loads the widget. If you send the
+wrong one the solve still succeeds, but the token comes back in a format the
+target site will not accept — a silent verification failure rather than an error.
+
+### The page URL has to match the key
+
+CaptchaFox keys are registered against a list of allowed domains and the service
+checks the host before issuing anything. A correct key used on a page outside
+that list is refused permanently, not intermittently. CapSkip reports that case
+rather than retrying it, because retrying cannot help.
+
+### Challenge types
+
+| Challenge | Frequency | Supported |
+|---|---|---|
+| Invisible | Usually | Yes |
+| Slide | Sometimes | Yes |
+| Image select | Rarely | No |
+| Audio | Rarely | No |
+
+The two unsupported ones are uncommon and a retry usually draws a different
+challenge, so treat an unsolvable result as a signal to resubmit rather than a
+permanent failure of the key.
+
+### SDK usage
+
+```js
+const result = await solver.captchafox(
+  'sk_xtNxpk6fCdFbxh1_xJeGflSdCE9tn99G',
+  'https://example.com/signup',
+);
+
+// Post in the form field named cf-captcha-response
+result.token;
+
+// Submit under the UA that minted the token, not your own
+result.userAgent;
+```
+
+Uses `recaptchaTimeout` — it is a real browser session, and longer again when an
+interactive challenge is drawn.
+
+---
+
+## 9. Friendly Captcha — `friendlyCaptcha(sitekey, url, { ... })`
+
+Proof-of-work, with nothing shown on screen. The widget searches for values that
+hash below a difficulty the service sets per request.
+
+### POST `/in.php`
+
+| Parameter | Type | Required | Description |
+|---|---|---|---|
+| `key` | string | Yes | CapSkip API key |
+| `method` | string | Yes | `friendly_captcha` |
+| `sitekey` | string | Yes | The `data-sitekey` of the element carrying `class="frc-captcha"` |
+| `pageurl` | string | Yes | Full URL of the page the widget appears on |
+| `version` | string | No | `v1` (default) or `v2`; a bare `1` or `2` is accepted |
+| `module_script` | string | No | `src` of the widget script tag carrying `type="module"` |
+| `nomodule_script` | string | No | `src` of the widget script tag carrying `nomodule` |
+| `api_server` | string | No | Data residency endpoint: `global` (default), `eu`, or a full URL |
+| `useragent` | string | No | User-Agent to send with the request |
+| `json` | int | No | `0` plain text, `1` JSON |
+| `proxy` | string | No | Proxy address |
+| `proxytype` | string | No | Proxy type |
+
+### Version 1 and version 2
+
+Two entirely different protocols ship under this one name, and a sitekey does not
+tell you which one a site uses — they share a brand and a sitekey namespace and
+nothing else. Both are live. Solve the wrong one and you get a well-formed token
+the target site rejects, with no indication that the version was the problem.
+
+| `version` | Widget package | Script |
+|---|---|---|
+| `v1` | `friendly-challenge` | `widget.module.min.js` / `widget.min.js` |
+| `v2` | `@friendlycaptcha/sdk` | `site.min.js` |
+
+CapSkip decides in this order, stopping at the first answer: the `version`
+parameter; then the script URL from `moduleScript` or `nomoduleScript`, which is
+the most reliable signal because it is the build the site actually loads; then
+v1. The SDK refuses any other `version` value locally.
+
+### Submitting the token
+
+| `version` | Form field |
+|---|---|
+| `v1` | `frc-captcha-solution` |
+| `v2` | `frc-captcha-response` |
+
+The field names differ, which is what catches an integration moved from one to
+the other. A v1 token is four dot-separated parts and runs to a few hundred
+characters; a v2 token is a single opaque string beginning `AQQA.` and is roughly
+six kilobytes, so size whatever carries it accordingly.
+
+### SDK usage
+
+```js
+// Say which version
+const result = await solver.friendlyCaptcha(
+  'FCMGEMUD2M567T8G',
+  'https://example.com/signup',
+  { version: 'v2' },
+);
+
+// …or let the script URL decide it
+const result = await solver.friendlyCaptcha(
+  'FCMGEMUD2M567T8G',
+  'https://example.com/signup',
+  { moduleScript: 'https://cdn.example.com/@friendlycaptcha/sdk@0.1.6/site.min.js' },
+);
+
+// EU data-residency tenant
+const result = await solver.friendlyCaptcha(
+  'FCMGEMUD2M567T8G',
+  'https://example.com/signup',
+  { version: 'v2', api_server: 'eu' },
+);
+
+result.token;
+```
+
+Uses `recaptchaTimeout`: the service decides how much work a request is worth at
+the moment it is made, so solve time is not a constant, and v2 always solves in a
+browser.
+
+---
+
+## 10. AWS WAF — `amazonWaf(sitekey, url, { ... })`
+
+AWS WAF puts its CAPTCHA either on a challenge page — the HTTP 405 interstitial
+that sets `window.gokuProps` — or in a widget an ordinary page renders with
+`AwsWafCaptcha.renderCaptcha`. CapSkip solves both in a real browser. See the
+[CapSkip API docs](https://capskip.com/api-docs/#aws-waf).
+
+### POST `/in.php`
+
+| Parameter | Type | Required | Description |
+|---|---|---|---|
+| `key` | string | Yes | CapSkip API key |
+| `method` | string | Yes | `amazon_waf` |
+| `sitekey` | string | Yes | Challenge page: `gokuProps.key`. Widget page: the widget's `apiKey` |
+| `pageurl` | string | Yes | Full http or https URL of the protected page |
+| `iv` | string | No | Challenge page: `gokuProps.iv`. Send together with `context` |
+| `context` | string | No | Challenge page: `gokuProps.context`. Send together with `iv` |
+| `challenge_script` | string | No | Full URL of the page's `challenge.js` |
+| `captcha_script` | string | No | Full URL of the page's `captcha.js` |
+| `jsapiScript` | string | No | Widget page: full URL of `jsapi.js` |
+| `json` | int | No | `0` plain text, `1` JSON |
+| `proxy` | string | No | Proxy address |
+| `proxytype` | string | No | Proxy type |
+
+The SDK also accepts `challengeScript`, `captchaScript` and `jsapi_script`, and
+sends the documented spelling of each. An optional left `undefined`, `null` or
+`''` is not sent — the server reads an empty value as absent.
+
+### Challenge page or widget page
+
+| | Challenge page | Widget page |
+|---|---|---|
+| Recognized by | HTTP 405 with `window.gokuProps` in an inline script | `AwsWafCaptcha.renderCaptcha(container, { apiKey, … })` |
+| `sitekey` | `gokuProps.key` | the widget's `apiKey` |
+| `iv` / `context` | `gokuProps.iv` / `gokuProps.context`, or neither | not sent |
+| Scripts | `challenge_script`, `captcha_script` | `jsapiScript` |
+
+`iv` and `context` come off the same page and only work as a pair, so the SDK
+refuses one without the other. Both are optional: left out, CapSkip reads them
+from `pageurl` at solve time, which is the safer choice when your copy of the
+page is more than a few minutes old.
+
+### Script URLs
+
+CapSkip posts the solution to the host a script URL names, so it refuses any
+script that is not on AWS WAF. The SDK applies the server's rule before the
+request is made: the URL must be `https`, its host must end in `.awswaf.com`, it
+must carry no credentials and no port other than 443, and its path must be one
+or more segments followed by `challenge.js`, `captcha.js` or `jsapi.js`. A query
+string is allowed. Anything else throws `ValidationException`, because CapSkip is
+not an AWS WAF integration for scripts hosted elsewhere.
+
+### GET `/res.php`
+
+The answer is **not a token**. With `json=1` it is an object in `request`:
+
+```json
+{"status":1,"request":{"captcha_voucher":"…","existing_token":"…"}}
+```
+
+and in plain text the same object as one line of JSON after `OK|`. The SDK
+expands it into `captcha_voucher` and `existing_token`; see
+[Return value](#return-value).
+
+### Exchanging the voucher
+
+The two values only work as a pair. POST them as JSON to the `voucher` endpoint
+beside the page's `challenge.js` (the same directory, with `voucher` in place of
+`challenge.js`). The response's `token` is the `aws-waf-token` cookie. Exchange
+them immediately rather than storing them for later.
+
+### SDK usage
+
+```js
+// Challenge page
+const result = await solver.amazonWaf(
+  'AQIDAHjcYuEXAMPLEghicBgQ/7bFaQZ+m5FKCMDnO+vTbNg96AHDh0IR5vgzHNceHYqZR+GOAAAAfjB8',
+  'https://example.com/protected',
+  {
+    iv: 'CgAFRDIjfgAAA5yY',
+    context: 'Rbp3r8fvbuhmrCqpUe8Mh1TLvs8OSKJZiSs2vCF4dt9rxVZI7xYJa2n5k/9r+XaXe7KUIu2I8nXTDHHkDvIOTDc2',
+    challenge_script: 'https://3f2a9c7d41b0.edge.sdk.awswaf.com/3f2a9c7d41b0/8e51d0c7a2f4/challenge.js',
+  },
+);
+
+// Widget page
+const result = await solver.amazonWaf(
+  'Xr9kEXAMPLE2bWQx1vTq8LmZ0aYc4dHs7nFp3gJt6uKw5eRi9AbCdEfGh=_0_1',
+  'https://example.com/protected',
+  { jsapiScript: 'https://5b7e0a19c3d8.us-east-1.captcha-sdk.awswaf.com/5b7e0a19c3d8/jsapi.js' },
+);
+
+result.captcha_voucher, result.existing_token;
+```
+
+Uses `recaptchaTimeout`: a real browser mints the token the voucher is issued
+for, and the puzzle rounds go through AWS on top of that.
+
+---
+
 ## Return value
 
 Every solve method resolves to:
@@ -401,6 +737,46 @@ form field it goes in) and `number`, the counter that solved it:
 }
 ```
 
+CaptchaFox and Friendly Captcha expose `token`, the same string as `code`, named
+for the form field it goes in. CaptchaFox adds `userAgent` when the solve
+reported one — the UA the browser minted the token under, not one you sent:
+
+```js
+{
+  captchaId: '12345',
+  code: '177f50c25b845601e5c779cdb51b040d…',
+  token: '177f50c25b845601e5c779cdb51b040d…',
+  userAgent: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) …',
+}
+```
+
+Capy returns an object rather than a token, expanded into the three fields the
+target form takes (`code` keeps the raw answer):
+
+```js
+{
+  captchaId: '12345',
+  code: { captchakey: 'PUZZLE_…', challengekey: '…', answer: '…', respKey: '' },
+  captchakey: 'PUZZLE_Abc1dEFghIJKLM2no34P56q7rStu8v',
+  challengekey: 'BalY2gJaI8uA2SGVOZhqBQ3V0CYSNNGP',
+  answer: '0xax8ex0xax84x0xkx7qx0x18x76x…',
+  respKey: '',
+}
+```
+
+AWS WAF returns an object too, expanded into the voucher pair the site's
+`voucher` endpoint trades for the `aws-waf-token` cookie (`code` keeps the raw
+answer):
+
+```js
+{
+  captchaId: '12345',
+  code: { captcha_voucher: '…', existing_token: '…' },
+  captcha_voucher: 'eyJ2b3VjaGVyIjoiRVhBTVBMRSJ9.9QwZcEXAMPLEvoucherJk4LmN0pQ',
+  existing_token: '7d4c2a91-EXAMPLE-4f0b-9e6d-3a1b5c8e2f70:EQoAeXAMPLEtokenAAAA:Wm9wc2E=',
+}
+```
+
 GeeTest additionally expands its answer into `challenge`, `validate`, and
 `seccode` (`code` keeps the raw JSON string):
 
@@ -431,6 +807,13 @@ Convenience aliases mapped before sending to CapSkip:
 | `api_subdomain` | `api_server` |
 | `challengeUrl` / `challengeURL` | `challenge_url` |
 | `challengeJson` / `challengeJSON` | `challenge_json` |
+| `userAgent` / `user_agent` | `useragent` |
+| `captchaKey` | `captchakey` |
+| `moduleScript` | `module_script` |
+| `nomoduleScript` / `noModuleScript` | `nomodule_script` |
+| `challengeScript` | `challenge_script` |
+| `captchaScript` | `captcha_script` |
+| `jsapi_script` | `jsapiScript` |
 | `proxy` object | `proxy` + `proxytype` strings |
 
 ```js

package/examples/amazon_waf.js

@@ -0,0 +1,97 @@
+'use strict';
+
+/**
+ * Solve an AWS WAF CAPTCHA.
+ *
+ * AWS WAF shows up in two forms, and the values you need depend on which one
+ * the target page uses:
+ *
+ *   * A challenge page -- the HTTP 405 interstitial that sets `window.gokuProps`
+ *     in an inline script. `sitekey` is `gokuProps.key`; `iv` and `context` are
+ *     `gokuProps.iv` and `gokuProps.context`. `challenge_script` and
+ *     `captcha_script` are the full URLs of the page's challenge.js and
+ *     captcha.js.
+ *   * A widget page -- an ordinary page that calls
+ *     `AwsWafCaptcha.renderCaptcha(container, { apiKey, ... })`. `sitekey` is
+ *     that `apiKey`, and `jsapiScript` is the full URL of jsapi.js.
+ *
+ * Only `sitekey` and the page URL are required. `iv` and `context` travel
+ * together: send both or neither. Left out, CapSkip reads them from the page
+ * at solve time, which is the safer choice when your copy of the page is more
+ * than a few minutes old.
+ *
+ * Every script URL must be an https URL on an awswaf.com host. CapSkip posts
+ * the solution to the host the script names, so it refuses anything else
+ * before the request is made.
+ *
+ * Unlike reCAPTCHA or Turnstile, the answer is NOT a token you put in a form.
+ * It is a voucher pair that AWS trades for the `aws-waf-token` cookie.
+ */
+
+const { CapSkip } = require('capskip');
+
+const solver = new CapSkip({
+  apiKey: process.env.CAPSKIP_API_KEY || 'capskip',
+  host: process.env.CAPSKIP_HOST || '127.0.0.1',
+  port: Number(process.env.CAPSKIP_PORT || 8080),
+});
+
+const PAGE_URL = 'https://example.com/protected';
+
+// From the challenge page's window.gokuProps.
+const SITEKEY = 'AQIDAHjcYuEXAMPLEghicBgQ/7bFaQZ+m5FKCMDnO+vTbNg96AHDh0IR5vgzHNceHYqZR+GOAAAAfjB8';
+const IV = 'CgAFRDIjfgAAA5yY';
+const CONTEXT = 'Rbp3r8fvbuhmrCqpUe8Mh1TLvs8OSKJZiSs2vCF4dt9rxVZI7xYJa2n5k/9r+XaXe7KUIu2I8nXTDHHkDvIOTDc2';
+const CHALLENGE_JS = 'https://3f2a9c7d41b0.edge.sdk.awswaf.com/3f2a9c7d41b0/8e51d0c7a2f4/challenge.js';
+
+async function main() {
+  const result = await solver.amazonWaf(SITEKEY, PAGE_URL, {
+    iv: IV,
+    context: CONTEXT,
+    challenge_script: CHALLENGE_JS,
+  });
+
+  console.log('Captcha ID:    ', result.captchaId);
+  console.log('Voucher:       ', `${result.captcha_voucher.slice(0, 32)}...`);
+  console.log('Existing token:', `${result.existing_token.slice(0, 32)}...`);
+
+  // --- A widget page -------------------------------------------------------
+  // The widget's apiKey as the sitekey, and the jsapi.js it loads. No iv or
+  // context: a widget page has none.
+  //
+  //   await solver.amazonWaf(
+  //     'Xr9kEXAMPLE2bWQx1vTq8LmZ0aYc4dHs7nFp3gJt6uKw5eRi9AbCdEfGh=_0_1',
+  //     PAGE_URL,
+  //     { jsapiScript: 'https://5b7e0a19c3d8.us-east-1.captcha-sdk.awswaf.com/5b7e0a19c3d8/jsapi.js' },
+  //   );
+  //
+  // --- With a per-request proxy --------------------------------------------
+  //   await solver.amazonWaf(SITEKEY, PAGE_URL, {
+  //     proxy: { type: 'HTTP', uri: 'login:password@1.2.3.4:8080' },
+  //   });
+
+  // Exchange the pair for the aws-waf-token cookie: POST both values as JSON
+  // to the `voucher` endpoint that sits beside the page's challenge.js. The
+  // response's `token` is the cookie value. Do this immediately -- the voucher
+  // is short-lived, so do not store the pair for a later request.
+  const voucherUrl = new URL('voucher', CHALLENGE_JS).href;
+  console.log('Voucher URL:   ', voucherUrl);
+  //
+  //   const response = await fetch(voucherUrl, {
+  //     method: 'POST',
+  //     headers: { 'Content-Type': 'application/json' },
+  //     body: JSON.stringify({
+  //       captcha_voucher: result.captcha_voucher,
+  //       existing_token: result.existing_token,
+  //     }),
+  //   });
+  //   const { token } = await response.json();
+  //
+  //   // Then request the protected page with the cookie:
+  //   await fetch(PAGE_URL, { headers: { Cookie: `aws-waf-token=${token}` } });
+}
+
+main().catch((error) => {
+  console.error(`${error.name}: ${error.message}`);
+  process.exitCode = 1;
+});

package/examples/captchafox.js

@@ -0,0 +1,102 @@
+'use strict';
+
+/**
+ * Solve a CaptchaFox challenge.
+ *
+ * CaptchaFox scores the browser itself rather than asking the visitor to read
+ * anything, so most solves draw no puzzle at all. CapSkip drives the real widget
+ * in a real browser and returns the verification token it would have produced.
+ *
+ * You need two values, both read off the target page:
+ *
+ *   * sitekey - the public key the widget renders with, conventionally prefixed
+ *     `sk_`. It is on the widget container as `data-sitekey`, or in the
+ *     `captchafox.render(...)` call. If the page builds the widget at runtime,
+ *     open DevTools -> Network and find the request to api.captchafox.com: the
+ *     key is the path segment after /captcha/.
+ *   * pageurl - the full URL of the page the widget appears on
+ *
+ * The page URL has to match: CaptchaFox keys are registered against a list of
+ * allowed domains and the service checks the host before it issues anything. A
+ * key that is correct but used on a page outside that list is refused
+ * permanently, not intermittently -- so if a sitekey fails immediately and
+ * consistently, check that you are sending the page the widget actually runs on
+ * rather than a search page, a redirect or a shortened link.
+ */
+
+const { CapSkip } = require('capskip');
+
+const solver = new CapSkip({
+  apiKey: process.env.CAPSKIP_API_KEY || 'capskip',
+  host: process.env.CAPSKIP_HOST || '127.0.0.1',
+  port: Number(process.env.CAPSKIP_PORT || 8080),
+});
+
+const SITEKEY = 'sk_xtNxpk6fCdFbxh1_xJeGflSdCE9tn99G';
+const PAGE_URL = 'https://example.com/signup';
+
+async function main() {
+  const result = await solver.captchafox(SITEKEY, PAGE_URL);
+
+  console.log('Captcha ID:', result.captchaId);
+  console.log('Token:     ', `${result.token.slice(0, 60)}...`);
+  console.log('User-Agent:', result.userAgent || '(none reported)');
+
+  // --- Choosing the widget source ------------------------------------------
+  // CaptchaFox publishes its widget from two places, and which one a site loads
+  // decides the shape of the token it expects back. Send api_server only when
+  // the target page does not use the default (https://cdn.captchafox.com/).
+  //
+  //   await solver.captchafox(SITEKEY, PAGE_URL, {
+  //     api_server: 'https://s.uicdn.com/mampkg/@mamdev/core.frontend.libs.captchafox/',
+  //   });
+  //
+  // That one returns a MAM_ prefixed token. Read the value from the <script>
+  // tag on the target page: if you send the wrong one the solve still succeeds,
+  // but the token comes back in a format the site will not accept, which looks
+  // like a silent verification failure rather than an error.
+  //
+  // --- With a per-request proxy --------------------------------------------
+  // CapSkip does not force a proxy, but CaptchaFox scores the network a widget
+  // runs on as well as the browser, so repeated solves from one address push
+  // that address toward the interactive challenges and then toward refusals.
+  //
+  //   await solver.captchafox(SITEKEY, PAGE_URL, {
+  //     proxy: { type: 'HTTP', uri: 'login:password@1.2.3.4:8080' },
+  //   });
+
+  // Post the token back in the form field the widget uses, named
+  // `cf-captcha-response`. Treat it as opaque and pass it through unchanged --
+  // it is verified server side against the session that produced it, so any
+  // edit invalidates it.
+  //
+  //   await fetch(SIGNUP_URL, {
+  //     method: 'POST',
+  //     headers: { 'User-Agent': result.userAgent },
+  //     body: new URLSearchParams({
+  //       email: 'someone@example.com',
+  //       'cf-captcha-response': result.token,
+  //     }),
+  //   });
+  //
+  // Some integrations read the token from a JSON body field instead, so check
+  // what the page's own submit sends and mirror it.
+  console.log('Form field:', { 'cf-captcha-response': `${result.token.slice(0, 40)}...` });
+
+  // Submit under the User-Agent the token was minted with, not your own.
+  // CapSkip solves in a real browser and uses that browser's identity, so the
+  // UA it reports is the one the token is bound to.
+  //
+  // Tokens are short lived: submit promptly rather than holding one while a
+  // user fills in a form, and solve again if the form is abandoned and resumed.
+
+  // Two of CaptchaFox's challenge types are not solvable -- image-select and
+  // the audio fallback, both rare. They are reported as unsolvable rather than
+  // waited out, so treat a failure as a signal to resubmit into a fresh
+  // challenge rather than as a permanent failure of the key.
+}
+
+main().catch((error) => {
+  console.error(`${error.name}: ${error.message}`);
+  process.exitCode = 1;
+});