🌐 Need Proxies? Check out my services
| Service | Pricing | Features |
|---|---|---|
| 🔮 VaultProxies | $1.00/GB residential |
Residential · IPv6 · Residential Unlimited · Datacenter |
| 🌑 NullProxies | $0.75/GB residential |
Residential · Residential Unlimited · DC Unlimited · Mobile Proxies |
| ⚡ StrikeProxy | $0.75/GB residential |
Residential · Residential Unlimited · DC Unlimited · Mobile Proxies |
solvex-sdk
Python client for the Solvex FunCaptcha solving API.
Install
pip install solvex-sdk
# or, from this repo:
pip install .
The distribution is published as solvex-sdk; the import name is solvex.
Requires Python 3.10+. Depends on httpx.
Quickstart
from solvex import SolvexClient, FunCaptchaTask, Proxy
with SolvexClient("sk_live_...") as sx:
result = sx.solve(FunCaptchaTask(
website_url="https://roblox.com",
website_public_key="476068BF-9607-4799-B53D-966BE98E2B81",
proxy=Proxy.from_url("http://user:pass@184.82.39.210:8080"),
))
print(result.token)
print(f"cost=${result.cost_usd} solved in {result.solve_seconds}s")
A proxy is required — Solvex does not run proxyless solves.
Supported site keys
Solvex rejects websitePublicKey values it doesn't know, rather than silently
forwarding bad context (wrong surl, wrong location.href, wrong referrer)
that Arkose would quietly suppress a token for. The currently-registered keys:
| Label | websitePublicKey |
|---|---|
| Roblox Login | 476068BF-9607-4799-B53D-966BE98E2B81 |
| Roblox Signup | A2A14B1D-1AF3-C791-9BBC-EE33CC7A0A6F |
Passing anything else raises UnsupportedSiteKeyError (errorId: 23) — contact
support to add the site you need.
Logged-in sessions (blob + cookies)
When the challenge is tied to a logged-in Roblox session (e.g. authenticated
actions that hand you a dataExchangeBlob), pass the blob in data and the
matching session cookie string in cookies. Without the cookie Arkose will
treat the session as mismatched and suppress the token:
result = sx.solve(FunCaptchaTask(
website_url="https://www.roblox.com",
website_public_key="476068BF-9607-4799-B53D-966BE98E2B81",
proxy=Proxy.from_url("http://user:pass@1.2.3.4:8080"),
data=roblox_data_exchange_blob,
cookies=".ROBLOSECURITY=...; RBXEventTrackerV2=...;",
))
Cookie formats
The API accepts cookies in any of the shapes you'd get from common clients —
they're normalized to a Cookie: header server-side:
# Raw header string (default)
cookies=".ROBLOSECURITY=...; RBXEventTrackerV2=..."
# Python requests
cookies=session.cookies.get_dict()
# rnet — same dict shape
cookies=dict(client.cookies)
# Playwright / Selenium / Puppeteer
cookies=[{"name": ".ROBLOSECURITY", "value": "..."}, {"name": "RBXEventTrackerV2", "value": "..."}]
# List of pair strings
cookies=[".ROBLOSECURITY=...", "RBXEventTrackerV2=..."]
PoW-flagged sessions
When Arkose returns pow=true, the server can solve the PoW challenge and
still hand you a token instead of failing. Opt in with solve_pow=True —
it trades 1–3s (C++ fast path) or 15–30s (Node fallback) of latency for a
higher success rate on flagged sessions. Billed as a normal solve.
task = FunCaptchaTask(..., solve_pow=True)
Async
import asyncio
from solvex import AsyncSolvexClient, FunCaptchaTask, Proxy
async def main():
async with AsyncSolvexClient("sk_live_...") as sx:
result = await sx.solve(FunCaptchaTask(
website_url="https://roblox.com",
website_public_key="476068BF-9607-4799-B53D-966BE98E2B81",
proxy=Proxy.from_url("socks5://184.82.39.210:1080"),
use_http3=True, # None = server default (enabled)
))
print(result.token)
asyncio.run(main())
Low-level
If you want to manage polling yourself:
task_id = sx.create_task(task)
while True:
r = sx.get_task_result(task_id)
if r["status"] == "ready":
print(r["solution"]["token"])
break
Balance
print(f"${sx.get_balance():.4f} remaining")
Errors
Every non-zero errorId raises a typed exception:
| Exception | errorId | Meaning |
|---|---|---|
InvalidKeyError |
1 | clientKey missing / bad / revoked |
UnsupportedTaskError |
2, 22 | task type not enabled |
UnsupportedSiteKeyError |
23 | websitePublicKey not registered — contact support |
InsufficientCreditsError |
10 | account balance too low |
TaskFailedError |
12 | solver couldn't produce a token (credits refunded) |
TaskNotFoundError |
16 | unknown taskId |
RateLimitedError |
31 | per-key or per-user rate limit |
TaskTimeoutError |
40 | task exceeded server timeout / client wait |
Catch SolvexError to catch everything.
from solvex import SolvexClient, TaskFailedError, RateLimitedError
try:
result = sx.solve(task, timeout=90)
except TaskFailedError:
# server already refunded — retry with fresh proxy
...
except RateLimitedError:
time.sleep(5)
Idempotency
Pass idempotency_key= to guard against double-billing on retries. Replays
within 24h return the same taskId without a second charge.
sx.solve(task, idempotency_key=f"user-42-{run_id}")
HTTP/3
Set use_http3=False on the task to force HTTP/2 (useful when debugging
proxies that mangle h3). Default is server-side (h3 enabled).
Browser profile
Set browser= to route the solve through a specific fingerprints_v2 profile.
Accepts a family alias ("firefox", "chrome", "brave", "edge",
"safari") or a specific profile name ("firefox_win_140",
"chrome_win_141", etc.). Omit or pass "auto" for the legacy Safari path.
task = FunCaptchaTask(..., browser="firefox")
License
MIT.
Metadata
Release files for solvex-sdk 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| solvex_sdk-0.1.2.tar.gz | 12.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| solvex_sdk-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.4 kB
Release files / solvex_sdk-0.1.2.tar.gz
| Download URL | solvex_sdk-0.1.2.tar.gz |
|---|---|
| Size | 12.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
337f865bc9d52b26be19d49d74d143a091e5852fbf318005a7a196620f1b0e46
|
|
BLAKE2b-256 checksum How to use checksums |
77bdd42f8db0c60b38b3419c4e88d477a80e938fe631dce2a18570b748e9400f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 11, 2026.
Transparency logRelease files / solvex_sdk-0.1.2-py3-none-any.whl
| Download URL | solvex_sdk-0.1.2-py3-none-any.whl |
|---|---|
| Size | 14.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
67b24fadb2ab7c0aaf5f89a0e6c1ed47b54d5dc74562cf64bdf045c8b44c060f
|
|
BLAKE2b-256 checksum How to use checksums |
47293a87abcfad3fe7614dfe8a7f1507b76e274abc34befe56742719f7a99eb0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 11, 2026.
Transparency logSecurity for solvex-sdk 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for solvex_sdk-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 11, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.