Adding a provider proxy should not mean copying the same credentials one field at a time. In the typical Proxifier workflow, you enter the hostname, port, protocol, username and password manually, test the server, and then create a routing rule. It is a lot of form work for information that already exists in one proxy string.
ProxyTool can turn that whole string into the setup. Paste it into ProxyTool AI and say: "Add this IPBurger proxy and route Firefox through it." The assistant reads every field, detects the protocol and proposes both the proxy and the app rule. You review the result once instead of retyping the source data.
IPBurger sells residential proxies, mobile proxies, static ISP proxies and dedicated IPs. Each product is a different endpoint in its dashboard. In ProxyTool each one is a proxy plus a rule: residential for the scraper, a dedicated IP for the account that must stay put, mobile for the app that should look like a phone. IPBurger and ProxyTool work together as partners. Direct store purchasing is planned but is not in checkout yet; an existing IPBurger endpoint works now.
Copy the endpoint
From the IPBurger dashboard, copy what the product page shows:
- Host and port
- Username and password
- Protocol: HTTP, HTTPS or SOCKS5
Dedicated and ISP products are one address you keep. Residential and mobile products are a gateway, and the username is where country, city or session length usually lives. Change the username, not the host, when you need another location.
Type it in
- Open Proxies and add a proxy.
- Paste host, port, username and password into the matching fields. Set the protocol IPBurger printed next to the endpoint.
- Name it after the job: "IPBurger Mobile US", "IPBurger Dedicated".
- Run the check. Protocol, login and exit country have to match before you attach an app.
- Add a rule for the process, or for the hosts that job talks to. Leave every other app on the direct rule.
That is the manual setup. It works for a single browser and for a stack of tools that must not share an IP. Windows, macOS, Linux, Android and iOS use the same fields.
Hand the string to ProxyTool AI
Skip the form when you have the line IPBurger shows. Paste one proxy string, or several, into ProxyTool AI.
Say it plainly: "Integrate this IPBurger proxy and route only Firefox through it." Or: "Add these three proxies. Put the scraper on the residential one, Slack on the dedicated one, and leave everything else direct."
The assistant accepts the usual shapes: protocol://user:pass@host:port, protocol://host:port:user:pass, and host:port:user:pass. It fills host, port, username, password and protocol, then proposes the proxies and the rules. You read that proposal and confirm. Until you do, nothing in the policy changes.
Pasting the string is the integration. There is no IPBurger driver and no extra connector.
The practical advantage over Proxifier
The difference is not whether both clients can route an app through a proxy. They can. The difference is the setup work. A conventional Proxifier setup makes the endpoint fields and the routing rule separate manual tasks. ProxyTool AI accepts the provider string and your routing request together, then gives you one proposal to review. That matters when you add several residential or mobile proxies, because the time saving repeats for every endpoint.
One provider, apps kept apart
A proxy client for Windows and the other ProxyTool apps exist so a provider account does not have to capture the whole device. Mobile proxies and ISP proxies from IPBurger stay on the apps you assign. The rest of the machine keeps your own address.
That split is the point of the partnership on our side. The partner overview shows the relationship; direct store purchase comes later. The setup above is what you use with an IPBurger account you already have, and it is the same setup a store endpoint can use when it becomes available.
Start from the line in the IPBurger dashboard. Type the four fields, or paste the string and tell the AI which apps go through it.