CordFingerprintAction
Draw a dated Cord fingerprint for the X-Fingerprint header, so the account you register carries that fingerprint's creation date.
CordFingerprintAction hands you one Cord fingerprint from stock, optionally restricted to a date or a date range, and returns it with its creation date. Nothing is solved: each fingerprint is handed out once and then dropped from stock.
What the fingerprint does
A Cord fingerprint is a snowflake, a dot, and a signed blob. The Cord client generates one shortly before registering and sends it as the X-Fingerprint header with the registration:
1174092529238016042.sample_fingerprint_stringOn a valid registration, Cord reuses the fingerprint's snowflake as the new account's ID. A snowflake encodes the millisecond it was created, so the fingerprint sets the account's creation date. Register with a fingerprint made in December 2023 and the account reads as created in December 2023, however long after that you sign up.
A fingerprint cannot be generated with a past timestamp, so dated fingerprints come from stock rather than being generated on request. Stock covers a limited window of dates, and an account registered with one of them lands in that window. What is left inside the window shifts as fingerprints are drawn: ask for a date and see what comes back.
This task does not register anything
It only dispenses the fingerprint. Creating the account and solving any CAPTCHA on the register endpoint are yours to do.
Use the fingerprint
Go through your registration flow and find every request that carries an X-Fingerprint header. Replace that header's value with the fingerprint this task returned, and send the same one on all of them.
A fingerprint works for one registration only. Draw a new one for the next registration.
Choose a date
date is optional. Omit it to draw from every date in stock, or send a single date or an inclusive range. Single dates take any of these styles, and month-name dates accept ordinals:
| Style | Examples |
|---|---|
| Month name | Dec 1 2023, December 1 2023, Dec 1st 2023 |
| Year first | 2023-12-01, 2023/12/01, 2023_12_01, 2023.12.01 |
| Day first | 01-12-2023, 01/12/2023, 01_12_2023, 01.12.2023 |
Numeric dates are day-month-year, never month-day-year; the four-digit part is the year. A range joins two dates with -, .., : or to and includes both bounds:
2023/11/01-2023/12/31
2023-11-01 - 2023-12-31
Nov 1 2023 to Dec 31 2023
Nov 1 2023..Dec 31 2023
Nov 1 2023:Dec 31 2023A reversed range is swapped for you. All dates are UTC. There is no fallback to a nearby day: a date with no stock left returns no fingerprint.
The price depends on whether you send a date; the pricing table on this page shows the current rates, and the exact figure comes back as cost on the result.
Read the date
solution.date is the fingerprint's own timestamp, RFC 3339 UTC with milliseconds, decoded from its snowflake:
timestamp_ms = (snowflake >> 22) + 14200704000001420070400000 is 1 January 2015 UTC, the epoch of these snowflakes; the low 22 bits are worker and sequence data. For the fingerprint above, the result is 2023-11-14T21:04:32.554Z.
The decoded value is used only when it falls between 2015 and 2035. Otherwise solution.date is midnight UTC of the date the fingerprint is filed under. Either way, solution.date is the creation date an account registered with the fingerprint carries.
Check Provider stats for live success rates and solve times before you pick a provider.
Supported Providers
| Provider | Price per 1,000 | Routing |
|---|---|---|
CapCracker | $5.00–$5.50 |
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 | ||
date | string | No | Restrict the draw to one issue date or an inclusive range. Accepts Example: |
{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "CordFingerprintAction"
}
}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 |
|---|---|---|---|
fingerprint* | string | Yes | Cord fingerprint, sent verbatim as the Example: |
date* | string | Yes | Creation timestamp of the fingerprint (RFC 3339, UTC, milliseconds), decoded from its snowflake. This is the creation date an account registered with it will carry. Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |