Captcha Configuration

Discord uses hCaptcha Enterprise to protect against automation. Filly integrates with multiple captcha solving services to automatically solve these challenges.

Configuration

Captcha settings are configured in the captcha section of input/config.json:

{
  "captcha": {
    "solve_captcha": true,
    "service": "razorcap",
    "apikey": "3e5fc347-dfd8-4b12-9ca3-e57f931c5fbc",
    "proxyless": false
  }
}

Configuration Options

solve_captcha

boolean

default:"true"

required

Enable or disable automatic captcha solving.

true: Automatically solve captchas when detected
false: Skip captcha solving (joins will fail if captcha appears)

service

string

required

Captcha solving service to use. Supported services:

razorcap - RazorCap API (recommended)
hcoptcha - hCoptcha API
csolver - CSolver service (uses hardcoded API key)
capmonster - CapMonster Cloud

Service name is case-sensitive and must match exactly.

apikey

string

required

API key from your captcha solving service. Each service provides a unique API key when you create an account.Example: 3e5fc347-dfd8-4b12-9ca3-e57f931c5fbc

proxyless

boolean

default:"false"

Whether the captcha solver should use proxies.

true: Solve captchas without proxies (faster but may have lower success rate)
false: Use proxies from input/proxies.txt (better for avoiding detection)

This setting is independent from the main proxyless setting. You can use proxies for joins but not captcha solving, or vice versa.

Supported Services

RazorCap (Recommended)

{
  "captcha": {
    "solve_captcha": true,
    "service": "razorcap",
    "apikey": "your-razorcap-api-key",
    "proxyless": false
  }
}

Features:

hCaptcha Enterprise support
Fast solving times (30-60 seconds)
RQ data support for Discord
Proxy support
Polling-based result retrieval

API Details:

Create task: POST https://api.razorcap.xyz/create_task
Get result: GET https://api.razorcap.xyz/get_result/{task_id}
Timeout: 120 seconds

AISolver

{
  "captcha": {
    "solve_captcha": true,
    "service": "aisolver",
    "apikey": "your-aisolver-api-key",
    "proxyless": false
  }
}

Features:

Discord-specific optimization
Proxy required for best results
RQ data support

hCoptcha

{
  "captcha": {
    "solve_captcha": true,
    "service": "hcoptcha",
    "apikey": "your-hcoptcha-api-key",
    "proxyless": false
  }
}

Features:

hCaptcha Enterprise support
User agent customization
Proxy rotation support

API Details:

Create task: POST https://api.hcoptcha.com/api/createTask
Get result: POST https://api.hcoptcha.com/api/getTaskData

CSolver

{
  "captcha": {
    "solve_captcha": true,
    "service": "csolver",
    "apikey": "your-api-key-here",
    "proxyless": true
  }
}

CSolver uses a hardcoded API key (71144850f4fb4cc55fc0ee6935badddf) embedded in the source code. The apikey value you provide in config.json is ignored for this service.

Features:

Fast response times
Simple API
RQ data support
Uses shared API key (no personal key needed)

API Details:

Endpoint: POST https://api.csolver.xyz/solve
Single request (no polling)

CapMonster Cloud

{
  "captcha": {
    "solve_captcha": true,
    "service": "capmonster",
    "apikey": "your-capmonster-api-key",
    "proxyless": false
  }
}

Features:

HCaptchaTaskProxyless support
User agent customization
Reliable service

API Details:

Create task: POST https://api.capmonster.cloud/createTask
Get result: POST https://api.capmonster.cloud/getTaskResult

How Captcha Solving Works

Captcha detection

When joining a server, Discord may return a captcha challenge:

{
  "captcha_sitekey": "a9b5fb07-92ff-493f-86fe-352a2803b3df",
  "captcha_rqdata": "...",
  "captcha_rqtoken": "..."
}

Send to solver

The tool sends the captcha data to your configured service:

solution = self._handle_captcha(
    response.json()['captcha_rqdata'],
    response.json()['captcha_rqtoken']
)

Wait for solution

The solver processes the captcha (typically 30-90 seconds):

[!] Captcha Detected | Token: MTIzNDU2.*****
[✓] Captcha Solved Successfully

Retry with solution

The tool retries the join with the captcha solution:

self.client.headers.update({
    "authorization": token_only,
    "x-captcha-key": solution,
    "x-captcha-rqtoken": response.json()['captcha_rqtoken']
})
response = self.client.post(
    f"https://discord.com/api/v9/invites/{invite}",
    json={}
)

Discord Captcha Details

Site Configuration

url = "https://discord.com/channels/@me"
sitekey = "a9b5fb07-92ff-493f-86fe-352a2803b3df"
user_agent = 'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:124.0) Gecko/20100101 Firefox/124.0'

sitekey

string

Discord’s hCaptcha site key: a9b5fb07-92ff-493f-86fe-352a2803b3dfThis is constant for all Discord captchas.

rqdata

string

Request-specific data from Discord’s captcha challenge. Unique for each captcha.

rqtoken

string

Request token from Discord. Must be sent back with the solution.

Captcha Headers

When submitting a captcha solution:

{
  "authorization": "token_here",
  "x-captcha-key": "P1_eyJ0eXAiOiJKV1QiLCJhbGc...",
  "x-captcha-rqtoken": "rqtoken_from_discord"
}

Response Handling

