Keep Your Proxies.
Get Our Anti-Bot Stack.
Already have a proxy contract, a compliance-approved IP range, or a pool tuned for a specific target? Plug it straight into FineData and keep every other part of the scraping stack -- TLS fingerprinting, CAPTCHA solving, JS rendering -- without paying a vendor markup on IPs you already own.
The Proxy Lock-In Problem
Most scraping APIs force you onto their proxy vendor, marked up and billed per GB or per request. That's a problem if you've already solved the proxy side of the equation.
Paying Twice for Proxies
You've already signed a contract with a residential or mobile proxy provider, but scraping APIs charge their own proxy markup on top.
IP Allowlisting Requirements
Some targets (banking portals, internal partner APIs, licensed data feeds) only accept traffic from pre-approved IP ranges you control.
Losing IP Reputation
You've spent months warming up a proxy pool's reputation on a specific target. Switching to a shared vendor pool resets that trust to zero.
Building Anti-Bot In-House
Owning proxies doesn't solve TLS fingerprinting, CAPTCHA solving, or JS rendering -- you still need the rest of the anti-bot stack.
How FineData Solves It
Bring the proxies, we bring everything else. One saved profile connects your pool to the full FineData anti-bot engine.
Any Proxy Type
Add up to 100 http, https, socks5, or socks5h endpoints per profile, across up to 10 profiles per account. Separate pools by client, region, or target site.
Flat Token Pricing
Requests through a BYOP profile cost a flat +1 token -- no vendor proxy surcharge, no per-GB billing. You already pay your proxy provider directly.
Encrypted & Validated
Proxy URLs and credentials are encrypted at rest. Every host is checked against private/reserved IP ranges before use to block SSRF attempts.
Two Calls to Go Live
Save your proxy list once as a profile, then reference its id on any scrape or async job request. Everything else -- retries, fingerprinting, CAPTCHA solving -- works exactly as it does with our own proxies.
Works with http, https, socks5, and socks5h proxies
rotation_mode: sticky keeps one exit IP per session
Mutually exclusive with proxy_country / use_residential / use_isp / use_mobile
import requests
# 1. Save your proxy pool as a BYOP profile (dashboard or API)
profile = requests.post(
"https://api.finedata.ai/api/v1/proxy-profiles",
headers={"x-api-key": "fd_your_key"},
json={
"name": "eu-residential-pool",
"proxies": ["http://user:pass@proxy1.example.com:8000", "..."],
"rotation_mode": "sticky",
}
).json()
# 2. Reference the profile id on any scrape request
response = requests.post(
"https://api.finedata.ai/api/v1/scrape",
headers={"x-api-key": "fd_your_key"},
json={
"url": "https://example.com/account",
"proxy_profile_id": profile["profile_id"],
"proxy_sticky": True,
}
)
data = response.json()
print(data["tokens_used"]) # flat +1 token for BYOP, not the vendor surchargeRequires the PAYG plan or higher (Team S/M/L, Scaling). See the Proxy & Geo-Targeting docs for the full reference.
Why Teams Bring Their Own Proxies
Own Your IP Reputation
Keep using proxies you've already warmed up on a specific target instead of resetting trust with a shared pool.
Predictable Costs
Flat +1 token per request regardless of proxy type -- no surprise per-GB or per-IP vendor billing.
Sticky Sessions
rotation_mode: sticky plus proxy_sticky keeps one exit IP for an entire warmup-to-fetch flow.
Compliance-Friendly
Route through your own IP-allowlisted ranges for licensed data feeds, banking portals, or internal partner APIs.
Frequently Asked Questions
What is Bring Your Own Proxy (BYOP)?
+1 token
instead of the usual proxy surcharge.
Which plans have access to BYOP?
How many proxies can I add to a profile?
http,
https,
socks5, or
socks5h). You can create
up to 10 profiles per account, so you can separate pools by client, region, or target site.
Are my proxy credentials secure?
Can I keep the same exit IP across a session with BYOP?
rotation_mode
to sticky and pass
proxy_sticky: true on the
request to keep the same proxy for an entire browser session -- useful for anti-bot flows where
warmup and API calls must share one IP.
Can I combine BYOP with proxy_country or use_residential?
proxy_profile_id is
mutually exclusive with proxy_country,
use_residential,
use_isp, and
use_mobile -- once you
select a BYOP profile, FineData routes exclusively through your own proxies for that request.
Connect Your Proxies in Minutes
Start with free tokens, then upgrade to PAYG or a Team plan to save your first BYOP profile and route requests through the proxies you already trust.