Proxies
Import proxies in bulk and bind them to your social-task accounts.
Walk through proxy groups, bulk import, testing and assignment in the real Zyper interface.
Platforms and launchpads are sometimes protected with a heavy rate-limits for their APIs. Proxies mask your traffic so it looks like to come from different IPs, easing the rate-limits through your tasks.
Adding Proxies#
Proxies are separated into groups. Grouping by provider or proxy type makes assignment and health checks easier.
- Click + Add Group and name it—for example,
Birdproxy. - Click + Add Proxies and paste one proxy per line. Lines beginning with
#are ignored as comments. - Click Add. Valid lines are imported and malformed lines are reported separately.
- Run Test All to check connectivity and latency. Importing does not automatically test the proxy.
Accepted formats#
| Format | Example |
|---|---|
| Host and port | 192.0.2.10:8080 |
| URL without authentication | http://192.0.2.10:8080 or https://192.0.2.10:8443 |
| Credentials after host | 192.0.2.10:8080:user:pass |
| Credentials before host | user:pass:192.0.2.10:8080 |
| URL-style authentication | user:[email protected]:8080 |
| Full authenticated URL | https://user:[email protected]:8443 |
Inputs without a scheme default to http. An explicit http or https
scheme is preserved. The legacy host:port:user:pass form supports passwords
containing additional colons. In URL-style forms, percent-encode reserved
characters in usernames or passwords.
When and Where#
- On-Chain tasks — for platforms or launchpads with heavy rate-limits, when you’re running plenty of wallets.
- Social tasks — when a module needs it (Cloudflare-protected sites, captcha-gated submissions), you can pin each burner account to a proxy on the Accounts page.
Folder Location#
Proxies are stored in the encrypted platform store:
%LOCALAPPDATA%\zyper-suite\data\proxies.dat on Windows or
~/Library/Application Support/Zyper AIO/data/proxies.dat on macOS. Username
and password fields are encrypted at rest.
Health Check#
The probe times out generously (about 10 seconds) per proxy. Failures don’t drop proxies from the list — they’re just marked unhealthy. Re-run the probe later to revive any that come back online.