Skip to content

Use case · AI agents and data pipelines

Proxies for AI agents and data pipelines

Choose a route for a permitted task, check the actual result and measure an isolated sample before scheduling more work.

Get proxiesTry 1 GB for EUR 1.49from EUR 0.89 per GB · one price for every country

Once per customer. Cryptocurrency network minimums and fees vary.

The job

What this actually is.

Start with one verifiable task: read an authorised page or approved API response. Record the expected fields and state. An HTTP 200 with wrong content is not an accepted result.

Set allowed destinations, maximum steps, a whole-task deadline and finite retries in the runner. A proxy session name enforces none of these. Do not repeat an interrupted form submission or purchase automatically.

Configure the connection in the client making the request. MCP manages account and connection operations; it does not carry browser traffic. Use the MCP setup guide for tool inputs, masked credentials and purchase checks. Other tools and model API calls need separate configuration. Follow the Playwright setup or HTTP client guide.

Keep credentials outside prompts and logs. Built URLs can contain credentials. MCP build_proxy_url masks the password by default; revealing it exposes it in transcripts. Require separate approval for purchases and other writes.

Which pool

Mobile or residential for this job.

Choose residential for opt-in peer connections or mobile 4G/5G for carrier exits. Both shared pools use one GB balance. Check current locations; availability changes. API pool names residential and mobile correspond to username tokens peer and mbl.

POST /v1/traffic/build-url validates settings. POST /v1/traffic/test makes a separate server-side request, consuming traffic. When country_verified is true, exit_country is an observed classification for that test address. Otherwise exit_country is null. This proves neither physical location nor another request’s route.

Test your actual client too. On your own site, correlate a request identifier with destination logs. Record language, currency, cookies and account region separately. Consult the country troubleshooting guide for discrepancies.

Mobile 4G/5G proxies by the GB · Residential proxies by the GB · Check countries online now

Settings

Rotation, and the username that sets it.

Recommended rotation modes for AI agents and data pipelines, with the username each one needs
ModeUsername
Sticky sessionPrefers an existing binding while available; its IP can change. Preserve browser state separately. A session label creates no separate usage meter.USERNAME-peer-us-sid-agent7-rot-sticky
Per-connection rotationFor independent checks. Addresses can repeat, and requests can reuse connections. Rotation does not reset browser state.USERNAME-peer-us-rot-ondemand
Timed rotationTen-minute example for tasks tolerating route changes. The timer neither waits for workflow completion nor guarantees a different address.USERNAME-peer-us-rot-auto10

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.

A record for one permitted agent tasktext
Before the run
  Allowed destination: your approved page or endpoint
  Accepted result: required fields and expected page state
  Limits: maximum steps, total deadline, retry and traffic budgets
  Requested route: chosen pool, available country, rotation mode
  Session label: internal task label; never a password or API key

After the run
  Outcome: accepted / incorrect content / failed / unfinished
  Attempts: initial request and retries, counted separately
  Evidence: timestamp, client, stage, status and redacted error code
  Country: requested value and observed classification kept separate
  Usage window: refreshed shared-balance readings before and after
  Other workers in that window: yes / no / unknown

Decision
  Continue only if the task passed and stayed within its limits.
  Investigate errors or mixed usage before estimating the next run.
  Stop on access refusals; do not buy more traffic automatically.

This is a planning record, not executable code or measured results. Implement the limits in your runner and connect it using the client guides above. A session name does not meter traffic separately; retain only redacted evidence.

Cost

How to think about the GB.

Measure an isolated sample. Pause other workers and let earlier traffic reach the meter before recording the baseline. Run the sample, then wait for its usage before recording the final reading. Usage syncs every five minutes; keep timestamps. GET /v1/traffic and MCP get_traffic report the shared balance, not usage for an individual session. If other workers ran during the window, attribution is uncertain.

Count attempts, accepted results, failures and retries separately. Divide isolated usage, including failures, by accepted results. Zero accepted results means no per-result estimate. Client counters are not the account meter. Use the trial evaluation checklist, then budget the rest.

Record the failing stage and error code; next checks are listed on the docs page. Resolve authentication or balance errors before repeating. Stop on access refusals, respect destination limits and retry only safe operations within budget. Never purchase automatically to recover.

Traffic is EUR 1.99 per GB for a small order and EUR 0.89 per GB at the largest step, on either pool. The paid trial is 1 GB for EUR 1.49, once per customer and subject to eligibility. View pricing and traffic validity.

Limits

What we will not help with.

Use authorised destinations and respect their terms and crawl rules. A proxy provides connectivity, not permission, data accuracy or spending authority.

Read the acceptable-use policy before ordering. You accept it at checkout.

Start

Start with a small order.