Geo-Availability Checker

Checks whether a set of URLs are reachable, blocked, or redirected when accessed from specific countries, using residential proxies.

No dataset output. This Actor doesn't scrape or return page content, and there's nothing to download as JSON/CSV. Each check is an action — it runs, logs a pass/fail line to the run log, and charges for having happened. That's the whole output.

Input

{
  "urls": ["https://apify.com"],
  "countries": ["US"],
  "expectedOutcome": "reachable",
  "timeoutSecs": 20,
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}

urls: ["https://apify.com"] and countries: ["US"] are the schema defaults, so this is also what Apify's automated daily test run will use — keep them pointed at something that will reliably resolve. Every url is combined with every country unless you use the advanced checks field to list exact {url, country, expected} triples yourself (useful when different URLs need different expected outcomes).

expectedOutcome can be "reachable", "blocked", or "any" (just record what happened, no pass/fail judgment).

Setting up monetization (do this in Apify Console, not in code)

1. Actor page → Publication tab → Monetization section.
2. Choose Pay per event (PPE).
3. Define one custom event named exactly check-performed, matching the eventName used in src/main.js. Suggested starting price: $0.02 per check (raw infra cost for a plain HTTP fetch through residential proxy runs roughly $0.004-$0.007 per check, so this leaves a healthy margin — revisit after real runs via Insights → Monetization).
4. Leave Pay-per-usage/Rental off — PPE is the only model that pays you here.
5. Fill in billing details and identity verification so payouts can process.
6. Set your payout method to PayPal if you expect to be below the $100 wire transfer minimum for a while — PayPal's floor is $20.

Why no headless browser

This uses got-scraping (plain HTTP requests with proxy + header/TLS fingerprint handling) instead of Playwright/Puppeteer. Most availability/ geo-block checks don't need JS execution, and skipping the browser keeps Compute Unit usage — and therefore your infra-cost deduction — low, which is what protects your margin on cheap, high-volume runs.

Local development

npm install
apify run

Requires the Apify CLI and an Apify account (free plan is enough to build and test) so Actor.createProxyConfiguration() and Actor.charge() have something to talk to.