Overview

helodata proxies are standards-compliant HTTP / HTTPS / SOCKS5 — so anything that speaks those protocols will work. This section is a recipe book: for each common tool we show exactly where the proxy goes, with copy-paste-ready snippets for the three live products.

Quick reference — what credentials to use

The credential shape depends on the product:

Product	Host	Username	Password
Residential	gate.helodata.io:7777	helo_{user}-type-res-region-{cc}[-...optional...]	sub-user password
Mobile	gate.helodata.io:7777	helo_{user}-type-mob-region-{cc}[-asn-...]	sub-user password
ISP	per IP from your list, e.g. 198.51.100.42:8000	helo_{user} (no extra segments)	sub-user password

If a tool only accepts a single ip:port:user:pass line, that's the ISP shape — gateway products need their targeting segments inside the username.

What's in this section

• Browsers — Chrome, Firefox, Edge, Safari (manual or extension-based)
• Antidetect browsers — AdsPower, GoLogin, Multilogin, Dolphin {anty}, Octo
• Scraping tools — Python requests, Scrapy, Selenium, Playwright, Puppeteer, Node fetch/axios
• Operating systems — system-wide proxy on Windows, macOS, Linux
• Mobile — Android Wi-Fi proxy, iOS Wi-Fi proxy, Shadowrocket
• AI & workflow — Postman, LangChain, n8n, MCP server

Conventions used in this section

• Placeholder sub-user: s1a2b3c4d5e
• Placeholder password: PASSWORD
• Placeholder ISP IP: 198.51.100.42
• All examples use US residential as the default target — change region-us to any ISO code

When a screenshot would help, the placeholder [screenshot: …] marks where one belongs. Real screenshots will live in .gitbook/assets/ once the dashboard UI is final.