Rotating
Proxies
Fresh IP on every request. No rotation logic to build, no proxy lists to maintain, no health checks to run. One API parameter activates a pool of 200M+ IPs across residential, ISP, and mobile tiers.
Rotating vs Sticky
Both modes are available on every request. The default is rotating. Add a session ID to switch to sticky.
Rotating (default)
Fresh IP on every request. Maximum anonymity. The target never sees the same IP twice.
- ✓Large-scale crawling
- ✓Search result collection
- ✓Price monitoring across many products
- ✓Any independent, single-page requests
"proxy_enabled": true Sticky sessions
Same IP for up to 10 minutes. Use when the target expects consistent identity across requests.
- ✓Login and authenticated scraping
- ✓Multi-page checkout monitoring
- ✓Pagination with session cookies
- ✓Any flow where IP consistency matters
"session": "checkout-flow-123" What You Don't Build
No CSV files of proxy URLs, no provider dashboards, no API keys per provider. One Spider API key covers everything.
No round-robin implementations, no weighted selection, no cooldown tracking. Spider handles it.
No ping checks, no success rate tracking, no dead proxy cleanup. Spider scores every IP per domain in real time.
No fallback chains, no "try residential then mobile" code. Spider escalates automatically on failure.
No per-country proxy lists, no geo-routing tables. One "country" parameter.
Code Examples
Rotating (default)
from spider import Spider
client = Spider()
# Each request gets a fresh IP
for url in product_urls:
result = client.scrape_url(url, params={
"proxy_enabled": True,
"country": "us",
})Sticky session
from spider import Spider
client = Spider()
# Same IP for the entire flow
for page in range(1, 20):
result = client.scrape_url(
f"https://example.com/results?page={page}",
params={
"proxy_enabled": True,
"session": "paginate-123",
}
)Pricing
Rotation is not a separate product. It is built into every proxy request at no additional cost. You pay only for the proxy tier you use.
ISP
Residential
Mobile
Frequently Asked Questions
How does automatic rotation work?
Every API request gets a different IP from the pool. Spider selects the next IP based on country targeting, proxy type, recent success rate, and IP freshness. There is no configuration needed. Set "proxy_enabled": true and rotation happens automatically.
Can I keep the same IP across multiple requests?
Yes. Pass a session ID in your request to pin the IP for up to 10 minutes. All requests with the same session ID will use the same IP. When the session expires, the next request gets a fresh IP. This is useful for login flows, pagination, and multi-page scraping.
How large is the rotation pool?
The total pool exceeds 200M IPs across residential, ISP, and mobile tiers. The available pool for a specific country depends on the proxy type and location. The US alone has 47M+ residential IPs in the pool.
What happens if an IP gets blocked mid-session?
Spider detects failed requests and automatically retries with a different IP from the same country and proxy tier. This happens transparently. You see a successful response (or a final failure if all retries are exhausted). Failed retries do not cost additional credits.
Do I need to build rotation logic in my code?
No. That is the point. Spider handles IP selection, rotation timing, health checking, retry logic, and geographic targeting. Your code sends a request with "proxy_enabled": true. The system does the rest. There are no proxy URLs, connection strings, or port lists to manage.
Does rotation work with headless browsers?
Yes. When you use Spider's browser rendering with proxy_enabled, each browser session gets its own IP. The browser fingerprint (user agent, screen size, WebGL hash) is matched to the proxy type so the full request looks consistent to the target site.