Use case · AI agents and data pipelines
Proxies for AI agents and data pipelines
One credential an agent can steer itself: pool, country and session are tokens in the username.
The job
What this actually is.
Browser agents, retrieval pipelines and scheduled jobs all need an egress they can choose at runtime. An agent researching a market has to read that market from inside it; a pipeline collecting public pages for an index has to keep its country fixed so the corpus stays comparable.
The awkward part of giving that to an agent is usually credentials. A pool of separate proxy endpoints means a config to keep in sync, a secret per endpoint and no clean way for the agent to say "the same thing, but from France".
Which pool
Mobile or residential for this job.
Residential is the working default: widest country coverage, one balance, and the pool most agent tasks want. Mobile 4G/5G is there for the six countries where a task specifically needs a carrier exit, and it is reached by changing mbl for peer in the same username.
This is where our API earns its place. POST /v1/traffic/build-url builds and validates a URL from pool, country, rotation and session; POST /v1/traffic/test reports the exit IP and the latency, not a verified country; GET /v1/traffic reports the balance. The same calls exist as MCP tools, so an agent can construct its own connection, test it and read what it has left without a human editing a config file.
Mobile 4G/5G proxies by the GB · Residential proxies by the GB · Check countries online now
Settings
Rotation, and the username that sets it.
| Mode | Username | Use it for |
|---|---|---|
| Sticky sessionOne agent run, one session name. The whole task keeps one device, and the session name is a natural place to put the run id. | USERNAME-peer-us-sid-agent7-rot-sticky | One agent run, one session name. The whole task keeps one device, and the session name is a natural place to put the run id. |
| New IP on every connectionA fan-out of independent fetches in a pipeline, where requests have nothing to do with each other. | USERNAME-peer-us-rot-ondemand | A fan-out of independent fetches in a pipeline, where requests have nothing to do with each other. |
| Timer, 5 to 60 minutesA long-running scheduled job where the exit should move on its own without the job managing sessions. | USERNAME-peer-us-rot-auto10 | A long-running scheduled job where the exit should move on its own without the job managing sessions. |
USERNAME stands for the account part of your username; it and the password appear in the dashboard after a fulfilled purchase. Swap the two-letter country code for an available market. Every token is listed in the docs.
# the API builds and validates the URL from pool, country, rotation and session
curl -sS -X POST https://api.portproof.org/v1/traffic/build-url \
-H "Authorization: Bearer $PORTPROOF_API_KEY" -H "Content-Type: application/json" \
-d '{"pool":"residential","country":"US","rotation":"sticky","session":"agent7","protocol":"http"}'
# then test the connection from our side: it reports the exit IP and the latency, not a verified country
curl -sS -X POST https://api.portproof.org/v1/traffic/test \
-H "Authorization: Bearer $PORTPROOF_API_KEY" -H "Content-Type: application/json" \
-d '{"pool":"residential","country":"US","rotation":"sticky","session":"agent7"}'
# the same username, written by hand
# USERNAME-peer-us-sid-agent7-rot-stickyThe same three calls exist as MCP tools, so an agent can build, test and meter its own egress without a human editing a config file.
Cost
How to think about the GB.
Agents are expensive in traffic because they render. A browser agent loads the whole page, and it often loads it more than once while it decides what to do. Meter per run: give each run its own session name, read the usage counter after the first one, and use that figure to budget the rest. Usage alerts fire at 80 percent of the balance and again at the cap.
Give the agent the errors as well as the URL. It should handle 407 when the balance is used up or the credentials changed, 502 when no device is online in the country it asked for, and 429 when it opens too many connections or sessions at once, and it should back off rather than retry in a tight loop. All of them are listed on the docs page with their codes.
Traffic is EUR 4.50 per GB for a small order and EUR 2.50 per GB at the largest step, on either pool. The paid trial is 0.5 GB for EUR 2.90, once per customer and subject to eligibility. View pricing and traffic validity.
Limits
What we will not help with.
Country-accurate access and rate discipline, not evasion. An agent may not create accounts, work around a protection, or ignore a site’s stated crawl rules on your behalf, and an autonomous loop is still your responsibility under the acceptable-use policy you accept at checkout.
Read the acceptable-use policy before ordering. You accept it at checkout.
Start