Sign inGet started
$2 First two hours on 4G$3 First two hours on 5G4 h Longest hourly purchase, never renewsUnlimited Data and rotation, hourly included
Sign inSign up
Integrations

Putting an Hourly Line Into the Tools You Already Have

Everything we sell is a host, an HTTP port, a SOCKS5 port, a username and a password, which means it goes into any tool that takes a proxy. When the line only lasts two hours, the setup needs to take two minutes, not twenty, so this page is a list of the tools our customers reach for most, each with the exact steps and the one or two things that trip people up. The two anti-detect browsers we recommend come first, Undetectable.io and then GoLogin, followed by the command-line and code tools developers use for short jobs, then the helpers for browsers, desktops and phones.

Undetectable.io

Anti-detect browser

The anti-detect browser we recommend first. Each profile is its own browser with its own fingerprint and its own proxy, and the built-in proxy check tells you the carrier and city of the line before you open a single tab. It is the fastest way to put a two-hour line under one account, run the job, and close the profile when the meter stops. The free tier is enough to test the pairing.

  1. Install Undetectable.io and sign in.
  2. In the HourlyProxies dashboard copy the host, port, username and password of the line you just bought.
  3. Create a new profile, open its proxy tab, pick HTTP or SOCKS5 to match the port, paste the four values and run the check.
  4. When the check shows a US carrier in the right city, save the profile and launch it.
  5. Open an IP lookup page in the profile to confirm, then start the job.
  • Give the profile the same name as the line so you know which meter it is on.
  • If the hours run out mid-session, the profile simply loses connection; add an hour in the dashboard and reload.
Get Undetectable.io ↗ (partner link)

GoLogin

Anti-detect browser

Our second recommendation, and the better fit if you work on Linux, want to open a profile from Android, or share profiles with a team. The proxy is stored on the profile and checked before launch, so a profile cannot be opened on the wrong line by accident. For hourly work the cloud profiles are handy: start a profile on a line, hand the profile to a colleague, and the job carries on from their machine on the same address.

  1. Install GoLogin on Windows, Mac, Linux or Android and log in.
  2. Create a profile and accept the generated fingerprint for the operating system you want to appear as.
  3. In the profile's proxy section choose HTTP or SOCKS5, paste host, port, username and password from the dashboard, and press check.
  4. Let GoLogin set the time zone and language from the proxy, or set them to the line's city by hand.
  5. Launch the profile and confirm the address on an IP lookup page.
  • One profile per line at a time. Two profiles on one line share one address and one session.
  • Rotate the line between tasks, not while a profile is signed in.
Get GoLogin ↗ (partner link)

curl

Command line

The quickest way to prove a line is up and see what it looks like from outside. One command sends a request through the proxy and prints the address a website sees, and the same flag works for HTTP and SOCKS5. Most customers run a curl check in the first minute of an hourly purchase before pointing anything bigger at the line, and run it again after a rotation to confirm the address changed.

  1. Run: curl -x http://USER:PASS@HOST:PORT https://api.ipify.org and read the address printed.
  2. For SOCKS5 use -x socks5h://USER:PASS@HOST:PORT so DNS resolves through the line as well.
  3. Call your rotation link with curl, wait a few seconds, and run the first command again to confirm a new address.
  • Put the proxy in a CURL_PROXY shell variable so you can paste the same commands on the next line you rent.
(partner link)

Python requests

Code library

The standard HTTP library for Python scripts, and the one most of our scraping customers use. A proxies dictionary on the session routes every request through the line, and because an hourly line has a fixed end, the pattern that works is: buy the line, run the script, let the purchase end. Install the socks extra if you want SOCKS5. Keep the credentials in environment variables so the script does not change between purchases.

  1. pip install requests, or pip install requests[socks] for SOCKS5.
  2. Build the URL http://USER:PASS@HOST:PORT (or socks5h://USER:PASS@HOST:PORT) and set it as both http and https in a proxies dict.
  3. Create a requests.Session, assign session.proxies, and make your calls as usual.
  4. To rotate, call the rotation link with requests.get and pause for a few seconds before the next batch.
  • Use a Session rather than bare requests.get so the connection is reused; it is faster on mobile latency.
  • Set a timeout on every call. A line whose hours have run out will refuse connections, and you want the script to notice.
(partner link)

Node.js (undici or axios)

Code library

