215M+ IPs across 199 countries.
Access residential proxies with country targeting through the API or a direct proxy connection. Pay for bandwidth and compute from your Spider credit balance. Failed requests cost $0.
Where Spider can route from.
Click any country to see its proxy pool, supported types, and a pricing summary.
Largest pools by IP count.
Proxies for your workflow.
Choose a country and connect with your API key. Use the Scrape API to fetch pages or keep your existing proxy client.
Country targeting
Set country_code in your API request to choose a country. Browse the directory below for available locations.
Residential IPs
Check local search results, compare prices, and verify ads using residential IP addresses in your target country.
Usage-based billing
Pay per GB of bandwidth and per CPU-minute of compute from your Spider credit balance. Failed requests cost $0.
HTTP, HTTPS, and SOCKS5
Connect through the protocol your proxy client supports. The examples below show how to authenticate and make a request.
API or direct proxy
Use the Scrape API to fetch a page, or connect your existing client to the direct proxy endpoint.
One API key
Use the same API key for the Scrape API and direct proxy. Manage your credentials and credit balance in one account.
All 199 countries.
Route through any country.
Two ways in, one API key: the Scrape API for managed end-to-end requests, or a direct HTTP/HTTPS/SOCKS5 proxy for clients you already use. Rotation and retry are the default on both. There is nothing else to set up.
curl -X POST https://api.spider.cloud/scrape \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com",
"country_code": "us",
"return_format": "markdown"
}'Residential proxies.
Access websites through residential IP addresses in your chosen country. Use them for price checks, local search results, and ad verification.
Residential Proxies
- Trust
- Highest
- Best for
- Demanding sites, account management, ad verification
Route through real consumer connections. Residential IPs belong to home networks, so sites treat the traffic like any household visitor.
Common questions.
What types of proxies does Spider offer?
Spider offers residential proxies. They route through real consumer connections, so sites treat the traffic like any household visitor.
How many proxy locations are available?
Spider provides proxy coverage in 199+ countries across every inhabited continent. The total pool exceeds 200 million IPs, with the largest coverage in the United States, United Kingdom, Germany, Brazil, and Japan.
Do I need to manage proxy rotation myself?
No. Spider handles automatic IP rotation on every request. You can optionally pin a session to a single IP using sticky sessions, or let the system rotate IPs automatically for maximum anonymity.
How do I target a specific country?
Pass the two-letter ISO country code in the "country_code" parameter of your API request. For example, set "country_code": "de" to route through a German proxy. If Spider cannot fulfill a request from your selected country, it returns an error.
What is the average proxy latency?
Residential proxies average 150-300ms depending on the target country. Spider automatically selects the fastest available proxy in your target location.
Is there a bandwidth limit on proxy usage?
There are no hard bandwidth caps. Usage is metered: you pay per gigabyte of bandwidth plus a small compute charge per minute of CPU, billed from one prepaid credit balance. Failed requests are billed at $0, and your balance never expires. There is no subscription and nothing resets monthly.
Can I use proxies with headless browsers?
Yes. Spider's proxy network integrates directly with its headless browser infrastructure. Every request already goes through a residential proxy, so turn on browser rendering to pair residential IPs with a real browser engine.
Do you support SOCKS5 or HTTP CONNECT proxies?
Yes. Spider exposes an HTTP/HTTPS proxy on proxy.spider.cloud:8888 (HTTP) and :8889 (HTTPS), plus a SOCKS5 proxy on proxy.spider.cloud:8887. Use your API key as the username and optional parameters such as country_code=us as the password.
How does pricing work for proxy requests?
Proxy requests bill like every other Spider request: bandwidth per gigabyte plus compute per minute of CPU, denominated in credits from one prepaid balance. Every request goes through a residential proxy by default. There is no separate proxy invoice or minimum commitment, retries cost nothing extra, and failed requests are billed at $0.
What happens if a proxy request fails?
Spider retries failed requests automatically at no extra charge. If the request still fails, you receive an error and are billed $0.
Residential Proxies, Briefly
What are residential proxies?
Residential proxies route requests through IP addresses that internet service providers assign to real households, so your traffic looks like a regular visitor browsing from home. That matters because many sites treat traffic differently by IP type, and residential IPs share the same address space as everyday users.
Residential proxies work for strict sites, ad verification, account work, price monitoring and SERP scraping. They support country-level targeting, which is what makes region-specific pricing, search results, and ad placement visible from where your users actually are.
How Spider makes them simple
Use residential proxies through the Scrape API or connect your existing client to the direct proxy endpoint. Set "country_code" to choose a country. Spider handles IP rotation and automatic retries.
Billing is metered from one prepaid credit balance: bandwidth at $1/GB (measured on content before transformation) plus compute at $0.0001 per CPU-minute. No monthly minimums, no separate proxy invoice, and the same balance covers crawling, browser sessions, and AI extraction.
Start routing in 30 seconds.
One API key. No proxy vendor to manage.
2,500 free credits, worth $0.25, if your signup passes our checks. No card required.