Success

if solution:
    self.stats.captcha_solved += 1
    NovaLogger.win("Captcha Solved Successfully")

Token saved to output/joined.txt if join succeeds.

Failure

If captcha solving fails:

if "captcha_key" in response.text:
    NovaLogger.fail("Failed Due To Solver Issue", 
                    token=masked_token, 
                    error=response.json()['captcha_key'])
    self._append_to_file("failed_captcha.txt", token)

Token saved to output/failed_captcha.txt.

Statistics

Captcha statistics are displayed in real-time:

Filly | Total: 50 | Joined: 120 | Failed: 5 | Captcha: 15 (12 solved) | Invalid: 1 | Locked: 0

Captcha: Total captchas encountered
Solved: Successfully solved captchas

Proxy Configuration

When captcha.proxyless is false, proxies are randomly selected:

if not config["captcha"]["proxyless"]:
    proxy = random.choice(proxies).strip()
    proxies = f"http://{proxy}"
else:
    proxies = None

Captcha solvers have their own proxy update mechanism:

def update_proxy(self):
    if not config["captcha"]["proxyless"]:
        proxy = random.choice(proxies).strip()
        proxies = {f"http://{proxy}"}
        return proxies

Best Practices

Captcha solving recommendations:

Use RazorCap or hCoptcha for best Discord compatibility
Enable proxy support for better success rates
Monitor your API balance to avoid service interruptions
Test with a few tokens before running large batches
Keep API keys secure and never commit to Git

Common issues to avoid:

Using free captcha solvers (unreliable)
Running out of API credits mid-operation
Using proxyless mode (lower success rate)
Setting solve_captcha to false (joins will fail)
Wrong service name (case-sensitive)

Cost Considerations

Pricing

Captcha solving services typically charge per solve:

RazorCap: ~$2-3 per 1000 solves
hCoptcha: ~$2-4 per 1000 solves
CapMonster: ~$1-3 per 1000 solves
CSolver: ~$1-2 per 1000 solves

Prices vary by service and account type. Check with your provider for current rates.

Optimization

Reduce captcha costs:

Use good quality proxies (reduces captcha rate)
Add delays between requests
Use fewer concurrent threads
Use residential proxies instead of datacenter
Rotate session IDs frequently

Troubleshooting

Captchas not being solved

Common causes:

solve_captcha is set to false
Invalid API key
Service name misspelled
API balance depleted
Service is down

Solutions:

Set "solve_captcha": true in config.json
Verify API key is correct
Check service name matches exactly
Check API balance with provider
Try different service

All captcha solutions failing

Common causes:

Wrong sitekey
RQ data expired
Proxy issues
Service returning bad solutions

Solutions:

Verify sitekey is a9b5fb07-92ff-493f-86fe-352a2803b3df
Reduce delay (captcha data expires)
Try "proxyless": true for captcha
Contact solver service support
Switch to different service

Captcha solving too slow

Common causes:

Service overloaded
Complex captcha challenges
Network latency
Proxy slowing down requests

Solutions:

Try different service (RazorCap is fastest)
Use "proxyless": true for captcha
Check network connection
Upgrade to premium service tier

Getting charged but no solutions

Common causes:

Service charging for attempts, not successes
Wrong task type being created
API misconfiguration

Solutions:

Review service billing policy
Check service dashboard for task details
Verify configuration matches service docs
Contact service support with task IDs

Service returns 'Invalid sitekey'

Common causes:

Service doesn’t support Discord’s sitekey
Service not configured for hCaptcha Enterprise
API endpoint changed

Solutions:

Use RazorCap, hCoptcha, or CSolver (tested with Discord)
Contact service to enable Enterprise support
Check service documentation for updates
Try alternative service

Service Comparison

Service	Speed	Success Rate	Price	Proxy Support	Recommended
RazorCap	⭐⭐⭐⭐⭐	⭐⭐⭐⭐⭐	$$	✅	✅ Best overall
hCoptcha	⭐⭐⭐⭐	⭐⭐⭐⭐⭐	$$$	✅	✅ High success
CSolver	⭐⭐⭐⭐⭐	⭐⭐⭐⭐	$	❌	✅ Budget option
AISolver	⭐⭐⭐	⭐⭐⭐⭐	$$	✅	⚠️ Requires proxy
CapMonster	⭐⭐⭐⭐	⭐⭐⭐⭐	$$	✅	✅ Reliable

All services support Discord’s hCaptcha Enterprise. Choose based on your budget and requirements.

Documentation Index

​Configuration

​Configuration Options

​Supported Services

​RazorCap (Recommended)

​AISolver

​hCoptcha

​CSolver

​CapMonster Cloud

​How Captcha Solving Works

​Discord Captcha Details

​Site Configuration

​Captcha Headers

​Response Handling

​Success

​Failure

​Statistics

​Proxy Configuration

​Best Practices

​Cost Considerations

​Pricing

​Optimization

​Troubleshooting

​Service Comparison

Configuration

Configuration Options

Supported Services

RazorCap (Recommended)

AISolver

hCoptcha

CSolver

CapMonster Cloud

How Captcha Solving Works

Discord Captcha Details

Site Configuration

Captcha Headers

Response Handling

Success

Failure

Statistics

Proxy Configuration

Best Practices

Cost Considerations

Pricing

Optimization

Troubleshooting

Service Comparison