# US Water System & Utility Leads Scraper (EPA SDWIS) (`scrapesage/us-water-system-scraper`) Actor

Scrape every US public water system from the official EPA SDWIS database: utility name, admin contact, email, phone, address, population served, service connections, owner & source type, plus health-based violations. Filter by state, size & type. B2B water-utility leads + monitoring.

- **URL**: https://apify.com/scrapesage/us-water-system-scraper.md
- **Developed by:** [Scrape Sage](https://apify.com/scrapesage) (community)
- **Categories:** Lead generation, Agents, Integrations
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.75 / 1,000 water system records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## US Water System & Utility Leads Scraper (EPA SDWIS)

Extract **every public water system in the United States** — drinking-water utilities, water districts, municipal systems, mobile-home parks, HOAs, schools and more — straight from the **official EPA SDWIS (Safe Drinking Water Information System)** database. Each system comes with its **administrative contact, email, phone and mailing address**, plus **population served, service connections, owner type, water source**, and an optional **drinking-water violation / compliance history**.

No login, no cookies, no browser, **no API key** — fast JSON extraction from the EPA Envirofacts service with a derived **lead score** on every record.

### Why this water system scraper?

Most "water" scrapers on the market either dump raw SDWIS rows with no contacts, or focus on hydrology gauges and risk reports. This actor ships the **richest water-utility lead dataset in the category** — built for sales, not just research:

| Data | Typical scrapers | This actor |
|---|---|---|
| Administrative contact **name** | ❌ | ✅ |
| Contact **email** | ❌ | ✅ |
| Contact **phone** + extension | ❌ | ✅ |
| Full mailing address | partial | ✅ |
| Population served + size tier | partial | ✅ |
| Service connections | ❌ | ✅ |
| Owner type (local gov / private / state / federal) | ❌ | ✅ |
| Water source (ground / surface / purchased) | ❌ | ✅ |
| Wholesaler & school/daycare flags | ❌ | ✅ |
| Health-based violations + contaminants | ❌ | ✅ opt-in |
| Counties / cities served | ❌ | ✅ opt-in |
| Lead score (0–100) + lead signals | ❌ | ✅ |
| New-system / new-violation monitoring | ❌ | ✅ |

There are **~150,000 active public water systems** in the US (≈50,000 of them community systems serving year-round residents) — every one a potential buyer of treatment chemicals, equipment, lab testing, engineering, metering or compliance software.

### Use cases

- **B2B lead generation** — water utilities are recurring buyers: treatment chemicals & equipment (filtration, disinfection, membranes), pipe/valve/pump suppliers, SCADA / AMI smart-metering / leak-detection, lab & PFAS/lead testing, engineering & consulting, infrastructure financing, and compliance SaaS. Score systems by `populationServed` and reach the named `contactName` / `contactEmail` directly.
- **Territory planning** — pull every community system in a state, filter by size (`minPopulationServed`) and owner type, and build a clean call list for reps.
- **Compliance / service intent** — turn on `includeViolations` and `healthBasedViolationsOnly` to surface systems with recent MCL / treatment-technique violations — the highest-intent prospects for remediation, treatment and testing vendors.
- **Market & infrastructure analysis** — analyze water-source mix, system sizes, ownership and service connections by state or county.
- **Monitoring** — schedule recurring runs with `monitorMode` to capture **only new systems or newly-recorded violations** as fresh leads.

### How to use

1. [Sign up for Apify](https://console.apify.com/sign-up) — the free plan is enough to try this actor.
2. Open the **US Water System Scraper**, choose **states** and **system types**, set filters (size, owner, source, compliance), and click **Start**.
3. Watch results stream into the dataset table.
4. **Export** as JSON, CSV, Excel, XML, or HTML — or pull results programmatically via the [Apify API](https://docs.apify.com/api/v2).

### Input

```json
{
    "states": ["TX"],
    "pwsTypes": ["CWS"],
    "ownerTypes": ["L", "P"],
    "minPopulationServed": 3300,
    "withPhoneOnly": true,
    "includeViolations": true,
    "healthBasedViolationsOnly": false,
    "sortBy": "leadScore",
    "maxResults": 500
}
```

- **states** — two-letter USPS codes (`CA`, `TX`, `NY`). Leave empty to sweep all states & territories (bounded by `maxResults`).
- **pwsTypes** *(default `["CWS"]`)* — `CWS` (Community), `NTNCWS` (Non-Transient Non-Community: schools/factories/offices), `TNCWS` (Transient Non-Community: gas stations/campgrounds). Empty = all.
- **activeOnly** *(default true)* — only systems currently active in SDWIS.
- **ownerTypes / sourceTypes** — filter by ownership (Local gov, Private, State, Federal, Mixed, Native American) and water source (Ground / Surface / GUDI).
- **cities / zipCodes / nameQuery** — filter by the system's mailing city, ZIP prefix, or name text.
- **minPopulationServed / maxPopulationServed / minServiceConnections** — target by system size.
- **wholesalersOnly / servesSchoolOrDaycareOnly / withEmailOnly / withPhoneOnly** — high-value segment toggles.
- **includeViolations** *(default false)* — enrich each system with its EPA drinking-water violation history (counts, latest date, contaminants, recent detail).
- **healthBasedViolationsOnly** — keep only systems with recent health-based violations (needs `includeViolations`).
- **includeGeographicArea** *(default false)* — add the counties, cities and ZIPs each system serves.
- **sortBy** — `leadScore` (recommended), `populationHigh`, `connectionsHigh`, `recentViolation`, `name`, or `source`.
- **maxResults / maxResultsPerState / deduplicateResults** — output controls.
- **monitorMode / monitorKey** — only emit new / changed systems across scheduled runs.

### Output

One record per public water system (`recordType: "waterSystem"`):

```json
{
    "recordType": "waterSystem",
    "pwsid": "TX0610001",
    "pwsName": "City Of Austin Water",
    "pwsTypeCode": "CWS",
    "pwsType": "Community Water System",
    "isCommunity": true,
    "activityStatus": "Active",
    "ownerTypeCode": "L",
    "ownerType": "Local government",
    "isGovernmentOwned": true,
    "primarySourceCode": "SW",
    "primarySource": "Surface water",
    "isSurfaceWater": true,
    "populationServed": 960000,
    "populationCategory": "Very large (>100k)",
    "serviceConnections": 248000,
    "isWholesaler": true,
    "servesSchoolOrDaycare": false,
    "primacyType": "State",
    "epaRegion": "06",
    "orgName": "City Of Austin",
    "contactName": "Jane Doe",
    "contactEmail": "jane.doe@austintexas.gov",
    "contactPhone": "(512) 555-0142",
    "addressLine1": "625 E 10th St",
    "city": "Austin",
    "state": "TX",
    "zip": "78701",
    "fullAddress": "625 E 10th St, Austin, TX, 78701",
    "violationCount": 7,
    "healthBasedViolationCount": 1,
    "recentHealthViolationCount": 1,
    "latestViolationDate": "2024-09-30",
    "topContaminants": ["3100", "1040"],
    "hasRecentHealthViolation": true,
    "countiesServed": ["Travis"],
    "leadScore": 92,
    "leadSignals": ["Very large system (>100k served)", "Community water system", "Local government", "Has email", "Has phone", "Water wholesaler", "Recent health-based violation"],
    "sourceUrl": "https://data.epa.gov/efservice/WATER_SYSTEM/PWSID/TX0610001/JSON",
    "scrapedAt": "2026-06-20T12:00:00.000Z"
}
```

Every record also carries `sourceFields` — the complete raw SDWIS row — so no data is lost.

#### Field coverage — measured, not promised

Measured on real platform runs (2026-07-22) and verified field-by-field against the raw EPA
columns, so you know exactly what you are buying. **Core lead fields are 100%:** `pwsid`,
`pwsName`, `pwsType`, `ownerType`, `primarySource`, `populationServed`, `serviceConnections`,
`contactName`, `contactPhone`, `addressLine1`, `city`, `state`, `zip`, `fullAddress`, `leadScore`.

| Field | Coverage | Why |
|---|---|---|
| `contactEmail` | **100%** large municipal (TX) · 83% FL · 68% small rural (WY/MT) | EPA makes the admin email optional; coverage scales with system size. Use `withEmailOnly` to keep only systems that publish one. |
| `seasonBeginDate` / `seasonEndDate` | **100%** seasonal systems · 0% year-round | SDWIS records an operating season only for seasonal systems (campgrounds, RV parks) — not a gap. |
| `fax`, `phoneExt`, `altPhone`, `addressLine2` | 0–18% | Optional legacy SDWIS columns, rarely filled by the utility. |
| Violation block (`violationCount`, `healthBasedViolationCount`, `topContaminants`, …) | **100%** with `includeViolations` on | Off by default because it adds one request per system. |
| `countiesServed` / `citiesServed` / `zipsServed` | 97% / 57% / 7% with `includeGeographicArea` on | Off by default (one request per system). EPA indexes most systems by county, about half by city, and rarely by ZIP served. |

Nothing above is a parser gap — each was checked against its raw EPA column in `sourceFields`
and matches 1:1. Empty means EPA is empty.

### Automate & schedule

Run this actor on autopilot and pull results into your own stack:

- **[Apify API](https://docs.apify.com/api/v2)** — start runs, fetch datasets, and manage schedules over REST.
- **[apify-client for JavaScript](https://docs.apify.com/api/client/js/)** and **[apify-client for Python](https://docs.apify.com/api/client/python/)** — official SDKs.
- **[Schedules](https://docs.apify.com/platform/schedules)** — run it weekly/monthly with `monitorMode` to capture newly-added systems and newly-recorded violations as leads.
- **[Webhooks](https://docs.apify.com/platform/integrations/webhooks)** — trigger downstream actions (CRM import, Slack alert, email sequence) the moment a run finishes.

```js
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });

const run = await client.actor('scrapesage/us-water-system-scraper').call({
    states: ['CA'],
    pwsTypes: ['CWS'],
    minPopulationServed: 10000,
    withPhoneOnly: true,
    sortBy: 'leadScore',
    maxResults: 500,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Got ${items.length} water-utility leads`);
```

### Integrate with any app

Connect the dataset to 5,000+ apps — no code required:

- **[Make](https://docs.apify.com/platform/integrations/make)** — multi-step automation scenarios.
- **[Zapier](https://docs.apify.com/platform/integrations/zapier)** — push new utility leads straight into your CRM.
- **[Slack](https://docs.apify.com/platform/integrations/slack)** — get notified when a monitored search finds new systems.
- **[Google Drive / Sheets](https://docs.apify.com/platform/integrations/drive)** — auto-export every run to a spreadsheet.
- **[Airbyte](https://docs.apify.com/platform/integrations/airbyte)** — pipe results into your data warehouse.
- **[GitHub](https://docs.apify.com/platform/integrations/github)** — trigger runs from commits or releases.

### Use with AI assistants (MCP)

The output is clean, LLM-ready JSON. You can call this actor from Claude, ChatGPT, or any agent framework through the **[Apify MCP server](https://docs.apify.com/platform/integrations/mcp)** — ask your assistant to "find every large community water utility in Texas with a phone number and recent violations" and let it run this scraper for you.

### Agent-ready: autonomous payments (x402 & Skyfire)

This actor is **agent-ready** — AI agents can discover it, run it, and **pay for it autonomously**, with no Apify account and no human in the loop. It uses [pay-per-event](https://docs.apify.com/platform/actors/publishing/monetize/pay-per-event) pricing and [limited permissions](https://docs.apify.com/platform/actors/development/permissions), so it qualifies for Apify's agentic-payment standards:

- **[x402](https://docs.apify.com/platform/integrations/x402)** — an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp) — no account, no API key.
- **[Skyfire](https://docs.apify.com/platform/integrations/skyfire)** — agent-to-service payments for fully autonomous AI-agent workflows.

Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.

### More scrapers from scrapesage

Build a complete **US B2B lead-gen & regulatory-intelligence stack** from official open-data sources:

- **[EPA ECHO Scraper](https://apify.com/scrapesage/epa-echo-scraper)** — regulated facilities, environmental compliance, violations & penalties (air, water, hazardous waste).
- **[FMCSA Trucking Scraper](https://apify.com/scrapesage/fmcsa-trucking-scraper)** — motor carriers & trucking companies with safety ratings and contacts.
- **[MSHA Mine, Quarry & Aggregates Scraper](https://apify.com/scrapesage/msha-mine-operations-scraper)** — mine & quarry operators, parent companies and violations.
- **[USDA FSIS Establishment Scraper](https://apify.com/scrapesage/fsis-establishment-scraper)** — meat, poultry & egg plant leads.
- **[US Organic Operations Scraper](https://apify.com/scrapesage/us-organic-operations-scraper)** — USDA-certified organic business leads.
- **[US Property Records Scraper](https://apify.com/scrapesage/us-property-records-scraper)** — property & parcel records with owner mailing addresses.
- **[US Business Formation Scraper](https://apify.com/scrapesage/us-business-formation-scraper)** — newly-registered companies as fresh B2B leads.
- **[US Contractor License Scraper](https://apify.com/scrapesage/us-contractor-license-scraper)** — licensed contractors from official state registries.
- **[Website Contact Scraper](https://apify.com/scrapesage/website-contact-scraper)** — enrich any utility website for emails, phones and socials.

### Tips

- **Best leads first**: keep `pwsTypes` on `CWS` and `sortBy` on `leadScore` — community systems with a contact email/phone and large populations rank highest.
- **Service-intent targeting**: turn on `includeViolations` + `healthBasedViolationsOnly` to find systems with active water-quality problems (treatment, testing, engineering buyers).
- **National sweeps**: leave `states` empty and set a `maxResults` cap; use `maxResultsPerState` for an even spread across states.
- **Cost & speed**: compliance and geographic enrichment add one request per returned system — leave them off for the fastest, cheapest base list, then re-run with enrichment on your shortlist.
- **Proxies**: not needed — the EPA SDWIS / Envirofacts API is queried directly. Leave the proxy off for the fastest queries.

### FAQ

**Where does the data come from?** The official US EPA **SDWIS (Safe Drinking Water Information System)**, served through the public **Envirofacts** REST API (`data.epa.gov/efservice`). No API key or login is required.

**What is a "public water system"?** Any system that provides water for human consumption to at least 15 connections or 25 people. SDWIS classifies them as Community (CWS), Non-Transient Non-Community (NTNCWS), or Transient Non-Community (TNCWS).

**Do records include contact emails and phones?** Yes — SDWIS stores each system's administrative contact (name, email, phone, mailing address). Coverage varies by system; fields are `null` only when EPA doesn't publish them, never because the scraper skipped them.

**Can I get only systems with violations?** Yes — turn on `includeViolations`, then `healthBasedViolationsOnly` to keep only systems with recent health-based (MCL / treatment-technique) violations.

**Can I export to Google Sheets, CSV, or Excel?** Yes — one click in the dataset view, or automatically on every run via the [Google Drive integration](https://docs.apify.com/platform/integrations/drive).

**How do I monitor new systems automatically?** Turn on `monitorMode`, give each watch a `monitorKey`, and create a [Schedule](https://docs.apify.com/platform/schedules). Each run emits only systems that are new or whose violation history changed since the last run.

**Is this legal?** This actor collects publicly available government data only. You are responsible for using the data in compliance with applicable laws and EPA's terms.

### Need help?

Open an issue on the actor's **Issues** tab, or visit the [Apify help center](https://help.apify.com/). Feature requests are welcome — this actor is actively maintained.

# Actor input Schema

## `states` (type: `array`):

Filter by the water system's state — two-letter USPS codes, e.g. <code>CA</code>, <code>TX</code>, <code>NY</code>, <code>FL</code>. Leave empty to sweep all 50 states, DC and US territories (bounded by Max results).

## `pwsTypes` (type: `array`):

Which kinds of public water system to include. <b>CWS</b> = Community (year-round residents — cities, towns, mobile-home parks, HOAs; the best B2B leads). <b>NTNCWS</b> = Non-Transient Non-Community (schools, factories, offices with their own supply). <b>TNCWS</b> = Transient Non-Community (gas stations, campgrounds, rest stops). Leave empty for all types.

## `activeOnly` (type: `boolean`):

Only include water systems currently flagged as active in EPA's SDWIS (recommended for clean, contactable leads). Turn off to include inactive / historical systems.

## `ownerTypes` (type: `array`):

Keep only systems with the selected ownership. <b>Local government</b> (cities/towns/districts) and <b>Private</b> are the most actionable B2B buyers. Leave empty for all.

## `sourceTypes` (type: `array`):

Filter by primary water source. <b>Ground water</b> (wells) vs <b>Surface water</b> (rivers/lakes/reservoirs) — relevant for treatment, equipment and testing vendors. Leave empty for all.

## `cities` (type: `array`):

Filter by the system's mailing city (case-insensitive), e.g. <code>Houston</code>, <code>Phoenix</code>, <code>Denver</code>. Combine with a state for accuracy.

## `zipCodes` (type: `array`):

Filter by the system's mailing ZIP — full ZIP (<code>85001</code>) or a prefix (<code>850</code> matches all 850xx).

## `nameQuery` (type: `string`):

Only return systems whose name contains this text (case-insensitive), e.g. <code>city of</code>, <code>water district</code>, <code>utility</code>, <code>mobile home</code>, or a specific name.

## `minPopulationServed` (type: `integer`):

Only systems serving at least this many people. Larger systems = larger budgets (e.g. set <code>10000</code> for mid/large utilities).

## `maxPopulationServed` (type: `integer`):

Only systems serving at most this many people (e.g. set <code>3300</code> to target small/rural systems).

## `minServiceConnections` (type: `integer`):

Only systems with at least this many service connections (metered hookups).

## `wholesalersOnly` (type: `boolean`):

Only systems flagged as water wholesalers (they sell treated water to other systems) — large infrastructure buyers.

## `servesSchoolOrDaycareOnly` (type: `boolean`):

Only systems flagged as serving a school or daycare (relevant for lead-testing and compliance vendors).

## `withEmailOnly` (type: `boolean`):

Only return systems that publish an administrative contact email address.

## `withPhoneOnly` (type: `boolean`):

Only return systems that publish an administrative contact phone number.

## `includeViolations` (type: `boolean`):

Enrich each returned system with its EPA drinking-water violation history — total & health-based violation counts, latest violation date, top contaminants and recent violation detail. Adds one request per returned system. Health-based violations = high service-intent (treatment, testing, engineering).

## `healthBasedViolationsOnly` (type: `boolean`):

Only return systems with at least one recent health-based violation (MCL / MRDL / treatment-technique). Requires "Include compliance / violations".

## `recentViolationYears` (type: `integer`):

How many years back to count "recent" violations when compliance enrichment is on.

## `includeGeographicArea` (type: `boolean`):

Enrich each returned system with the counties, cities and ZIP codes it serves (from SDWIS geographic-area data). Adds one request per returned system.

## `minLeadScore` (type: `integer`):

Only return systems with a lead score (0–100) at or above this value.

## `sortBy` (type: `string`):

<b>Lead score</b> = most contactable / highest-value first (recommended). <b>Largest population</b> / <b>Most connections</b> rank by system size. <b>Recent violation</b> ranks by latest violation (needs compliance enrichment). <b>Source order</b> = fastest on very large limits.

## `maxResults` (type: `integer`):

Maximum number of water system records to return in this run.

## `maxResultsPerState` (type: `integer`):

Optional cap on records per state (useful for an even spread across a multi-state sweep). Leave empty for no per-state cap.

## `deduplicateResults` (type: `boolean`):

Skip duplicate systems (same PWSID) within this run (recommended).

## `monitorMode` (type: `boolean`):

Remember which systems were already returned (in a named key-value store) and emit ONLY systems that are <b>new</b> or whose violation history changed since the last run — each tagged with a <code>monitorEvent</code> (<code>new</code> or <code>new\_violation</code>). EPA refreshes SDWIS regularly; run on a Schedule to capture fresh systems & violations as leads. Works alongside Apify Schedules (the schedule starts the run; monitoring decides what's new).

## `monitorKey` (type: `string`):

Names the memory used by monitoring mode. Use a distinct key per saved watch (e.g. per state or system type) so different monitors don't share state.

## `proxyConfiguration` (type: `object`):

Optional proxy. The EPA SDWIS / Envirofacts API is queried directly and needs no proxy — leave this off for the fastest queries. Enable Apify Proxy only if your network requires it.

## Actor input object example

```json
{
  "states": [
    "WY"
  ],
  "pwsTypes": [
    "CWS"
  ],
  "activeOnly": true,
  "wholesalersOnly": false,
  "servesSchoolOrDaycareOnly": false,
  "withEmailOnly": false,
  "withPhoneOnly": false,
  "includeViolations": false,
  "healthBasedViolationsOnly": false,
  "recentViolationYears": 5,
  "includeGeographicArea": false,
  "sortBy": "leadScore",
  "maxResults": 1000,
  "deduplicateResults": true,
  "monitorMode": false,
  "monitorKey": "default",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (type: `string`):

All scraped public water system records in the default dataset, each with firmographics, administrative contact, population served, owner & source type, optional violation/compliance summary and a lead score.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "states": [
        "WY"
    ],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesage/us-water-system-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "states": ["WY"],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("scrapesage/us-water-system-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "states": [
    "WY"
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call scrapesage/us-water-system-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapesage/us-water-system-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/mAwe4LEuDl4DPejrp/builds/MeLjnXg3dUv7AXUAY/openapi.json