CordServerJoinAction
Join a Cord guild with an account token and an invite code, with an optional boost. Covers the request schema, an example and each provider's price per 1,000.
CordServerJoinAction joins a guild with a Cord account for you. You send the account token and the invite code, and the task returns the guild ID and the join status. Nothing is solved on your side: the provider performs the join through your proxy.
Build the request
tokenis the account token that performs the join. Treat it like a password and send it only to AnySolver.inviteis the invite code only. For an invite link, send the part after the host, for exampleafkfor.../afk.boostis optional. Set it totrueto boost the guild after a successful join. Not every provider supports boosting: SwiftSolve, for example, rejects a task withboost: truewithTASK_NOT_SUPPORTED. Check the provider list on this page.proxyis the proxy the account uses for the join.
Proxy
task.proxy is required on this task type, and the provider makes the join from that address. Use the proxy the account normally uses, instead of changing the account's IP for each action. Proxy formats are in Proxy configuration.
Read the result
solution.guildId is the ID of the guild the account joined, and solution.status is the status the provider reports. Both are optional, so check solution.raw when a field is missing.
Check Provider stats for live success rates and solve times before you pick a provider.
Supported Providers
| Provider | Price per 1,000 | Routing |
|---|---|---|
CaptchaHeaven | $10.00 | |
SwiftSolve | $7.00 |
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 | ||
token* | string | Yes | Cord account token that performs the join. Example: |
invite* | string | Yes | Invite code only: the part of the invite link after the host, for example Example: |
proxy* | string | object | Yes | Proxy the provider solves through, as a string or an object. See Proxy configuration. View proxy configurationExample: |
boost | boolean | No | Boost the guild after a successful join. Not every provider supports it. |
{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "CordServerJoinAction",
"token": "YOUR_ACCOUNT_TOKEN",
"invite": "afk",
"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 |
|---|---|---|---|
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |
guildId | string | No | Id of the guild the account joined. Example: |
status | string | No | Join status reported by the provider. |