Hand over a big list as a job

For the lists that take minutes: hand the list over, get an id back immediately, come back for the results when it is done. Nothing has to stay connected, so a dropped line, a closed laptop or a restart on our side does not cost you the run — a job that is interrupted resumes on the line after the last one answered.

Accounts only (an API key, or signed in on the dashboard). The list costs the same as checking it any other way: every line is charged to your daily budget of 3,000,000 when the job is created, and refunded if the job could not be created at all.

The limits that keep this from becoming a flood: up to 100,000 lines per job, 3 queued or running jobs at a time per account, and 20 job creations an hour. Job probes run in the lowest lane, below every live check, so they pause while the service is under load and pick up again by themselves. Results live for 72 hours after the job ends, then the files are deleted and the job reads expired.

Send the list as { "proxies": [...] } with the same options the streaming endpoint takes, or as a text/plain body of one proxy per line (what curl --data-binary @list.txt sends). Answer is 202 with the job.