For JavaScript, undici is the fetch implementation built into modern Node and takes a ProxyAgent directly; axios takes a proxy object or an agent from a small helper package. Either lets a script or a small service route through a line for exactly as long as the hours last. Node users on our lines tend to be running API tests, webhooks that must come from a mobile network, or Playwright-adjacent tooling.

  1. With undici: import ProxyAgent and setGlobalDispatcher, create new ProxyAgent('http://USER:PASS@HOST:PORT') and set it globally; fetch now goes through the line.
  2. With axios: install https-proxy-agent or socks-proxy-agent and pass the agent as httpsAgent in the axios config.
  3. Request an IP lookup endpoint once at startup and log the address so you can see which line the run used.
  • Node's native fetch ignores HTTP_PROXY environment variables; set the dispatcher explicitly.
(partner link)

Postman

API client

When you are testing an API by hand and need the calls to arrive from a US mobile address, Postman's proxy settings route the whole workspace through a line without touching your system settings. It is the right tool for the two-hour job of checking what an API returns to a mobile client in a given city, or for reproducing a customer's report from the carrier they use. Turn the proxy off again when the hours end.

  1. Open Settings, then Proxy, and switch on the custom proxy.
  2. Enter HOST and PORT for the HTTP port of your line and tick both HTTP and HTTPS.
  3. Enable proxy authentication and enter the username and password.
  4. Send a request to an IP lookup URL to confirm the address before running your collection.
  • Postman's custom proxy is HTTP only; use the HTTP port, not the SOCKS5 port.
(partner link)

Playwright

Browser automation

Playwright drives a real browser from code and takes a proxy per browser launch or per context, which fits hourly lines well: launch with the line, run the flow, close the browser as the hours run out. Teams use it on our lines for end-to-end tests that must come from a cellular network, for screenshot runs of mobile search results, and for checks of how a page loads at mobile latency. Works in Python, Node, Java and .NET.

  1. Launch the browser with proxy: { server: 'http://HOST:PORT', username: 'USER', password: 'PASS' } (or the equivalent dict in Python).
  2. Set the context's locale and timezoneId to the line's city so the browser matches the address.
  3. Navigate to an IP lookup page first and assert the carrier before the test proper.
  4. Call the rotation link between test cases if each case should start from a new address.
  • Use socks5://HOST:PORT as the server if you need UDP or want DNS to resolve through the line; pass credentials the same way.
(partner link)

Scrapy

Scraping framework

Scrapy is the framework for crawls that are bigger than a script but still finish in an afternoon. A proxy can be set per request through the meta dictionary or for the whole spider through a downloader middleware, and the rotation link slots into the middleware so the spider rotates itself every N responses. Scrapy's built-in throttling extension is useful on a mobile line because carriers prefer steady traffic to bursts.

  1. In the spider, set request.meta['proxy'] = 'http://USER:PASS@HOST:PORT' for each request, or do it once in a downloader middleware.
  2. Add a middleware that counts responses and calls the rotation link every few hundred.
  3. Enable the AutoThrottle extension so request pacing adapts to the line's latency.
  4. Run the spider while the hours last; if the crawl is going to need more than four hours, upgrade the line to a day in the dashboard.
  • Set DOWNLOAD_TIMEOUT so the crawl fails fast once the hours expire rather than hanging on refused connections.
(partner link)

FoxyProxy

Browser extension

FoxyProxy puts a proxy switch in the toolbar of Chrome or Firefox. Add the line once, flip it on for the job, flip it off when the meter stops. It is the tool for quick manual checks in your normal browser when a full anti-detect profile is more than the job needs: look at a page from a Houston mobile address, take a screenshot, done. Patterns let you send only certain sites through the line and leave the rest direct.

  1. Install FoxyProxy from the browser's extension store.
  2. Add a proxy: HTTP or SOCKS5 type, HOST, PORT, username and password, and give it the city as its name.
  3. Choose that proxy from the toolbar icon and load an IP lookup page to confirm.
  4. Switch back to direct when the hours end.
  • Clear the browser's DNS cache or restart it after switching if the first page still shows your home address.
(partner link)

Proxifier

System-wide proxy

Proxifier sends the traffic of any application on Windows or Mac through a proxy, including programs that have no proxy setting of their own. For hourly work it is the way to put a desktop app, a game client or a legacy tool on a mobile line for the length of a test, with rules that pick which programs go through the line and which stay direct. SOCKS5 is the natural choice here because it carries whatever the application sends.

  1. Add a proxy server: HOST, the SOCKS5 port, authentication with username and password.
  2. Create a rule that sends the application you are testing through that proxy and leaves everything else direct.
  3. Open the application and check its traffic in the Proxifier log; run an IP lookup from the same rule to confirm the address.
  4. Disable the rule when the purchase ends.
  • Enable remote DNS resolution in the proxy settings so hostnames resolve on the mobile side.
