Limits
What to size your client for.
| Limit | Value |
|---|---|
| Requests per second, per key | 50 |
| Requests per second, per account | 200 |
| Request body | 2 MB (a challenge script alone is about 500 KB) |
| Solve timeout (ours) | 30 seconds, then solver_timeout |
| Typical solve time | 2 to 10 seconds. Most of it is round trips through your proxy; our own work is well under a second. |
userAgent length | 512 characters |
Set your client timeout to 60 seconds so it outlasts ours. Need more throughput? Ask on Discord.
Over the limit you get rate_limited (429) and a retry-after header. When our solvers are full you get solver_unavailable (503) with the same header. In both cases wait, then retry.
Proxies
- Format:
http://user:pass@host:port(orhttps://). SOCKS proxies are not supported. - The proxy must be on the public internet. Private, loopback and link-local addresses are refused with
bad_params. - Residential or mobile IPs clear far more often than datacenter ones. Use a sticky session so the IP does not change mid-run.
- Your proxy is used for that one request and is not stored with your usage records.