node-fetch / undici · PROXY SETUP

node-fetch / undici proxy setup

fetch() in Node — the built-in one and the node-fetch package. Point it at the Eveses residential pool with the configuration below — the geo lives in the username, so nothing else in your setup has to change to move country.

proxy.eveses.com:12321 · SOCKS5 on 32325 · 199 countries · from $7.35/GB

Get proxies →All integrations
Watch out

Node's global `fetch` is undici, which does not read `HTTPS_PROXY` and does not accept an `agent` option. It needs `ProxyAgent` passed as `dispatcher`. node-fetch (the package) is the opposite — it wants `agent`.

Configuration

// Node 18+ built-in fetch (undici)
import { ProxyAgent } from "undici";

const dispatcher = new ProxyAgent({
  uri: "http://proxy.eveses.com:12321",
  token: "Basic " + Buffer.from(
    "eveses_user_country-us:YOUR_PROXY_PASSWORD").toString("base64"),
});
const res = await fetch("https://target-site.com", { dispatcher });

// node-fetch package
import fetch from "node-fetch";
import { HttpsProxyAgent } from "https-proxy-agent";
const agent = new HttpsProxyAgent(
  "http://eveses_user_country-us:[email protected]:12321");
await fetch("https://target-site.com", { agent });

Change country without touching node-fetch / undici

Germanyeveses_user_country-de
Sticky 30 mineveses_user_country-de_session-ab12cd34_lifetime-30m

The geo and the session live in the username, not in the host or the port. Every configuration on this page stays exactly as it is when you move country — you edit one string. 199 countries are addressable, with city and state tokens inside most of them.

FAQ

How do I set a proxy in node-fetch / undici?›
Point it at proxy.eveses.com on port 12321 for HTTP, or 32325 for SOCKS5, and authenticate with your Eveses proxy username and password. The exact syntax is in the snippet above. Node's global `fetch` is undici, which does not read `HTTPS_PROXY` and does not accept an `agent` option. It needs `ProxyAgent` passed as `dispatcher`. node-fetch (the package) is the opposite — it wants `agent`.
How do I choose the country node-fetch / undici exits from?›
Append a geo token to the USERNAME rather than changing the host: eveses_user_country-de reaches Germany, eveses_user_country-us the United States. 199 countries are addressable this way, and city or state tokens narrow it further. Nothing else in your node-fetch / undici configuration changes.
How do I keep the same IP across requests in node-fetch / undici?›
Add a session token — eveses_user_country-us_session-ab12cd34_lifetime-30m — and every request carrying that username exits from the same address until the lifetime runs out. Drop the token and each request rotates to a fresh IP.
What does this cost?›
Residential traffic is billed by the gigabyte from your Eveses wallet: $7.35/GB at 1 GB, falling to $2.57/GB in volume. There is no per-tool charge, and the same credentials work in every tool at once.
Paste your own curl → get it in javascript →

Other integrations

ScrapySeleniumPuppeteerPlaywrightPython requestsHTTPXaiohttpAxiosGuzzlecURL

Run node-fetch / undici through residential IPs

$7.35/GB at 1 GB, $2.57/GB in volume — same credentials in every tool.

Get proxies →