Geo-Location

Sentinel Scout allows scraping jobs to be executed from specific countries, cities, or ISPs using its distributed mobile proxy network.

Geo-Location in Sentinel Scout

Geo-location is a critical feature of Sentinel Scout. It allows users and AI agents to target content as it appears in specific countries, cities, or even from certain ISPs. This is essential for:

• Accessing geo-restricted content (e.g., websites only available in certain regions).

• Running localized market research (e.g., how prices differ by country).

• Verification of localized versions of websites.

• Training AI systems on region-specific datasets.

---

How Geo-Location Works

1. Proxy Node Assignment

   • Scout maintains a distributed pool of Android-based mobile proxies and other nodes.

   • Each node is tied to a real-world location (country, city, ISP).

   • When a scraping job is submitted with a geo-parameter, the system routes the job to the best available node matching the requested region.

2. Fallback Routing

   • If the selected location fails (blocked, timeout, etc.), Scout automatically rotates to another proxy/node within the same region or a nearby one.

   • This ensures high success rates even for restrictive targets.

3. Location-Aware Distribution

   • The task queue tags jobs with geo-preferences.

   • Nodes are dynamically matched using:

     • Country codes (ISO-2 standard).

     • City names.

     • ISP identifiers.

---

Technical Commands & Endpoints

Note: This section provides only an overview. The full API documentation with detailed request/response schemas is available in the API Docs (Advanced) section and should be referred to for implementation.

1. Get Available Countries

Retrieve the full list of supported countries (ISO-2 codes).

curl -X GET "https://api.scout.sentinel.co/api/v1/generic/countries" \
  -H "accept: application/json"

Example Output:

[
  "US",
  "DE",
  "IN",
  "JP",
  "BR",
  "AU",
  "GB",
  "CA"
]

---

2. Get Available Cities

For more granular control, fetch the cities where proxies are available.

curl -X GET "https://api.scout.sentinel.co/api/v1/generic/cities" \
  -H "accept: application/json"

Example Output:

[
  "New York",
  "London",
  "Mumbai",
  "Tokyo",
  "Berlin",
  "Sydney",
  "Toronto"
]

---

3. Get Available ISPs

Target a scraping task from specific Internet Service Providers (ISPs). Useful for avoiding network-based restrictions or testing ISP-specific access.

curl -X GET "https://api.scout.sentinel.co/api/v1/generic/isps" \
  -H "accept: application/json"

Example Output:

[
  "Verizon",
  "AT&T",
  "Jio",
  "Vodafone",
  "Comcast",
  "Deutsche Telekom"
]

---

4. Submit a Scraping Job with Geo-Parameters

Submit a job targeting Wikipedia, requesting content as seen from India.

curl -X POST "https://api.scout.sentinel.co/api/v1/probe" \
  -H "Authorization: Bearer <API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://en.wikipedia.org/wiki/Artificial_intelligence",
    "countryCode": "IN",
    "tagsToStripOff": ["script", "style"],
    "fallBackRouting": true,
    "antiBotScrape": true,
    "outputFileExtension": "EXTENSION_HTML"
  }'

Example Response:

{
  "taskId": "91f5b7a8-2b53-4a01-8249-f93e6f7767b1",
  "status": "SUBMITTED",
  "message": "Scraping job submitted successfully."
}

---

5. Location-Wise Task Distribution (Conceptual)

• Country-specific routing: Pass "countryCode": "US" to fetch U.S.-specific content.

• City-specific routing: Use /api/v1/generic/cities to find "London", then pass "city": "London" in your job (if supported).

• ISP-specific routing: Pass "isp": "Jio" to mimic a Jio mobile subscriber in India.

---

Best Practices

• Always check /generic/countries before submitting geo-specific jobs to ensure the country is currently supported.

• Use fallback routing ("fallBackRouting": true) to maximize scraping success in restrictive regions.

• Combine antiBotScrape with geo-targeting for the most resilient results.

• If your workflow requires real-time results, use the Synchronous API (/api/v1/probe/sync) with the same geo-parameters.

---

Why Mobile Proxies Work Best

• Websites often treat mobile IPs as legitimate user traffic, reducing block rates.

• Mobile IPs cycle dynamically, making it harder to blacklist.

• CAPTCHAs are less frequent on mobile networks compared to data centers.

---

In summary: Geo-location in Sentinel Scout is flexible and powerful — enabling scraping jobs to be executed with country, city, and ISP-level precision, while leveraging the natural resilience of mobile Android proxies for better success rates.