validated availability data

Find the right proxy for the job.

A small, fast API for querying live proxy availability by country, reliability, latency, anonymity, and HTTPS support.

request.sh

$ curl -G \
  https://freeproxyapi.crawlora.net/proxies \
  -d exit_country=US \
  -d min_ratio_pct=80 \
  -d https=true \
  -d exclude_tampered=true

{
  "count": 50,
  "has_more": true,
  "proxies": [ ... ]
}

live snapshot

Know what is available now.

Aggregate health data is public. The page refreshes automatically from the same endpoint your monitoring can use.

Validated proxies—Loading live data…

Elite anonymity—

Under 500 ms—

Countries covered—known entry countries

Loading live stats…

—

Loading…

Country filters use the observed exit location. “Modified” marks proxies seen altering responses.
Proxy	Protocol	Exit country	Success	Latency	Anonymity	HTTPS	Last checked
Loading proxies…

Loading… Rows per page View JSON ↗

three lines to start

Simple enough to ship today.

Responses are JSON pages of up to 1,000 matching proxies. Use limit for a smaller page and offset with has_more to read further.

Choose a country

Use exit_country=US to find proxies with a US exit. country optionally filters the entry location.

Set a quality floor

Combine min_ratio_pct, max_latency_ms, and anonymity. Add https=true for HTTPS-capable proxies and exclude_tampered=true to skip proxies seen modifying traffic.

Cache the response

Public results are edge-cacheable for 30 seconds and limited by client IP to keep access fair.

javascript

const params = new URLSearchParams({
  exit_country: "US",
  min_ratio_pct: "80",
  https: "true",
  exclude_tampered: "true",
});
const response = await fetch(
  "https://freeproxyapi.crawlora.net/proxies?" + params
);
const { proxies } = await response.json();

Run carefully. Availability can change after a response is cached. Only use proxies and target websites you are authorized to access, and follow applicable laws, terms, and network policies. Before running large-scale validation in the cloud, consult your provider first: high-volume traffic can trigger abuse systems or be mistaken for scanning or DDoS-like activity.