const response = await fetch(
'https://intrude.io/api/v1/proxies?min_uptime=95&sort=reliability'
);
const { data, meta } = await response.json();
console.log(meta.total, data[0]);PUBLIC INTERFACE / VERSION 1
BUILD ON
THE SIGNAL.
One request.
Live intelligence.
The Intrude API is open for read-only use. It returns proxies that are currently live, plus verification evidence and an explainable reliability score.
curl "https://intrude.io/api/v1/proxies?country=US&min_uptime=95&max_latency=1500&limit=25"import requests
response = requests.get(
"https://intrude.io/api/v1/proxies",
params={"country": "US", "min_uptime": 95, "limit": 25},
)
response.raise_for_status()
print(response.json()["data"])GET /api/v1/stats
Returns a fast, source-private snapshot of the network. Protocol counts include live proxies only and may overlap because one endpoint can support several transports. https is the unique union of HTTPS CONNECT and TLS-to-proxy support.
curl "https://intrude.io/api/v1/stats"data.inventorydata.protocolsdata.qualitydata.performancedata.coveragedata.freshnessdata.pipelineGET /api/v1/proxies
Every live record includes independently tested supported_protocols and protocol_latencies. HTTPS CONNECT tunneling, TLS-to-proxy, SOCKS4, and SOCKS5 are tested separately; HTTP-only endpoints are excluded from the useful live inventory. The legacy supports_https field remains as an alias for HTTPS CONNECT support.
USLos AngelesELITEfalseHTTPS_CONNECTtrue95150010Cloudflarereliability100 / 0GET /api/v1/rotate
Returns one uniformly random proxy from the live nodes matching your filters. Every request performs a fresh selection and responses are never cached. The response includes the size of the matching pool, normalized filters, selection method, generation time, and quota state alongside the selected proxy.
curl "https://intrude.io/api/v1/rotate?country=US&protocol=SOCKS5&blacklisted=false&min_uptime=90&max_response_time=2500&min_score=70"US / MiamiSOCKS5false250090 / 10070 / 10010ELITE / CloudflareGET /api/map
Returns coordinate clusters instead of thousands of raw records. Use grid to control geographic precision, then request /api/map/proxies?lat=…&lng=…&grid=… for the live proxies inside a selected cluster.
curl "https://intrude.io/api/map?grid=3&min_uptime=90&max_latency=2500"curl "https://intrude.io/api/map/proxies?lat=34.05&lng=-118.25&grid=3"Every endpoint.
Real data.
Configure and execute every public Intrude endpoint directly from the browser. Requests use the same routes, validation, responses, and rate limits as your application.
Network stats
Read a source-private snapshot of live protocol, quality, performance, coverage, and pipeline health. Each click runs a real request against the current public dataset.
// Configure filters, then send a live request.A score you can audit.
The score combines 55% lifetime uptime, 20% verified latency, 15% confidence from check volume, and 10% verification recency. Blacklisted proxies receive a 20-point penalty. Raw inputs remain in every response.
Fair-use by default.
Public traffic is limited to 60 requests per minute per client and endpoint scope. Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset. Rotation responses are never cached.
Assume public proxies are hostile.
Never send passwords, session cookies, API tokens, payment data, or private information through an untrusted proxy. Intrude verifies reachability and observable reputation; it does not certify an operator’s intent.