Infrastructure · How Refetcher works

A 100M+ IP network
behind every request.

Refetcher routes every request through a 100M+ IP residential proxy network spanning 195 countries. You never see it — you just see clean JSON. This page is what's underneath.

100M+ residential IPs 195 countries Ethically sourced
The pipeline

What happens
to your request.

The journey of one requestrouting live
You

Send a request

Refetcher

Authenticate & route

Residential network

Routed through 100M+ IPs

84.232.41.7 · Frankfurt

Platform

Seen as a real visitor

Delivered

Clean JSON returns

01 · Request

You send any public URL.

Make a simple HTTP POST request containing the target URL. There is no need to log in, manage session state, bypass device fingerprinting, or coordinate cookie jars on your end — our API handles the entire handshake automatically.

HTTP POST Any public URL Zero configuration
02 · Route

Refetcher schedules & structures.

Our API gateway validates your request, checks permissions, determines the correct target platform, and prepares custom headers. We dynamically rotate user agents and select the optimal scraper protocol to avoid detection.

API gateway Header rotation Smart scheduling
03 · Proxy

Routed through a 100M+ IP residential pool.

Every request exits through a residential IP belonging to a real consumer device in one of 195 countries. Because the IP belongs to a real home network rather than a datacenter, platforms view the request as a normal visitor.

100M+ IPs 195 countries Ethically sourced Per-request rotation
04 · Extract

Per-platform engines pull the data.

Social networks change their markup constantly. Our dedicated extraction engines parse pages, retrieve the raw HTML or API payloads, bypass platform-level rate limits, and feed clean fields into our normalization parser.

5 platforms 24/7 monitoring Markup repair No rate limiting
05 · Deliver

Unified, clean JSON returned.

Raw platform responses are reshaped into one predictable JSON schema — returning the same metrics, post, and author structure whether the target was a Reel, a Tweet, or a Short. If a scrape fails, we retry through fresh IPs automatically.

One schema Auto-retry Failures free Public status
Why residential matters

Platforms block scripts.
Not people.

Social platforms recognize datacenter IP ranges instantly and block them on sight — that's why home-built scrapers break inside a month. Residential IPs belong to real consumer devices on real ISPs, so the traffic is indistinguishable from a person browsing. Serious scraping operations run on residential networks for exactly this reason, and Refetcher routes every request through one. The difference shows up in a single number: a 99.47% success rate, published live.

datacenter vs residential
# Same target, two exits

→ via datacenter IP
HTTP/2 429   # blocked: known datacenter range

→ via Refetcher's residential network
HTTP/2 200
{ "platform": "instagram", "success": true,
  "metrics": { "views": 1284203, "likes": 48211 } }
Built for volume

From your first scrape
to your first 100 million.

Enterprise options.

While you can start self-serve instantly, we support high-volume operations with custom volume discounts, dedicated routing nodes, custom SLAs, and invoiced billing. Contact us for custom enterprise setups.

volume discountscustom contractsinvoiced billing

Capacity to burn.

The network is engineered for hundreds of millions of scrapes a day. Batch up to 50 URLs per request, run as many requests in parallel as you like, and let the routing layer absorb the load.

batch × 50parallel safeburst friendly

Proof, not promises.

Success rate, latency and uptime are published live on the status page — and a public, visitor-triggered 1M-scrape benchmark is on its way, so you can watch the network clear a million posts yourself.

live statuspublic benchmarkopen numbers
The rules we run by

Big network.
Clean conscience.

Public data only

Refetcher retrieves what anyone can see in a browser without logging in: public posts, public profiles, public counts. No private accounts, no DMs, no login-walled content.

No credentials, ever

We never ask for platform logins, session cookies or tokens — yours or anyone else's. One Refetcher API key is the only credential in the system.

Ethically sourced capacity

Residential capacity comes through routing partners whose networks are built on consenting, compensated peers — the same sourcing standard the largest providers in the industry hold themselves to.

You pay for results only

If a scrape fails — private post, deleted page, network miss — it costs you nothing. The billing model only works when the network does, which keeps our incentives exactly where yours are.

Straight answers

The network, in plain English.

How big is Refetcher's proxy network? +

Refetcher routes every request through a 100M+ IP residential proxy network spanning 195 countries. The figure reflects total contracted network capacity across our routing partners.

Does Refetcher use residential proxies? +

Yes. Every scrape exits through a residential IP — an address belonging to a real consumer device — rather than a datacenter range, so requests look like ordinary user traffic to Instagram, TikTok, YouTube, X, and Facebook.

How does Refetcher avoid getting blocked? +

Three layers: every request routes through a 100M+ IP residential proxy network spanning 195 countries, IPs rotate continuously, and per-platform extraction engines are monitored and repaired around the clock. The result is published openly as a rolling success rate on the public status page.

Can Refetcher handle enterprise-scale volume? +

Yes. The network is engineered for hundreds of millions of scrapes a day. You can start instantly self-serve, and we support high-volume operations with volume discounts, custom SLAs, and invoiced billing.

Do I need to bring my own proxies to use Refetcher? +

No. Residential proxy routing, rotation, retries and parsing are all included in the price. You send a public URL and receive normalized JSON.

The network is included.

Proxies, rotation, retries and parsing — all inside one $0.90 price. You just get the data, starting with $10 free.

Get your API key