Skip to content
Get access

Residential proxies for web data

Real devices. Standard HTTP.

Residential IPs.
For web data.

Connect your scrapers, browsers, and data pipelines to real residential devices. Control IP rotation and session behavior through one HTTP proxy endpoint.

Talk to salesConfigure your proxy

Works with curl, Python, Node.js, and Playwright.

Your applicationOne endpoint
RESIDENTIAL EXIT
01PhoneExample exit device
GET example.com200 OK
NETWORK IN MOTIONIllustrative routing, not live traffic.
Residential IPs.
Your routing controls.HTTP proxy HTTPS via CONNECTThree modes rotate, sticky, fixedExit regions + country exclusions

01 / Residential proxy network

Real devices.
Flexible routing.

Route traffic through phones and desktops running partner apps. Choose session behavior and exit regions for each workload.

An elevated railway weaving through a dense city at dusk, editorial artwork
RESIDENTIAL PROXIES.
BUILT FOR WEB DATA.
Residential exit devices

Your traffic.
Real devices.
One endpoint.

Exit regions are determined from device IPs, not self-reported locations.
Discuss your proxy requirements
01

Control your exit regions.

Select continent regions and exclude specific countries in the proxy username. Keep routing policy with each connection.

CONTINENTS + EXCLUSIONS
02

Choose how IPs rotate.

Rotate for each connection, use sticky sessions that can move if an exit drops, or use fixed sessions that never switch exits.

ROTATE / STICKY / FIXED
03

Keep your existing tools.

Add a proxy URL to your HTTP client or browser automation tool. No ports.io SDK or crawler migration required.

HTTP PROXY INTEGRATION

02 / Connect your existing stack

Add a proxy.
Keep your code.

Configure your exit region and session mode, then copy the example into your HTTP client. Use your workspace key to authenticate.

01

Configure your proxy

These controls only update the example. No request is sent.

request.sh
curl --proxy \
  "http://v1_rotate_regions_NA:rp1_YOUR_SECRET@PROXY_HOST:PORT" \
  --max-time 30 \
  "https://example.com"
North America / rotating sessionHTTP(S)

Replace rp1_YOUR_SECRET and PROXY_HOST:PORT with your key and endpoint. Requires cURL.

01 / CONNECTUse your existing HTTP client.

02 / ROUTEPut region and session options in the username.

03 / BUILDBring the response into your workflow.

03 / Proxy use cases

Web data for
your business.

01
COLLECT + INDEX

Web scraping & AI data

Connect your crawler to residential IPs to collect public pages for search indexes, research, and AI datasets. Your application handles extraction and processing.

  • Public page collection
  • Search indexing
  • AI data pipelines
02
MONITOR + VERIFY

SEO & ad verification

Route your monitoring tools through residential exits to inspect public search results, ad placements, and landing pages.

  • Search monitoring
  • Ad placement checks
  • Landing page QA
03
TRACK + COMPARE

Price monitoring

Use your scraper to track public prices, product listings, and availability. Feed the results into your pricing and market research tools.

  • Catalog monitoring
  • Price intelligence
  • Availability checks

Built for responsible collection of public data. Respect site terms, access controls, and applicable requirements.

Discuss access and pricing

Proxies for
your workload.

Share your target sites, required regions, session needs, and expected bandwidth. Talk to our team about access, pricing, and availability.

Talk to sales

Proxy questions, answered

How ports.io
works.

Does ports.io crawl and index pages for me?

ports.io provides the residential proxy connection. You bring the crawler, indexing pipeline, or data collection application. The network gives your requests a residential exit point.

Can I keep the same IP for multiple requests?

Sticky sessions use one exit and move to another eligible exit if it disconnects. Fixed sessions never switch and fail if their exit is unavailable. Both bindings expire after 5 minutes idle or 60 minutes total.

What do I need to get started?

An API key from your workspace and any client that speaks to an HTTP(S) proxy. Share your target regions, public-data use case, and expected bandwidth with our team to plan your setup.

Contact

Talk to sales

Tell us which sites you collect from, the exit regions you need, and your expected bandwidth. Our team can discuss proxy access, pricing, and availability for your workload.