(partner link)

Shadowrocket

iOS client

Shadowrocket is a paid iOS app that routes the whole phone, or chosen apps, through an HTTP or SOCKS5 proxy. It is how iPhone users test an app or a mobile site from a US carrier address in a city they are not in, for the two hours it takes, without changing anything on the phone afterwards. Add the line as a server, connect, and your iPhone's traffic leaves from the line's city.

  1. Buy Shadowrocket from the App Store and open it.
  2. Add a server of type SOCKS5 or HTTP with HOST, PORT, username and password.
  3. Select the server and toggle the connection on; approve the VPN configuration prompt the first time.
  4. Open Safari on an IP lookup page to confirm the address.
  • Use per-app rules if only one app should go through the line; everything else stays on your own carrier.

Android Wi-Fi proxy

Android setting

Android can route a Wi-Fi connection's browser traffic through an HTTP proxy with no extra app, from the advanced options of the network you are connected to. It covers Chrome and most apps that respect the system proxy, which is enough for checking how a site or a web app behaves from a US mobile address on a real phone. Apps that ignore the system proxy need a proxy app instead, and the setting is per Wi-Fi network, so it does not follow you to another network.

  1. Open Wi-Fi settings, long-press the connected network and choose Modify, then Advanced options.
  2. Set Proxy to Manual and enter HOST and the HTTP PORT.
  3. Open Chrome; when it asks for the proxy credentials, enter the username and password.
  4. Load an IP lookup page to confirm, and set Proxy back to None when the hours are up.
  • Some Android builds do not prompt for proxy credentials; if a page fails to load, a proxy app that supports authentication is the fix.

The five values every tool wants

Open any line in the HourlyProxies dashboard and you will see a host, an HTTP port, a SOCKS5 port, a username and a password. That is the whole integration surface. The host and ports point at a real SIM from AT&T, T-Mobile or Verizon in a device we own in the city you chose; the username and password are the line's own, generated when you bought it. Either port reaches the same SIM and the same address. SOCKS5 adds UDP and remote DNS, which matter for a few desktop and phone tools; HTTP is simpler and is what most browser and code tools expect.

The line is identical regardless of how long you bought it for. Two hours, a day, a week or a month, it is the same host and the same credentials, so a tool configured during an hourly test needs no changes when the job becomes a monthly one.

Rotation from inside a tool

Each line has a rotation link, a plain URL that triggers a new address when it is fetched. That means any tool that can make an HTTP request can rotate the line: a curl call in a shell script, a requests.get in Python, a fetch in Node, a middleware in Scrapy, a pre-request script in Postman. Rotation takes a few seconds while the modem re-registers, so wait before the next request. The dashboard also offers rotation on a timer, which is useful when the tool itself has no hook to call the link from. There is no limit on how often you rotate inside your hours.

The one habit to build is rotating between units of work rather than inside them. A browser profile that is signed in, a crawl page that is half fetched, an API test mid-flow: finish it, then rotate.

Working to the meter

An hourly purchase has a definite end, and a well-behaved integration knows that. Set timeouts in scripts so a refused connection after the hours expire is a clean failure. Name browser profiles and proxy entries after the line and the city so you can tell which meter they are on. Run an IP lookup through the tool in the first minute of a purchase, before the expensive part of the job, so a misconfiguration costs seconds rather than an hour.

If the job is clearly outgrowing the purchase, add an hour or let the dashboard convert it to a day; the hours already paid count toward the day price, and your tool configuration does not change. A dollar or two for the upgrade is cheaper than restarting a crawl. If a tool you rely on is not on this list, write to [email protected] with its name and we will send you the settings that work.

Integration questions

Which port should I use, HTTP or SOCKS5?

HTTP for browsers, Postman, Playwright, requests and most scrapers. SOCKS5 for Proxifier, phone clients and anything that needs UDP or wants DNS resolved on the mobile side. Both reach the same SIM.

Do I need to change anything in my tool when I upgrade from hours to a day?

No. The host, ports and credentials stay the same for the life of the line. Only the time remaining changes.

Can I rotate the line from a script?

Yes. Fetch the line's rotation link with any HTTP client, wait a few seconds for the modem to re-register, and carry on. There is no rotation limit.

Every tool here takes a standard proxy

HTTP and SOCKS5 ports, username and password, on a dedicated US carrier line. Plans from $2 for 2 hours or $5/day.

View plans Test a proxy